IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Use any relevant skills in this directory that match the task. User request: "Please review this checkout flow for UX problems, but also flag accessibility and performance issues before we ship." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...


SKILL.md
adapt/SKILL.md
animate/SKILL.md
arrange/SKILL.md
audit/SKILL.md
bolder/SKILL.md
clarify/SKILL.md
colorize/SKILL.md
critique/SKILL.md
delight/SKILL.md
distill/SKILL.md
extract/SKILL.md
frontend-design/SKILL.md
harden/SKILL.md
normalize/SKILL.md
onboard/SKILL.md
optimize/SKILL.md
overdrive/SKILL.md
polish/SKILL.md
quieter/SKILL.md
teach-impeccable/SKILL.md
typeset/SKILL.md


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md


**Checking project guidelines**

I see the project guidelines instruct me to always load the "caveman" skill and ensure other appropriate skills are loaded. I think “audit” might be a good choice for accessibility and performance, but I need to confirm that. So, my next step is to read through the audit documentation to check the specifics. Let's go ahead and use the functions to read the relevant SKILL.md file. This should help clarify everything.


---
name: audit
description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
---

## MANDATORY PREPARATION

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.

---

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.

## Diagnostic Scan

Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.

### 1. Accessibility (A11y)

**Check for**:
- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA)
- **Missing ARIA**: Interactive elements without proper roles, labels, or states
- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps
- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons
- **Alt text**: Missing or poor image descriptions
- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA)

### 2. Performance

**Check for**:
- **Layout thrashing**: Reading/writing layout properties in loops
- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity
- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change
- **Bundle size**: Unnecessary imports, unused dependencies
- **Render performance**: Unnecessary re-renders, missing memoization

**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized)

### 3. Theming

**Check for**:
- **Hard-coded colors**: Colors not using design tokens
- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme
- **Inconsistent tokens**: Using wrong tokens, mixing token types
- **Theme switching issues**: Values that don't update on theme change

**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly)

### 4. Responsive Design

**Check for**:
- **Fixed widths**: Hard-coded widths that break on mobile
- **Touch targets**: Interactive elements < 44x44px
- **Horizontal scroll**: Content overflow on narrow viewports
- **Text scaling**: Layouts that break when text size increases
- **Missing breakpoints**: No mobile/tablet variants

**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets)

### 5. Anti-Patterns (CRITICAL)

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design)

## Generate Report

### Audit Health Score

| # | Dimension | Score | Key Finding |
|---|-----------|-------|-------------|
| 1 | Accessibility | ? | [most critical a11y issue or "--"] |
| 2 | Performance | ? | |
| 3 | Responsive Design | ? | |
| 4 | Theming | ? | |
| 5 | Anti-Patterns | ? | |
| **Total** | | **??/20** | **[Rating band]** |

**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)

### Anti-Patterns Verdict
**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest.

### Executive Summary
- Audit Health Score: **??/20** ([rating band])
- Total issues found (count by severity: P0/P1/P2/P3)
- Top 3-5 critical issues
- Recommended next steps

### Detailed Findings by Severity

Tag every issue with **P0-P3 severity**:
- **P0 Blocking**: Prevents task completion — fix immediately
- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release
- **P2 Minor**: Annoyance, workaround exists — fix in next pass
- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits

For each issue, document:
- **[P?] Issue name**
- **Location**: Component, file, line
- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern
- **Impact**: How it affects users
- **WCAG/Standard**: Which standard it violates (if applicable)
- **Recommendation**: How to fix it
- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

### Patterns & Systemic Issues

Identify recurring problems that indicate systemic gaps rather than one-off mistakes:
- "Hard-coded colors appear in 15+ components, should use design tokens"
- "Touch targets consistently too small (<44px) throughout mobile experience"

### Positive Findings

Note what's working well — good practices to maintain and replicate.

## Recommended Actions

List recommended commands in priority order (P0 first, then P1, then P2):

1. **[P?] `/command-name`** — Brief description (specific context from audit findings)
2. **[P?] `/command-name`** — Brief description (specific context)

**Rules**: Only recommend commands from: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended.

After presenting the summary, tell the user:

> You can ask me to run these one at a time, all at once, or in any order you prefer.
>
> Re-run `/audit` after fixes to see your score improve.

**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.

