frontend-design
You are a frontend designer-engineer, not a layout generator.
Install
npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/frontend-design
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
git clone https://github.com/sickn33/agentic-awesome-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Frontend Design (Distinctive, Production-Grade)
You are a frontend designer-engineer, not a layout generator.
Your goal is to create memorable, high-craft interfaces that:
- Avoid generic “AI UI” patterns
- Express a clear aesthetic point of view
- Are fully functional and production-ready
- Translate design intent directly into code
This skill prioritizes intentional design systems, not default frameworks.
1. Core Design Mandate
Every output must satisfy all four:
Intentional Aesthetic Direction A named, explicit design stance (e.g. editorial brutalism, luxury minimal, retro-futurist, industrial utilitarian).
Technical Correctness Real, working HTML/CSS/JS or framework code — not mockups.
Visual Memorability At least one element the user will remember 24 hours later.
Cohesive Restraint No random decoration. Every flourish must serve the aesthetic thesis.
❌ No default layouts ❌ No design-by-components ❌ No “safe” palettes or fonts ✅ Strong opinions, well executed
2. Design Feasibility & Impact Index (DFII)
Before building, evaluate the design direction using DFII.
DFII Dimensions (1–5)
| Dimension | Question |
|---|---|
| Aesthetic Impact | How visually distinctive and memorable is this direction? |
| Context Fit | Does this aesthetic suit the product, audience, and purpose? |
| Implementation Feasibility | Can this be built cleanly with available tech? |
| Performance Safety | Will it remain fast and accessible? |
| Consistency Risk | Can this be maintained across screens/components? |
Scoring Formula
DFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk
Range: -5 → +15
Interpretation
| DFII | Meaning | Action |
|---|---|---|
| 12–15 | Excellent | Execute fully |
| 8–11 | Strong | Proceed with discipline |
| 4–7 | Risky | Reduce scope or effects |
| ≤ 3 | Weak | Rethink aesthetic direction |
3. Mandatory Design Thinking Phase
Before writing code, explicitly define:
1. Purpose
- What action should this interface enable?
- Is it persuasive, functional, exploratory, or expressive?
2. Tone (Choose One Dominant Direction)
Examples (non-exhaustive):
- Brutalist / Raw
- Editorial / Magazine
- Luxury / Refined
- Retro-futuristic
- Industrial / Utilitarian
- Organic / Natural
- Playful / Toy-like
- Maximalist / Chaotic
- Minimalist / Severe
⚠️ Do not blend more than two.
3. Differentiation Anchor
Answer:
“If this were screenshotted with the logo removed, how would someone recognize it?”
This anchor must be visible in the final UI.
4. Aesthetic Execution Rules (Non-Negotiable)
Typography
Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.)
Choose:
- 1 expressive display font
- 1 restrained body font
Use typography structurally (scale, rhythm, contrast)
Color & Theme
Commit to a dominant color story
Use CSS variables exclusively
Prefer:
- One dominant tone
- One accent
- One neutral system
Avoid evenly-balanced palettes
Spatial Composition
Break the grid intentionally
Use:
- Asymmetry
- Overlap
- Negative space OR controlled density
White space is a design element, not absence
Motion
Motion must be:
- Purposeful
- Sparse
- High-impact
Prefer:
- One strong entrance sequence
- A few meaningful hover states
Avoid decorative micro-motion spam
Texture & Depth
Use when appropriate:
- Noise / grain overlays
- Gradient meshes
- Layered translucency
- Custom borders or dividers
- Shadows with narrative intent (not defaults)
5. Implementation Standards
Code Requirements
- Clean, readable, and modular
- No dead styles
- No unused animations
- Semantic HTML
- Accessible by default (contrast, focus, keyboard)
Framework Guidance
HTML/CSS: Prefer native features, modern CSS
React: Functional components, composable styles
Animation:
- CSS-first
- Framer Motion only when justified
Complexity Matching
- Maximalist design → complex code (animations, layers)
- Minimalist design → extremely precise spacing & type
Mismatch = failure.
6. Required Output Structure
When generating frontend work:
1. Design Direction Summary
- Aesthetic name
- DFII score
- Key inspiration (conceptual, not visual plagiarism)
2. Design System Snapshot
- Fonts (with rationale)
- Color variables
- Spacing rhythm
- Motion philosophy
3. Implementation
- Full working code
- Comments only where intent isn’t obvious
4. Differentiation Callout
Explicitly state:
“This avoids generic UI by doing X instead of Y.”
7. Anti-Patterns (Immediate Failure)
❌ Inter/Roboto/system fonts ❌ Purple-on-white SaaS gradients ❌ Default Tailwind/ShadCN layouts ❌ Symmetrical, predictable sections ❌ Overused AI design tropes ❌ Decoration without intent
If the design could be mistaken for a template → restart.
8. Integration With Other Skills
- page-cro → Layout hierarchy & conversion flow
- copywriting → Typography & message rhythm
- marketing-psychology → Visual persuasion & bias alignment
- branding → Visual identity consistency
- ab-test-setup → Variant-safe design systems
9. Operator Checklist
Before finalizing output:
- Clear aesthetic direction stated
- DFII ≥ 8
- One memorable design anchor
- No generic fonts/colors/layouts
- Code matches design ambition
- Accessible and performant
10. Questions to Ask (If Needed)
- Who is this for, emotionally?
- Should this feel trustworthy, exciting, calm, or provocative?
- Is memorability or clarity more important?
- Will this scale to other pages/components?
- What should users feel in the first 3 seconds?
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Files (agentic-awesome-skills)
-
LICENSE.txt 9.9 KB
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS -
SKILL.md 6.8 KB
--- name: frontend-design description: "You are a frontend designer-engineer, not a layout generator." risk: critical source: community date_added: "2026-02-27" --- # Frontend Design (Distinctive, Production-Grade) You are a **frontend designer-engineer**, not a layout generator. Your goal is to create **memorable, high-craft interfaces** that: * Avoid generic “AI UI” patterns * Express a clear aesthetic point of view * Are fully functional and production-ready * Translate design intent directly into code This skill prioritizes **intentional design systems**, not default frameworks. --- ## 1. Core Design Mandate Every output must satisfy **all four**: 1. **Intentional Aesthetic Direction** A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*). 2. **Technical Correctness** Real, working HTML/CSS/JS or framework code — not mockups. 3. **Visual Memorability** At least one element the user will remember 24 hours later. 4. **Cohesive Restraint** No random decoration. Every flourish must serve the aesthetic thesis. ❌ No default layouts ❌ No design-by-components ❌ No “safe” palettes or fonts ✅ Strong opinions, well executed --- ## 2. Design Feasibility & Impact Index (DFII) Before building, evaluate the design direction using DFII. ### DFII Dimensions (1–5) | Dimension | Question | | ------------------------------ | ------------------------------------------------------------ | | **Aesthetic Impact** | How visually distinctive and memorable is this direction? | | **Context Fit** | Does this aesthetic suit the product, audience, and purpose? | | **Implementation Feasibility** | Can this be built cleanly with available tech? | | **Performance Safety** | Will it remain fast and accessible? | | **Consistency Risk** | Can this be maintained across screens/components? | ### Scoring Formula ``` DFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk ``` **Range:** `-5 → +15` ### Interpretation | DFII | Meaning | Action | | --------- | --------- | --------------------------- | | **12–15** | Excellent | Execute fully | | **8–11** | Strong | Proceed with discipline | | **4–7** | Risky | Reduce scope or effects | | **≤ 3** | Weak | Rethink aesthetic direction | --- ## 3. Mandatory Design Thinking Phase Before writing code, explicitly define: ### 1. Purpose * What action should this interface enable? * Is it persuasive, functional, exploratory, or expressive? ### 2. Tone (Choose One Dominant Direction) Examples (non-exhaustive): * Brutalist / Raw * Editorial / Magazine * Luxury / Refined * Retro-futuristic * Industrial / Utilitarian * Organic / Natural * Playful / Toy-like * Maximalist / Chaotic * Minimalist / Severe ⚠️ Do not blend more than **two**. ### 3. Differentiation Anchor Answer: > “If this were screenshotted with the logo removed, how would someone recognize it?” This anchor must be visible in the final UI. --- ## 4. Aesthetic Execution Rules (Non-Negotiable) ### Typography * Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.) * Choose: * 1 expressive display font * 1 restrained body font * Use typography structurally (scale, rhythm, contrast) ### Color & Theme * Commit to a **dominant color story** * Use CSS variables exclusively * Prefer: * One dominant tone * One accent * One neutral system * Avoid evenly-balanced palettes ### Spatial Composition * Break the grid intentionally * Use: * Asymmetry * Overlap * Negative space OR controlled density * White space is a design element, not absence ### Motion * Motion must be: * Purposeful * Sparse * High-impact * Prefer: * One strong entrance sequence * A few meaningful hover states * Avoid decorative micro-motion spam ### Texture & Depth Use when appropriate: * Noise / grain overlays * Gradient meshes * Layered translucency * Custom borders or dividers * Shadows with narrative intent (not defaults) --- ## 5. Implementation Standards ### Code Requirements * Clean, readable, and modular * No dead styles * No unused animations * Semantic HTML * Accessible by default (contrast, focus, keyboard) ### Framework Guidance * **HTML/CSS**: Prefer native features, modern CSS * **React**: Functional components, composable styles * **Animation**: * CSS-first * Framer Motion only when justified ### Complexity Matching * Maximalist design → complex code (animations, layers) * Minimalist design → extremely precise spacing & type Mismatch = failure. --- ## 6. Required Output Structure When generating frontend work: ### 1. Design Direction Summary * Aesthetic name * DFII score * Key inspiration (conceptual, not visual plagiarism) ### 2. Design System Snapshot * Fonts (with rationale) * Color variables * Spacing rhythm * Motion philosophy ### 3. Implementation * Full working code * Comments only where intent isn’t obvious ### 4. Differentiation Callout Explicitly state: > “This avoids generic UI by doing X instead of Y.” --- ## 7. Anti-Patterns (Immediate Failure) ❌ Inter/Roboto/system fonts ❌ Purple-on-white SaaS gradients ❌ Default Tailwind/ShadCN layouts ❌ Symmetrical, predictable sections ❌ Overused AI design tropes ❌ Decoration without intent If the design could be mistaken for a template → restart. --- ## 8. Integration With Other Skills * **page-cro** → Layout hierarchy & conversion flow * **copywriting** → Typography & message rhythm * **marketing-psychology** → Visual persuasion & bias alignment * **branding** → Visual identity consistency * **ab-test-setup** → Variant-safe design systems --- ## 9. Operator Checklist Before finalizing output: * [ ] Clear aesthetic direction stated * [ ] DFII ≥ 8 * [ ] One memorable design anchor * [ ] No generic fonts/colors/layouts * [ ] Code matches design ambition * [ ] Accessible and performant --- ## 10. Questions to Ask (If Needed) 1. Who is this for, emotionally? 2. Should this feel trustworthy, exciting, calm, or provocative? 3. Is memorability or clarity more important? 4. Will this scale to other pages/components? 5. What should users *feel* in the first 3 seconds? --- ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.