Frontend Design
Frontend Design is an design AI skill with a core value of Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. It
helps developers solve real-world problems in the design domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...
Quick Facts
mkdir -p ./skills/frontend-design && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/frontend-design/SKILL.md -o ./skills/frontend-design/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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 borde
🎯 Best For
- UI designers
- Product designers
- Claude users
- Designers
- Creative professionals
💡 Use Cases
- Generating component mockups
- Creating design system tokens
- Design system documentation
- Component specification creation
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Frontend Design to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
Does Frontend Design generate production-ready design specs?
It generates detailed specifications that developers can use directly. Review and adjust for your specific design system.
How do I install Frontend Design?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/frontend-design/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping usability testing
AI-generated designs should be validated with real users before development.
Not reading the full skill
Skills contain important context and edge cases beyond the quick start.