**NEVER**:
- Report issues without explaining impact (why does this matter?)
- Provide generic recommendations (be specific and actionable)
- Skip positive findings (celebrate what works)
- Forget to prioritize (everything can't be P0)
- Report false positives without verification

Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement.


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md

must-5e1881d9-0

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.

must-5e1881d9-1

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

- **Missing ARIA**: Interactive elements without proper roles, labels, or states

- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps

- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons

- **Alt text**: Missing or poor image descriptions

- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change

- **Render performance**: Unnecessary re-renders, missing memoization

- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme

must-5e1881d9-2

- **Theme switching issues**: Values that don't update on theme change

- **Missing breakpoints**: No mobile/tablet variants

must-5e1881d9-3

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

must-5e1881d9-4

- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

must-5e1881d9-5

- "Hard-coded colors appear in 15+ components, should use design tokens"

must-5e1881d9-6

> You can ask me to run these one at a time, all at once, or in any order you prefer.


---
name: frontend-design
description: Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context.
license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution.
---

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

## Context Gathering Protocol

Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work.

**Required context** — every design skill needs at minimum:
- **Target audience**: Who uses this product and in what context?
- **Use cases**: What jobs are they trying to get done?
- **Brand personality/tone**: How should the interface feel?

Individual skills may require additional context — check the skill's preparation section for specifics.

**CRITICAL**: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.

**Gathering order:**
1. **Check current instructions (instant)**: If your loaded instructions already contain a **Design Context** section, proceed immediately.
2. **Check .impeccable.md (fast)**: If not in instructions, read `.impeccable.md` from the project root. If it exists and contains the required context, proceed.
3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run /teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

---

## Design Direction

Commit to a BOLD aesthetic direction:
- **Purpose**: What problem does this interface solve? Who uses it?
- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
- **Constraints**: Technical requirements (framework, performance, accessibility).
- **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.

Then implement working code that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail

## Frontend Aesthetics Guidelines

### Typography
→ *Consult [typography reference](reference/typography.md) for scales, pairing, and loading strategies.*

Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.

**DO**: Use a modular type scale with fluid sizing (clamp)
**DO**: Vary font weights and sizes to create clear visual hierarchy
**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults
**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes
**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

### Color & Theme
→ *Consult [color reference](reference/color-and-contrast.md) for OKLCH, palettes, and dark mode.*

Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.

**DO**: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes
**DO**: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion
**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead
**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature
**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds
**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful
**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

### Layout & Space
→ *Consult [spatial reference](reference/spatial-design.md) for grids, rhythm, and container queries.*

Create visual rhythm through varied spacing—not the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis.

**DO**: Create visual rhythm through varied spacing—tight groupings, generous separations
**DO**: Use fluid spacing with clamp() that breathes on larger screens
**DO**: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis
**DON'T**: Wrap everything in cards—not everything needs a container
**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy
**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly
**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent
**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed
**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous

### Visual Details
**DO**: Use intentional, purposeful decorative elements that reinforce brand
**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully
**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional
**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful
**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output
**DON'T**: Use modals unless there's truly no better alternative—modals are lazy

### Motion
→ *Consult [motion reference](reference/motion-design.md) for timing, easing, and reduced motion.*

Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.

**DO**: Use motion to convey state changes—entrances, exits, feedback
**DO**: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration
**DO**: For height animations, use grid-template-rows transitions instead of animating height directly
**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only
**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

### Interaction
→ *Consult [interaction reference](reference/interaction-design.md) for forms, focus, and loading patterns.*

Make interactions feel fast. Use optimistic UI—update immediately, sync later.

**DO**: Use progressive disclosure—start simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions)
**DO**: Design empty states that teach the interface, not just say "nothing here"
**DO**: Make every interactive surface feel intentional and responsive
**DON'T**: Repeat the same information—redundant headers, intros that restate the heading
**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters

### Responsive
→ *Consult [responsive reference](reference/responsive-design.md) for mobile-first, fluid design, and container queries.*

**DO**: Use container queries (@container) for component-level responsiveness
**DO**: Adapt the interface for different contexts—don't just shrink it
**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it

### UX Writing
→ *Consult [ux-writing reference](reference/ux-writing.md) for labels, errors, and empty states.*

**DO**: Make every word earn its place
**DON'T**: Repeat information users can already see

---

## The AI Slop Test

**Critical quality check**: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

---

## Implementation Principles

Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details.

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md

must-5e1881d9-0

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.

must-5e1881d9-1

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

- **Missing ARIA**: Interactive elements without proper roles, labels, or states

- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps

- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons

- **Alt text**: Missing or poor image descriptions

- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change

- **Render performance**: Unnecessary re-renders, missing memoization

- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme

must-5e1881d9-2

- **Theme switching issues**: Values that don't update on theme change

- **Missing breakpoints**: No mobile/tablet variants

must-5e1881d9-3

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

must-5e1881d9-4

- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

must-5e1881d9-5

- "Hard-coded colors appear in 15+ components, should use design tokens"

must-5e1881d9-6

> You can ask me to run these one at a time, all at once, or in any order you prefer.

NOTICE.md

NOTICE.md

must-41032146-0

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

must-41032146-1

Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work.

must-41032146-2

- **Brand personality/tone**: How should the interface feel?

must-41032146-3

**CRITICAL**: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.

.impeccable.md

.impeccable.md

.impeccable.md

.impeccable.md

must-41032146-4

3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run /teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

reference/typography.md

reference/typography.md

must-41032146-5

**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults

must-41032146-6

**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes

must-41032146-7

**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

reference/color-and-contrast.md

reference/color-and-contrast.md

must-41032146-8

**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead

must-41032146-9

**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature

must-41032146-10

**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds

must-41032146-11

**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful

must-41032146-12

**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

reference/spatial-design.md

reference/spatial-design.md

must-41032146-13

**DON'T**: Wrap everything in cards—not everything needs a container

must-41032146-14

**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy

must-41032146-15

**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly

must-41032146-16

**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent

must-41032146-17

**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed

must-41032146-18

**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous

must-41032146-19

**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully

must-41032146-20

**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional

must-41032146-21

**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful

must-41032146-22

**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output

must-41032146-23

**DON'T**: Use modals unless there's truly no better alternative—modals are lazy

