frontend-design

# 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.

# Skill: Frontend Design


## What This Skill Does

Guides the creation of **distinctive, production-grade frontend interfaces** that avoid generic "AI slop" aesthetics. Instead of cookie-cutter components with predictable color schemes and default fonts, this skill enforces creative vision, bold aesthetic choices, and meticulous attention to visual detail.

The output is real, working code — not mockups or wireframes.


## Execution Model

- **Always**: the primary agent runs this skill directly.
- **Rationale**: frontend design requires iterative visual judgment and direct user dialogue for aesthetic direction.
- **Output**: HTML/CSS/JS source files, component files (React, Vue, etc.), or full page implementations.


## Workflow


### Step 1: Design Thinking

Before writing any code, understand the context and commit to a **BOLD aesthetic direction**:

1. **Purpose**: What problem does this interface solve? Who uses it?
2. **Tone**: Pick a clear direction — choose from flavors like:
   - Brutally minimal
   - Maximalist chaos
   - Retro-futuristic
   - Organic / natural
   - Luxury / refined
   - Playful / toy-like
   - Editorial / magazine
   - Brutalist / raw
   - Art deco / geometric
   - Soft / pastel
   - Industrial / utilitarian
   - Or invent your own — these are inspiration, not limits
3. **Constraints**: Technical requirements (framework, performance, accessibility)
4. **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?

**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work — the key is **intentionality**, not intensity.


### Step 2: Implement with Exceptional Aesthetics

Create working code (HTML/CSS/JS, React, Vue, etc.) that is:

- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail

Follow the **Aesthetics Guidelines** below for every implementation.


### Step 3: Verify Visual Quality

Before presenting the result:

- Check that fonts load correctly and create the intended impression
- Verify color palette is cohesive (no accidental generic blues/greys)
- Test animations/transitions for smoothness
- Ensure spatial composition feels intentional, not default
- Run in browser to confirm the visual experience matches the vision


## Aesthetics Guidelines


### Motion & Animation

Use animations for effects and micro-interactions:

- Prioritize **CSS-only solutions** for HTML projects
- Use Motion library for React when available
- Focus on **high-impact moments**: one well-orchestrated page load with staggered reveals (`animation-delay`) creates more delight than scattered micro-interactions
- Use scroll-triggering and hover states that surprise


### Backgrounds & Visual Details

Create **atmosphere and depth** rather than flat solid colors:

- Gradient meshes, noise textures, geometric patterns
- Layered transparencies, dramatic shadows
- Decorative borders, custom cursors, grain overlays
- Contextual effects that match the overall aesthetic


## Rules

1. **Design-first thinking**: Always establish aesthetic direction before coding. Never jump straight into implementation without a visual concept.
2. **No AI slop**: Never use overused font families, clichéd color schemes, or cookie-cutter layouts. Every design must feel genuinely crafted.
3. **Intentional variety**: No two designs should look the same. Vary themes, fonts, aesthetics, and composition across generations.
4. **Match complexity to vision**: Maximalist designs need elaborate code with extensive animations. Minimalist designs need restraint, precision, and careful spacing. Elegance = executing the vision well.
5. **Production-grade output**: All code must be functional, not just visual. Interactions must work, links must resolve, responsive layouts must adapt.
6. **Context-specific character**: Interpret requirements creatively for the specific context. A fintech dashboard and a bakery homepage should look nothing alike.
7. **No built-in explore agent**: Do NOT use the built-in `explore` subagent type.