reference/motion-design.md

reference/motion-design.md

must-41032146-24

**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only

must-41032146-25

**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

reference/interaction-design.md

reference/interaction-design.md

must-41032146-26

**DON'T**: Repeat the same information—redundant headers, intros that restate the heading

must-41032146-27

**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters

reference/responsive-design.md

reference/responsive-design.md

must-41032146-28

**DO**: Adapt the interface for different contexts—don't just shrink it

must-41032146-29

**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it

reference/ux-writing.md

reference/ux-writing.md

must-41032146-30

**DON'T**: Repeat information users can already see

must-41032146-31

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

must-41032146-32

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

must-41032146-33

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

must-41032146-34

Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.


---
name: critique
description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
---

## MANDATORY PREPARATION

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what the interface is trying to accomplish.

---

Conduct a holistic design critique, evaluating whether the interface actually works — not just technically, but as a designed experience. Think like a design director giving feedback.

## Phase 1: Design Critique

Evaluate the interface across these dimensions:

### 1. AI Slop Detection (CRITICAL)

**This is the most important check.** Does this look like every other AI-generated interface from 2024-2025?

Review the design against ALL the **DON'T** guidelines in the frontend-design skill — they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.

**The test**: If you showed this to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.

### 2. Visual Hierarchy
- Does the eye flow to the most important element first?
- Is there a clear primary action? Can you spot it in 2 seconds?
- Do size, color, and position communicate importance correctly?
- Is there visual competition between elements that should have different weights?

### 3. Information Architecture & Cognitive Load
> *Consult [cognitive-load](reference/cognitive-load.md) for the working memory rule and 8-item checklist*
- Is the structure intuitive? Would a new user understand the organization?
- Is related content grouped logically?
- Are there too many choices at once? Count visible options at each decision point — if >4, flag it
- Is the navigation clear and predictable?
- **Progressive disclosure**: Is complexity revealed only when needed, or dumped on the user upfront?
- **Run the 8-item cognitive load checklist** from the reference. Report failure count: 0–1 = low (good), 2–3 = moderate, 4+ = critical.

### 4. Emotional Journey
- What emotion does this interface evoke? Is that intentional?
- Does it match the brand personality?
- Does it feel trustworthy, approachable, premium, playful — whatever it should feel?
- Would the target user feel "this is for me"?
- **Peak-end rule**: Is the most intense moment positive? Does the experience end well (confirmation, celebration, clear next step)?
- **Emotional valleys**: Check for onboarding frustration, error cliffs, feature discovery gaps, or anxiety spikes at high-stakes moments (payment, delete, commit)
- **Interventions at negative moments**: Are there design interventions where users are likely to feel frustrated or anxious? (progress indicators, reassurance copy, undo options, social proof)

### 5. Discoverability & Affordance
- Are interactive elements obviously interactive?
- Would a user know what to do without instructions?
- Are hover/focus states providing useful feedback?
- Are there hidden features that should be more visible?

### 6. Composition & Balance
- Does the layout feel balanced or uncomfortably weighted?
- Is whitespace used intentionally or just leftover?
- Is there visual rhythm in spacing and repetition?
- Does asymmetry feel designed or accidental?

### 7. Typography as Communication
- Does the type hierarchy clearly signal what to read first, second, third?
- Is body text comfortable to read? (line length, spacing, size)
- Do font choices reinforce the brand/tone?
- Is there enough contrast between heading levels?

### 8. Color with Purpose
- Is color used to communicate, not just decorate?
- Does the palette feel cohesive?
- Are accent colors drawing attention to the right things?
- Does it work for colorblind users? (not just technically — does meaning still come through?)

### 9. States & Edge Cases
- Empty states: Do they guide users toward action, or just say "nothing here"?
- Loading states: Do they reduce perceived wait time?
- Error states: Are they helpful and non-blaming?
- Success states: Do they confirm and guide next steps?

### 10. Microcopy & Voice
- Is the writing clear and concise?
- Does it sound like a human (the right human for this brand)?
- Are labels and buttons unambiguous?
- Does error copy help users fix the problem?

## Phase 2: Present Findings

Structure your feedback as a design director would:

### Design Health Score
> *Consult [heuristics-scoring](reference/heuristics-scoring.md)*

Score each of Nielsen's 10 heuristics 0–4. Present as a table:

| # | Heuristic | Score | Key Issue |
|---|-----------|-------|-----------|
| 1 | Visibility of System Status | ? | [specific finding or "—" if solid] |
| 2 | Match System / Real World | ? | |
| 3 | User Control and Freedom | ? | |
| 4 | Consistency and Standards | ? | |
| 5 | Error Prevention | ? | |
| 6 | Recognition Rather Than Recall | ? | |
| 7 | Flexibility and Efficiency | ? | |
| 8 | Aesthetic and Minimalist Design | ? | |
| 9 | Error Recovery | ? | |
| 10 | Help and Documentation | ? | |
| **Total** | | **??/40** | **[Rating band]** |

Be honest with scores. A 4 means genuinely excellent. Most real interfaces score 20–32.

### Anti-Patterns Verdict
**Start here.** Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest.

### Overall Impression
A brief gut reaction — what works, what doesn't, and the single biggest opportunity.

### What's Working
Highlight 2–3 things done well. Be specific about why they work.

### Priority Issues
The 3–5 most impactful design problems, ordered by importance.

For each issue, tag with **P0–P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions):
- **[P?] What**: Name the problem clearly
- **Why it matters**: How this hurts users or undermines goals
- **Fix**: What to do about it (be concrete)
- **Suggested command**: Which command could address this (from: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

### Persona Red Flags
> *Consult [personas](reference/personas.md)*

Auto-select 2–3 personas most relevant to this interface type (use the selection table in the reference). If `AGENTS.md` contains a `## Design Context` section from `teach-impeccable`, also generate 1–2 project-specific personas from the audience/brand info.

For each selected persona, walk through the primary user action and list specific red flags found:

**Alex (Power User)**: No keyboard shortcuts detected. Form requires 8 clicks for primary action. Forced modal onboarding. ⚠ High abandonment risk.

**Jordan (First-Timer)**: Icon-only nav in sidebar. Technical jargon in error messages ("404 Not Found"). No visible help. ⚠ Will abandon at step 2.

Be specific — name the exact elements and interactions that fail each persona. Don't write generic persona descriptions; write what broke for them.

### Minor Observations
Quick notes on smaller issues worth addressing.

**Remember**:
- Be direct — vague feedback wastes everyone's time
- Be specific — "the submit button" not "some elements"
- Say what's wrong AND why it matters to users
- Give concrete suggestions, not just "consider exploring..."
- Prioritize ruthlessly — if everything is important, nothing is
- Don't soften criticism — developers need honest feedback to ship great design

## Phase 3: Ask the User

**After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan.

Ask questions along these lines (adapt to the specific findings — do NOT ask generic questions):

1. **Priority direction**: Based on the issues found, ask which category matters most to the user right now. For example: "I found problems with visual hierarchy, color usage, and information overload. Which area should we tackle first?" Offer the top 2–3 issue categories as options.

2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer/bolder/more playful?" Offer 2–3 tonal directions as options based on what would fix the issues found.

3. **Scope**: Ask how much the user wants to take on. For example: "I found N issues. Want to address everything, or focus on the top 3?" Offer scope options like "Top 3 only", "All issues", "Critical issues only".

4. **Constraints** (optional — only ask if relevant): If the findings touch many areas, ask if anything is off-limits. For example: "Should any sections stay as-is?" This prevents the plan from touching things the user considers done.

**Rules for questions**:
- Every question must reference specific findings from Phase 2 — never ask generic "who is your audience?" questions
- Keep it to 2–4 questions maximum — respect the user's time
- Offer concrete options, not open-ended prompts
- If findings are straightforward (e.g., only 1–2 clear issues), skip questions and go directly to Phase 4

## Phase 4: Recommended Actions

**After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Phase 3.

### Action Summary

List recommended commands in priority order, based on the user's answers:

1. **`/command-name`** — Brief description of what to fix (specific context from critique findings)
2. **`/command-name`** — Brief description (specific context)
...

**Rules for recommendations**:
- Only recommend commands from: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive
- Order by the user's stated priorities first, then by impact
- Each item's description should carry enough context that the command knows what to focus on
- Map each Priority Issue to the appropriate command
- Skip commands that would address zero issues
- If the user chose a limited scope, only include items within that scope
- If the user marked areas as off-limits, exclude commands that would touch those areas
- End with `/polish` as the final step if any fixes were recommended

After presenting the summary, tell the user:

> You can ask me to run these one at a time, all at once, or in any order you prefer.
>
> Re-run `/critique` after fixes to see your score improve.


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md

must-5e1881d9-0

must-5e1881d9-1

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

- **Missing ARIA**: Interactive elements without proper roles, labels, or states

- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps

- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons

- **Alt text**: Missing or poor image descriptions

- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change

- **Render performance**: Unnecessary re-renders, missing memoization

- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme

must-5e1881d9-2

- **Theme switching issues**: Values that don't update on theme change

- **Missing breakpoints**: No mobile/tablet variants

must-5e1881d9-3

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

must-5e1881d9-4

- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

must-5e1881d9-5

- "Hard-coded colors appear in 15+ components, should use design tokens"

must-5e1881d9-6

> You can ask me to run these one at a time, all at once, or in any order you prefer.

NOTICE.md

NOTICE.md

must-41032146-0

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

must-41032146-1

Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work.

must-41032146-2

- **Brand personality/tone**: How should the interface feel?

must-41032146-3

**CRITICAL**: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.

.impeccable.md

.impeccable.md

.impeccable.md

.impeccable.md

must-41032146-4

3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run /teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

reference/typography.md

reference/typography.md

must-41032146-5

**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults

must-41032146-6

**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes

must-41032146-7

**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

reference/color-and-contrast.md

reference/color-and-contrast.md

must-41032146-8

**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead

must-41032146-9

**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature

must-41032146-10

**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds

must-41032146-11

**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful

must-41032146-12

**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

reference/spatial-design.md

reference/spatial-design.md

must-41032146-13

**DON'T**: Wrap everything in cards—not everything needs a container

must-41032146-14

**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy

must-41032146-15

**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly

must-41032146-16

**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent

must-41032146-17

**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed

must-41032146-18

**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous

must-41032146-19

**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully

must-41032146-20

**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional

must-41032146-21

**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful

must-41032146-22

**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output

must-41032146-23

**DON'T**: Use modals unless there's truly no better alternative—modals are lazy

reference/motion-design.md

reference/motion-design.md

must-41032146-24

**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only

must-41032146-25

**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

reference/interaction-design.md

reference/interaction-design.md

must-41032146-26

**DON'T**: Repeat the same information—redundant headers, intros that restate the heading

must-41032146-27

**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters

reference/responsive-design.md

reference/responsive-design.md

must-41032146-28

**DO**: Adapt the interface for different contexts—don't just shrink it

must-41032146-29

**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it

reference/ux-writing.md

reference/ux-writing.md

must-41032146-30

**DON'T**: Repeat information users can already see

must-41032146-31

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

must-41032146-32

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

must-41032146-33

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

must-41032146-34

Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

must-54e41674-0

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what the interface is trying to accomplish.

must-54e41674-1

Review the design against ALL the **DON'T** guidelines in the frontend-design skill — they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.

must-54e41674-2

- Is there visual competition between elements that should have different weights?

reference/cognitive-load.md

reference/cognitive-load.md

- **Run the 8-item cognitive load checklist** from the reference. Report failure count: 0–1 = low (good), 2–3 = moderate, 4+ = critical.

must-54e41674-3

- Does it feel trustworthy, approachable, premium, playful — whatever it should feel?

- **Emotional valleys**: Check for onboarding frustration, error cliffs, feature discovery gaps, or anxiety spikes at high-stakes moments (payment, delete, commit)

must-54e41674-4

- Are there hidden features that should be more visible?

- Error states: Are they helpful and non-blaming?

- Does error copy help users fix the problem?

reference/heuristics-scoring.md

reference/heuristics-scoring.md

| 5 | Error Prevention | ? | |

| 9 | Error Recovery | ? | |

reference/heuristics-scoring.md

reference/heuristics-scoring.md

reference/personas.md

reference/personas.md

AGENTS.md

AGENTS.md

**Jordan (First-Timer)**: Icon-only nav in sidebar. Technical jargon in error messages ("404 Not Found"). No visible help. ⚠ Will abandon at step 2.

must-54e41674-5

Be specific — name the exact elements and interactions that fail each persona. Don't write generic persona descriptions; write what broke for them.

must-54e41674-6

- Don't soften criticism — developers need honest feedback to ship great design

must-54e41674-7

Ask questions along these lines (adapt to the specific findings — do NOT ask generic questions):

must-54e41674-8

1. **Priority direction**: Based on the issues found, ask which category matters most to the user right now. For example: "I found problems with visual hierarchy, color usage, and information overload. Which area should we tackle first?" Offer the top 2–3 issue categories as options.

must-54e41674-9

2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer/bolder/more playful?" Offer 2–3 tonal directions as options based on what would fix the issues found.

must-54e41674-10

4. **Constraints** (optional — only ask if relevant): If the findings touch many areas, ask if anything is off-limits. For example: "Should any sections stay as-is?" This prevents the plan from touching things the user considers done.

must-54e41674-11

- Every question must reference specific findings from Phase 2 — never ask generic "who is your audience?" questions

must-54e41674-12

- Each item's description should carry enough context that the command knows what to focus on

must-54e41674-13


**Reviewing the loading order**

I need to establish a sequence to load my skills: starting with the caveman, then moving to frontend design, and potentially teaching impeccable skills. Frontend design requires context from 'AGENTS.md', so I should check there first. It looks like 'AGENTS.md' exists. Since the frontend design protocol wants to examine 'Design Context', I need to ensure that context is available. However, for the immediate task, I just need to choose which skills to load, focusing on UX, accessibility, and performance issues.

**Determining load sequence**

I need to choose the right order for loading skills. I’ll start with the caveman for communication, then load frontend-design to gather context. Including critique and audit is essential, with audit focusing on accessibility and performance issues. So, the sequence should be: 1) caveman, 2) frontend-design for context, 3) critique for UX review, and 4) audit for technical checks. It looks like this order will help me ensure everything is covered thoroughly while keeping it efficient!

**Defining skills and order**

Skills: caveman, frontend-design, critique, audit.
Order: caveman -> frontend-design -> critique -> audit.
Why: Caveman ensures concise output; frontend-design gathers essential design context to prevent errors; critique assesses UX; audit checks for accessibility and performance issues. This structure supports clarity while following project guidelines!

**Confirming skills and order**

Skills: caveman, frontend-design, critique, audit.
Order: caveman -> frontend-design -> critique -> audit.
Why: Caveman ensures concise output; frontend-design gathers necessary design context to avoid errors; critique evaluates the UX of the checkout flow; audit flags any accessibility and performance issues. Brevity is a key focus here, as suggested by the project guidelines!

**Crafting concise output**

Skills: caveman, frontend-design, critique, audit.
Order: caveman, frontend-design, critique, audit.
Why: Caveman ensures terse communication; frontend-design provides necessary context and prevents errors; critique evaluates the UX of the checkout flow; audit focuses on deep accessibility and performance diagnostics. This format keeps everything clear and concise, meeting the project requirements perfectly!


---
name: teach-impeccable
description: One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
---

Gather design context for this project, then persist it for all future sessions.

## Step 1: Explore the Codebase

Before asking questions, thoroughly scan the project to discover what you can:

- **README and docs**: Project purpose, target audience, any stated goals
- **Package.json / config files**: Tech stack, dependencies, existing design libraries
- **Existing components**: Current design patterns, spacing, typography in use
- **Brand assets**: Logos, favicons, color values already defined
- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales
- **Any style guides or brand documentation**

Note what you've learned and what remains unclear.

## Step 2: Ask UX-Focused Questions

ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:

### Users & Purpose
- Who uses this? What's their context when using it?
- What job are they trying to get done?
- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)

### Brand & Personality
- How would you describe the brand personality in 3 words?
- Any reference sites or apps that capture the right feel? What specifically about them?
- What should this explicitly NOT look like? Any anti-references?

### Aesthetic Preferences
- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
- Light mode, dark mode, or both?
- Any colors that must be used or avoided?

### Accessibility & Inclusion
- Specific accessibility requirements? (WCAG level, known user needs)
- Considerations for reduced motion, color blindness, or other accommodations?

Skip questions where the answer is already clear from the codebase exploration.

## Step 3: Write Design Context

Synthesize your findings and the user's answers into a `## Design Context` section:

```markdown
## Design Context

### Users
[Who they are, their context, the job to be done]

### Brand Personality
[Voice, tone, 3-word personality, emotional goals]

### Aesthetic Direction
[Visual tone, references, anti-references, theme]

### Design Principles
[3-5 principles derived from the conversation that should guide all design decisions]
```

Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place.

Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well.

Confirm completion and summarize the key design principles that will now guide all future work.


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md

must-5e1881d9-0

must-5e1881d9-1

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

- **Missing ARIA**: Interactive elements without proper roles, labels, or states

- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps

- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons

- **Alt text**: Missing or poor image descriptions

- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change

- **Render performance**: Unnecessary re-renders, missing memoization

- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme

must-5e1881d9-2

- **Theme switching issues**: Values that don't update on theme change

- **Missing breakpoints**: No mobile/tablet variants

must-5e1881d9-3

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

must-5e1881d9-4

- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

must-5e1881d9-5

- "Hard-coded colors appear in 15+ components, should use design tokens"

must-5e1881d9-6

> You can ask me to run these one at a time, all at once, or in any order you prefer.

NOTICE.md

NOTICE.md

must-41032146-0

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

must-41032146-1

Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work.

must-41032146-2

- **Brand personality/tone**: How should the interface feel?

must-41032146-3

**CRITICAL**: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.

.impeccable.md

.impeccable.md

.impeccable.md

.impeccable.md

must-41032146-4

3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run /teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

reference/typography.md

reference/typography.md

must-41032146-5

**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults

must-41032146-6

**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes

must-41032146-7

**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

reference/color-and-contrast.md

reference/color-and-contrast.md

must-41032146-8

**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead

must-41032146-9

**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature

must-41032146-10

**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds

must-41032146-11

**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful

must-41032146-12

**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

reference/spatial-design.md

reference/spatial-design.md

must-41032146-13

**DON'T**: Wrap everything in cards—not everything needs a container

must-41032146-14

**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy

must-41032146-15

**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly

must-41032146-16

**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent

must-41032146-17

**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed

must-41032146-18

**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous

must-41032146-19

**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully

must-41032146-20

**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional

must-41032146-21

**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful

must-41032146-22

**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output

must-41032146-23

**DON'T**: Use modals unless there's truly no better alternative—modals are lazy

reference/motion-design.md

reference/motion-design.md

must-41032146-24

**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only

must-41032146-25

**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

reference/interaction-design.md

reference/interaction-design.md

must-41032146-26

**DON'T**: Repeat the same information—redundant headers, intros that restate the heading

must-41032146-27

**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters

reference/responsive-design.md

reference/responsive-design.md

must-41032146-28

**DO**: Adapt the interface for different contexts—don't just shrink it

must-41032146-29

**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it

reference/ux-writing.md

reference/ux-writing.md

must-41032146-30

**DON'T**: Repeat information users can already see

must-41032146-31

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

must-41032146-32

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

must-41032146-33

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

must-41032146-34

Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

must-54e41674-0

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what the interface is trying to accomplish.

must-54e41674-1

Review the design against ALL the **DON'T** guidelines in the frontend-design skill — they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.

must-54e41674-2

- Is there visual competition between elements that should have different weights?

reference/cognitive-load.md

reference/cognitive-load.md

- **Run the 8-item cognitive load checklist** from the reference. Report failure count: 0–1 = low (good), 2–3 = moderate, 4+ = critical.

must-54e41674-3

- Does it feel trustworthy, approachable, premium, playful — whatever it should feel?

- **Emotional valleys**: Check for onboarding frustration, error cliffs, feature discovery gaps, or anxiety spikes at high-stakes moments (payment, delete, commit)

must-54e41674-4

- Are there hidden features that should be more visible?

- Error states: Are they helpful and non-blaming?

- Does error copy help users fix the problem?

reference/heuristics-scoring.md

reference/heuristics-scoring.md

| 5 | Error Prevention | ? | |

| 9 | Error Recovery | ? | |

reference/heuristics-scoring.md

reference/heuristics-scoring.md

reference/personas.md

reference/personas.md

AGENTS.md

AGENTS.md

**Jordan (First-Timer)**: Icon-only nav in sidebar. Technical jargon in error messages ("404 Not Found"). No visible help. ⚠ Will abandon at step 2.

must-54e41674-5

Be specific — name the exact elements and interactions that fail each persona. Don't write generic persona descriptions; write what broke for them.

must-54e41674-6

- Don't soften criticism — developers need honest feedback to ship great design

must-54e41674-7

Ask questions along these lines (adapt to the specific findings — do NOT ask generic questions):

must-54e41674-8

1. **Priority direction**: Based on the issues found, ask which category matters most to the user right now. For example: "I found problems with visual hierarchy, color usage, and information overload. Which area should we tackle first?" Offer the top 2–3 issue categories as options.

must-54e41674-9

2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer/bolder/more playful?" Offer 2–3 tonal directions as options based on what would fix the issues found.

must-54e41674-10

4. **Constraints** (optional — only ask if relevant): If the findings touch many areas, ask if anything is off-limits. For example: "Should any sections stay as-is?" This prevents the plan from touching things the user considers done.

must-54e41674-11

- Every question must reference specific findings from Phase 2 — never ask generic "who is your audience?" questions

must-54e41674-12

- Each item's description should carry enough context that the command knows what to focus on

must-54e41674-13

Package.js

Package.js

must-411040d8-0

- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)

must-411040d8-1

- What should this explicitly NOT look like? Any anti-references?

must-411040d8-2

- Any colors that must be used or avoided?

must-411040d8-3

[3-5 principles derived from the conversation that should guide all design decisions]

.impeccable.md

.impeccable.md

AGENTS.md

AGENTS.md


**Choosing frontend skills**

The user wants me to select skills from a specific directory for the frontend. "Teach-impeccable" is a candidate, but I'm deliberating if it must be included. The minimal set was caveman, frontend-design, critique, and audit. To meet the frontend-design requirement, I could include teach-impeccable but run it conditionally. The concise Skills list will show this conditional order: "caveman -> frontend-design (run teach-impeccable if no Design Context) -> critique -> audit."


No files found matching pattern


**Producing concise output**

I need to keep my response concise. Here’s the structure I want to use:

Skills: caveman, frontend-design, teach-impeccable, critique, audit
Order: caveman → frontend-design → critique → audit
Why: frontend-design + teach-impeccable ensure the right context; critique checks UX, and the audit focuses on accessibility & performance; caveman is for concise reporting.

I'll be careful to present the final output with exactly three lines as requested, ensuring there’s nothing extra. Time to finalize!

**Finalizing concise output**

I’m crafting the final text, focusing on brevity:

Skills: caveman, frontend-design, teach-impeccable, critique, audit
Order: caveman → frontend-design (run teach-impeccable if no Design Context) → critique → audit
Why: caveman for terse output; frontend-design + teach-impeccable to gather project context and avoid AI slop; critique to highlight UX issues in the checkout flow; audit to flag accessibility and performance gaps.

I need to focus on clarity while ensuring I've met the user’s requirements accurately. Time to put this together!

Skills: caveman, frontend-design, teach-impeccable, critique, audit
Order: caveman → frontend-design (run teach-impeccable if no Design Context) → critique → audit
Why: caveman for terse reporting; frontend-design+teach-impeccable to capture context and avoid AI-slop; critique for UX checkout review; audit for accessibility + performance diagnostics.


SKILL.md

SKILL.md

adapt/SKILL.md

adapt/SKILL.md

animate/SKILL.md

animate/SKILL.md

arrange/SKILL.md

arrange/SKILL.md

audit/SKILL.md

audit/SKILL.md

bolder/SKILL.md

bolder/SKILL.md

clarify/SKILL.md

clarify/SKILL.md

colorize/SKILL.md

colorize/SKILL.md

critique/SKILL.md

critique/SKILL.md

delight/SKILL.md

delight/SKILL.md

distill/SKILL.md

distill/SKILL.md

extract/SKILL.md

extract/SKILL.md

frontend-design/SKILL.md

frontend-design/SKILL.md

harden/SKILL.md

harden/SKILL.md

normalize/SKILL.md

normalize/SKILL.md

onboard/SKILL.md

onboard/SKILL.md

optimize/SKILL.md

optimize/SKILL.md

overdrive/SKILL.md

overdrive/SKILL.md

polish/SKILL.md

polish/SKILL.md

quieter/SKILL.md

quieter/SKILL.md

teach-impeccable/SKILL.md

teach-impeccable/SKILL.md

typeset/SKILL.md

typeset/SKILL.md

must-5e1881d9-0

must-5e1881d9-1

Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

- **Missing ARIA**: Interactive elements without proper roles, labels, or states

- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps

- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons

- **Alt text**: Missing or poor image descriptions

- **Form issues**: Inputs without labels, poor error messaging, missing required indicators

- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change

- **Render performance**: Unnecessary re-renders, missing memoization

- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme

must-5e1881d9-2

- **Theme switching issues**: Values that don't update on theme change

- **Missing breakpoints**: No mobile/tablet variants

must-5e1881d9-3

Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).

must-5e1881d9-4

- **Suggested command**: Which command to use (prefer: /animate, /quieter, /optimize, /adapt, /clarify, /distill, /delight, /onboard, /normalize, /audit, /harden, /polish, /extract, /bolder, /arrange, /typeset, /critique, /colorize, /overdrive)

must-5e1881d9-5

- "Hard-coded colors appear in 15+ components, should use design tokens"

must-5e1881d9-6

> You can ask me to run these one at a time, all at once, or in any order you prefer.

NOTICE.md

NOTICE.md

must-41032146-0

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

must-41032146-1

Design skills produce generic output without project context. You MUST have confirmed design context before doing any design work.

must-41032146-2

- **Brand personality/tone**: How should the interface feel?

must-41032146-3

**CRITICAL**: You cannot infer this context by reading the codebase. Code tells you what was built, not who it's for or what it should feel like. Only the creator can provide this context.

.impeccable.md

.impeccable.md

.impeccable.md

.impeccable.md

must-41032146-4

3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run /teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

reference/typography.md

reference/typography.md

must-41032146-5

**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults

must-41032146-6

**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes

must-41032146-7

**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

reference/color-and-contrast.md

reference/color-and-contrast.md

must-41032146-8

**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead

must-41032146-9

**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature

must-41032146-10

**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds

must-41032146-11

**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful

must-41032146-12

**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

reference/spatial-design.md

reference/spatial-design.md

must-41032146-13

**DON'T**: Wrap everything in cards—not everything needs a container

must-41032146-14

**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy

must-41032146-15

**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly

must-41032146-16

**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent

must-41032146-17

**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed

must-41032146-18

**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous

must-41032146-19

**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully

must-41032146-20

**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional

must-41032146-21

**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful

must-41032146-22

**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output

must-41032146-23

**DON'T**: Use modals unless there's truly no better alternative—modals are lazy

reference/motion-design.md

reference/motion-design.md

must-41032146-24

**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only

must-41032146-25

**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

reference/interaction-design.md

reference/interaction-design.md

must-41032146-26

**DON'T**: Repeat the same information—redundant headers, intros that restate the heading

must-41032146-27

**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters

reference/responsive-design.md

reference/responsive-design.md

must-41032146-28

**DO**: Adapt the interface for different contexts—don't just shrink it

must-41032146-29

**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it

reference/ux-writing.md

reference/ux-writing.md

must-41032146-30

**DON'T**: Repeat information users can already see

must-41032146-31

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

must-41032146-32

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

must-41032146-33

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

must-41032146-34

Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

must-54e41674-0

Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: what the interface is trying to accomplish.

must-54e41674-1

Review the design against ALL the **DON'T** guidelines in the frontend-design skill — they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.

must-54e41674-2

- Is there visual competition between elements that should have different weights?

reference/cognitive-load.md

reference/cognitive-load.md

- **Run the 8-item cognitive load checklist** from the reference. Report failure count: 0–1 = low (good), 2–3 = moderate, 4+ = critical.

must-54e41674-3

- Does it feel trustworthy, approachable, premium, playful — whatever it should feel?

- **Emotional valleys**: Check for onboarding frustration, error cliffs, feature discovery gaps, or anxiety spikes at high-stakes moments (payment, delete, commit)

must-54e41674-4

- Are there hidden features that should be more visible?

- Error states: Are they helpful and non-blaming?

- Does error copy help users fix the problem?

reference/heuristics-scoring.md

reference/heuristics-scoring.md

| 5 | Error Prevention | ? | |

| 9 | Error Recovery | ? | |

reference/heuristics-scoring.md

reference/heuristics-scoring.md

reference/personas.md

reference/personas.md

AGENTS.md

AGENTS.md

**Jordan (First-Timer)**: Icon-only nav in sidebar. Technical jargon in error messages ("404 Not Found"). No visible help. ⚠ Will abandon at step 2.

must-54e41674-5

Be specific — name the exact elements and interactions that fail each persona. Don't write generic persona descriptions; write what broke for them.

must-54e41674-6

- Don't soften criticism — developers need honest feedback to ship great design

must-54e41674-7

Ask questions along these lines (adapt to the specific findings — do NOT ask generic questions):

must-54e41674-8

1. **Priority direction**: Based on the issues found, ask which category matters most to the user right now. For example: "I found problems with visual hierarchy, color usage, and information overload. Which area should we tackle first?" Offer the top 2–3 issue categories as options.

must-54e41674-9

2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer/bolder/more playful?" Offer 2–3 tonal directions as options based on what would fix the issues found.

must-54e41674-10

4. **Constraints** (optional — only ask if relevant): If the findings touch many areas, ask if anything is off-limits. For example: "Should any sections stay as-is?" This prevents the plan from touching things the user considers done.

must-54e41674-11

- Every question must reference specific findings from Phase 2 — never ask generic "who is your audience?" questions

must-54e41674-12

- Each item's description should carry enough context that the command knows what to focus on

must-54e41674-13

Package.js

Package.js

must-411040d8-0

- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)

must-411040d8-1

- What should this explicitly NOT look like? Any anti-references?

must-411040d8-2

- Any colors that must be used or avoided?

must-411040d8-3

[3-5 principles derived from the conversation that should guide all design decisions]

.impeccable.md

.impeccable.md

AGENTS.md

AGENTS.md

must-d9cc235e-0

Why: caveman for terse reporting; frontend-design+teach-impeccable to capture context and avoid AI-slop; critique for UX checkout review; audit for accessibility + performance diagnostics.