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: "Make this dashboard feel more alive with subtle hover states and a bit more personality, but don't go overboard." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...


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


must-09564fec-0

AGENTS.md

AGENTS.md

SKILL.md

SKILL.md


**Considering relevant skills**

I’ve got a bunch of skills to consider, like animate, delight, polish, and frontend-design. For making the dashboard feel lively, the animate skill is crucial for hover states, while polish or delight could add some personality, but I need to keep it subtle. The project notes say I must also load the caveman skill every time, plus one or two others like animate or polish. Let’s summarize: Skills: animate, polish, caveman.\nOrder: 1, 2, 3.\nWhy: to enhance user interaction effectively while keeping it balanced.

**Choosing skills for the dashboard**

The user is looking for a solution that features subtle hover states with a touch of personality, without going overboard. I think I need to include the animate skill for hover states, and perhaps delight to add personality. I also must include the caveman skill each time. So, I have a few options: either “caveman, animate, polish” for refinement, or “caveman, animate, delight” for more personality. I’ll lean toward the combination of caveman, animate, and delight to best fit the user's request.

**Selecting skills from the directory**

The AGENTS.md mentions various available skills, including caveman and writing-skills. I need to ensure the relevant directories exist, and both animate and delight do, along with polish. The user wants subtle hover states with some personality but also restraint. So, I think I should select animate for hover effects, potentially delight for balance, and polish for subtlety. Since I always have to load caveman, I’d suggest the order: caveman, animate, delight to meet the user’s needs effectively.


---
name: animate
description: Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.
---

Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.

## 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: performance constraints.

---

## Assess Animation Opportunities

Analyze where motion would improve the experience:

1. **Identify static areas**:
   - **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)
   - **Jarring transitions**: Instant state changes that feel abrupt (show/hide, page loads, route changes)
   - **Unclear relationships**: Spatial or hierarchical relationships that aren't obvious
   - **Lack of delight**: Functional but joyless interactions
   - **Missed guidance**: Opportunities to direct attention or explain behavior

2. **Understand the context**:
   - What's the personality? (Playful vs serious, energetic vs calm)
   - What's the performance budget? (Mobile-first? Complex page?)
   - Who's the audience? (Motion-sensitive users? Power users who want speed?)
   - What matters most? (One hero animation vs many micro-interactions?)

If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.

**CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them.

## Plan Animation Strategy

Create a purposeful animation plan:

- **Hero moment**: What's the ONE signature animation? (Page load? Hero section? Key interaction?)
- **Feedback layer**: Which interactions need acknowledgment?
- **Transition layer**: Which state changes need smoothing?
- **Delight layer**: Where can we surprise and delight?

**IMPORTANT**: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments.

## Implement Animations

Add motion systematically across these categories:

### Entrance Animations
- **Page load choreography**: Stagger element reveals (100-150ms delays), fade + slide combinations
- **Hero section**: Dramatic entrance for primary content (scale, parallax, or creative effects)
- **Content reveals**: Scroll-triggered animations using intersection observer
- **Modal/drawer entry**: Smooth slide + fade, backdrop fade, focus management

### Micro-interactions
- **Button feedback**:
  - Hover: Subtle scale (1.02-1.05), color shift, shadow increase
  - Click: Quick scale down then up (0.95 → 1), ripple effect
  - Loading: Spinner or pulse state
- **Form interactions**:
  - Input focus: Border color transition, slight scale or glow
  - Validation: Shake on error, check mark on success, smooth color transitions
- **Toggle switches**: Smooth slide + color transition (200-300ms)
- **Checkboxes/radio**: Check mark animation, ripple effect
- **Like/favorite**: Scale + rotation, particle effects, color transition

### State Transitions
- **Show/hide**: Fade + slide (not instant), appropriate timing (200-300ms)
- **Expand/collapse**: Height transition with overflow handling, icon rotation
- **Loading states**: Skeleton screen fades, spinner animations, progress bars
- **Success/error**: Color transitions, icon animations, gentle scale pulse
- **Enable/disable**: Opacity transitions, cursor changes

### Navigation & Flow
- **Page transitions**: Crossfade between routes, shared element transitions
- **Tab switching**: Slide indicator, content fade/slide
- **Carousel/slider**: Smooth transforms, snap points, momentum
- **Scroll effects**: Parallax layers, sticky headers with state changes, scroll progress indicators

### Feedback & Guidance
- **Hover hints**: Tooltip fade-ins, cursor changes, element highlights
- **Drag & drop**: Lift effect (shadow + scale), drop zone highlights, smooth repositioning
- **Copy/paste**: Brief highlight flash on paste, "copied" confirmation
- **Focus flow**: Highlight path through form or workflow

### Delight Moments
- **Empty states**: Subtle floating animations on illustrations
- **Completed actions**: Confetti, check mark flourish, success celebrations
- **Easter eggs**: Hidden interactions for discovery
- **Contextual animation**: Weather effects, time-of-day themes, seasonal touches

## Technical Implementation

Use appropriate techniques for each animation:

### Timing & Easing

**Durations by purpose:**
- **100-150ms**: Instant feedback (button press, toggle)
- **200-300ms**: State changes (hover, menu open)
- **300-500ms**: Layout changes (accordion, modal)
- **500-800ms**: Entrance animations (page load)

**Easing curves (use these, not CSS defaults):**
```css
/* Recommended - natural deceleration */
--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1);    /* Smooth, refined */
--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1);   /* Slightly snappier */
--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1);     /* Confident, decisive */

/* AVOID - feel dated and tacky */
/* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); */
/* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); */
```

**Exit animations are faster than entrances.** Use ~75% of enter duration.

### CSS Animations
```css
/* Prefer for simple, declarative animations */
- transitions for state changes
- @keyframes for complex sequences
- transform + opacity only (GPU-accelerated)
```

### JavaScript Animation
```javascript
/* Use for complex, interactive animations */
- Web Animations API for programmatic control
- Framer Motion for React
- GSAP for complex sequences
```

### Performance
- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties
- **will-change**: Add sparingly for known expensive animations
- **Reduce paint**: Minimize repaints, use `contain` where appropriate
- **Monitor FPS**: Ensure 60fps on target devices

### Accessibility
```css
@media (prefers-reduced-motion: reduce) {
  * {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
  }
}
```

**NEVER**:
- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself
- Animate layout properties (width, height, top, left)—use transform instead
- Use durations over 500ms for feedback—it feels laggy
- Animate without purpose—every animation needs a reason
- Ignore `prefers-reduced-motion`—this is an accessibility violation
- Animate everything—animation fatigue makes interfaces feel exhausting
- Block interaction during animations unless intentional

## Verify Quality

Test animations thoroughly:

- **Smooth at 60fps**: No jank on target devices
- **Feels natural**: Easing curves feel organic, not robotic
- **Appropriate timing**: Not too fast (jarring) or too slow (laggy)
- **Reduced motion works**: Animations disabled or simplified appropriately
- **Doesn't block**: Users can interact during/after animations
- **Adds value**: Makes interface clearer or more delightful

Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.


must-09564fec-0

AGENTS.md

AGENTS.md

SKILL.md

SKILL.md

must-ae5a86ac-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: performance constraints.

- **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)

- Validation: Shake on error, check mark on success, smooth color transitions

- **Success/error**: Color transitions, icon animations, gentle scale pulse

must-ae5a86ac-1

/* AVOID - feel dated and tacky */

must-ae5a86ac-2

/* Prefer for simple, declarative animations */

must-ae5a86ac-3

- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties

must-ae5a86ac-4

Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.


---
name: delight
description: Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.
---

Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences.

## 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's appropriate for the domain (playful vs professional vs quirky vs elegant).

---

## Assess Delight Opportunities

Identify where delight would enhance (not distract from) the experience:

1. **Find natural delight moments**:
   - **Success states**: Completed actions (save, send, publish)
   - **Empty states**: First-time experiences, onboarding
   - **Loading states**: Waiting periods that could be entertaining
   - **Achievements**: Milestones, streaks, completions
   - **Interactions**: Hover states, clicks, drags
   - **Errors**: Softening frustrating moments
   - **Easter eggs**: Hidden discoveries for curious users

2. **Understand the context**:
   - What's the brand personality? (Playful? Professional? Quirky? Elegant?)
   - Who's the audience? (Tech-savvy? Creative? Corporate?)
   - What's the emotional context? (Accomplishment? Exploration? Frustration?)
   - What's appropriate? (Banking app ≠ gaming app)

3. **Define delight strategy**:
   - **Subtle sophistication**: Refined micro-interactions (luxury brands)
   - **Playful personality**: Whimsical illustrations and copy (consumer apps)
   - **Helpful surprises**: Anticipating needs before users ask (productivity tools)
   - **Sensory richness**: Satisfying sounds, smooth animations (creative tools)

If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.

**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.

## Delight Principles

Follow these guidelines:

### Delight Amplifies, Never Blocks
- Delight moments should be quick (< 1 second)
- Never delay core functionality for delight
- Make delight skippable or subtle
- Respect user's time and task focus

### Surprise and Discovery
- Hide delightful details for users to discover
- Reward exploration and curiosity
- Don't announce every delight moment
- Let users share discoveries with others

### Appropriate to Context
- Match delight to emotional moment (celebrate success, empathize with errors)
- Respect the user's state (don't be playful during critical errors)
- Match brand personality and audience expectations
- Cultural sensitivity (what's delightful varies by culture)

### Compound Over Time
- Delight should remain fresh with repeated use
- Vary responses (not same animation every time)
- Reveal deeper layers with continued use
- Build anticipation through patterns

## Delight Techniques

Add personality and joy through these methods:

### Micro-interactions & Animation

**Button delight**:
```css
/* Satisfying button press */
.button {
  transition: transform 0.1s, box-shadow 0.1s;
}
.button:active {
  transform: translateY(2px);
  box-shadow: 0 2px 4px rgba(0,0,0,0.2);
}

/* Ripple effect on click */
/* Smooth lift on hover */
.button:hover {
  transform: translateY(-2px);
  transition: transform 0.2s cubic-bezier(0.25, 1, 0.5, 1); /* ease-out-quart */
}
```

**Loading delight**:
- Playful loading animations (not just spinners)
- Personality in loading messages (write product-specific ones, not generic AI filler)
- Progress indication with encouraging messages
- Skeleton screens with subtle animations

**Success animations**:
- Checkmark draw animation
- Confetti burst for major achievements
- Gentle scale + fade for confirmation
- Satisfying sound effects (subtle)

**Hover surprises**:
- Icons that animate on hover
- Color shifts or glow effects
- Tooltip reveals with personality
- Cursor changes (custom cursors for branded experiences)

### Personality in Copy

**Playful error messages**:
```
"Error 404"
"This page is playing hide and seek. (And winning)"

"Connection failed"
"Looks like the internet took a coffee break. Want to retry?"
```

**Encouraging empty states**:
```
"No projects"
"Your canvas awaits. Create something amazing."

"No messages"
"Inbox zero! You're crushing it today."
```

**Playful labels & tooltips**:
```
"Delete"
"Send to void" (for playful brand)

"Help"
"Rescue me" (tooltip)
```

**IMPORTANT**: Match copy personality to brand. Banks shouldn't be wacky, but they can be warm.

### Illustrations & Visual Personality

**Custom illustrations**:
- Empty state illustrations (not stock icons)
- Error state illustrations (friendly monsters, quirky characters)
- Loading state illustrations (animated characters)
- Success state illustrations (celebrations)

**Icon personality**:
- Custom icon set matching brand personality
- Animated icons (subtle motion on hover/click)
- Illustrative icons (more detailed than generic)
- Consistent style across all icons

**Background effects**:
- Subtle particle effects
- Gradient mesh backgrounds
- Geometric patterns
- Parallax depth
- Time-of-day themes (morning vs night)

### Satisfying Interactions

**Drag and drop delight**:
- Lift effect on drag (shadow, scale)
- Snap animation when dropped
- Satisfying placement sound
- Undo toast ("Dropped in wrong place? [Undo]")

**Toggle switches**:
- Smooth slide with spring physics
- Color transition
- Haptic feedback on mobile
- Optional sound effect

**Progress & achievements**:
- Streak counters with celebratory milestones
- Progress bars that "celebrate" at 100%
- Badge unlocks with animation
- Playful stats ("You're on fire! 5 days in a row")

**Form interactions**:
- Input fields that animate on focus
- Checkboxes with a satisfying scale pulse when checked
- Success state that celebrates valid input
- Auto-grow textareas

### Sound Design

**Subtle audio cues** (when appropriate):
- Notification sounds (distinctive but not annoying)
- Success sounds (satisfying "ding")
- Error sounds (empathetic, not harsh)
- Typing sounds for chat/messaging
- Ambient background audio (very subtle)

**IMPORTANT**:
- Respect system sound settings
- Provide mute option
- Keep volumes quiet (subtle cues, not alarms)
- Don't play on every interaction (sound fatigue is real)

### Easter Eggs & Hidden Delights

**Discovery rewards**:
- Konami code unlocks special theme
- Hidden keyboard shortcuts (Cmd+K for special features)
- Hover reveals on logos or illustrations
- Alt text jokes on images (for screen reader users too!)
- Console messages for developers ("Like what you see? We're hiring!")

**Seasonal touches**:
- Holiday themes (subtle, tasteful)
- Seasonal color shifts
- Weather-based variations
- Time-based changes (dark at night, light during day)

**Contextual personality**:
- Different messages based on time of day
- Responses to specific user actions
- Randomized variations (not same every time)
- Progressive reveals with continued use

### Loading & Waiting States

**Make waiting engaging**:
- Interesting loading messages that rotate
- Progress bars with personality
- Mini-games during long loads
- Fun facts or tips while waiting
- Countdown with encouraging messages

```
Loading messages — write ones specific to your product, not generic AI filler:
- "Crunching your latest numbers..."
- "Syncing with your team's changes..."
- "Preparing your dashboard..."
- "Checking for updates since yesterday..."
```

**WARNING**: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy — instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.

### Celebration Moments

**Success celebrations**:
- Confetti for major milestones
- Animated checkmarks for completions
- Progress bar celebrations at 100%
- "Achievement unlocked" style notifications
- Personalized messages ("You published your 10th article!")

**Milestone recognition**:
- First-time actions get special treatment
- Streak tracking and celebration
- Progress toward goals
- Anniversary celebrations

## Implementation Patterns

**Animation libraries**:
- Framer Motion (React)
- GSAP (universal)
- Lottie (After Effects animations)
- Canvas confetti (party effects)

**Sound libraries**:
- Howler.js (audio management)
- Use-sound (React hook)

**Physics libraries**:
- React Spring (spring physics)
- Popmotion (animation primitives)

**IMPORTANT**: File size matters. Compress images, optimize animations, lazy load delight features.

**NEVER**:
- Delay core functionality for delight
- Force users through delightful moments (make skippable)
- Use delight to hide poor UX
- Overdo it (less is more)
- Ignore accessibility (animate responsibly, provide alternatives)
- Make every interaction delightful (special moments should be special)
- Sacrifice performance for delight
- Be inappropriate for context (read the room)

## Verify Delight Quality

Test that delight actually delights:

- **User reactions**: Do users smile? Share screenshots?
- **Doesn't annoy**: Still pleasant after 100th time?
- **Doesn't block**: Can users opt out or skip?
- **Performant**: No jank, no slowdown
- **Appropriate**: Matches brand and context
- **Accessible**: Works with reduced motion, screen readers

Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct.


must-09564fec-0

AGENTS.md

AGENTS.md

SKILL.md

SKILL.md

must-ae5a86ac-0

must-ae5a86ac-1

/* AVOID - feel dated and tacky */

must-ae5a86ac-2

must-ae5a86ac-3

must-ae5a86ac-4

must-1bba0795-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's appropriate for the domain (playful vs professional vs quirky vs elegant).

must-1bba0795-1

**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.

must-1bba0795-2

- Delight moments should be quick (< 1 second)

must-1bba0795-3

- Don't announce every delight moment

must-1bba0795-4

- Respect the user's state (don't be playful during critical errors)

must-1bba0795-5

- Delight should remain fresh with repeated use

open-question-1bba0795-0

**Playful error messages**:

open-question-1bba0795-1

"Error 404"

open-question-1bba0795-2

"Connection failed"

open-question-1bba0795-3

- Error state illustrations (friendly monsters, quirky characters)

open-question-1bba0795-4

- Error sounds (empathetic, not harsh)

must-1bba0795-6

- Don't play on every interaction (sound fatigue is real)

must-1bba0795-7

**WARNING**: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy — instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.

Howler.js

Howler.js

must-1bba0795-8

- Make every interaction delightful (special moments should be special)

must-1bba0795-9

Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct.


---
name: polish
description: Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
---

## 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: quality bar (MVP vs flagship).

---

Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished.

## Pre-Polish Assessment

Understand the current state and goals:

1. **Review completeness**:
   - Is it functionally complete?
   - Are there known issues to preserve (mark with TODOs)?
   - What's the quality bar? (MVP vs flagship feature?)
   - When does it ship? (How much time for polish?)

2. **Identify polish areas**:
   - Visual inconsistencies
   - Spacing and alignment issues
   - Interaction state gaps
   - Copy inconsistencies
   - Edge cases and error states
   - Loading and transition smoothness

**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete.

## Polish Systematically

Work through these dimensions methodically:

### Visual Alignment & Spacing

- **Pixel-perfect alignment**: Everything lines up to grid
- **Consistent spacing**: All gaps use spacing scale (no random 13px gaps)
- **Optical alignment**: Adjust for visual weight (icons may need offset for optical centering)
- **Responsive consistency**: Spacing and alignment work at all breakpoints
- **Grid adherence**: Elements snap to baseline grid

**Check**:
- Enable grid overlay and verify alignment
- Check spacing with browser inspector
- Test at multiple viewport sizes
- Look for elements that "feel" off

### Typography Refinement

- **Hierarchy consistency**: Same elements use same sizes/weights throughout
- **Line length**: 45-75 characters for body text
- **Line height**: Appropriate for font size and context
- **Widows & orphans**: No single words on last line
- **Hyphenation**: Appropriate for language and column width
- **Kerning**: Adjust letter spacing where needed (especially headlines)
- **Font loading**: No FOUT/FOIT flashes

### Color & Contrast

- **Contrast ratios**: All text meets WCAG standards
- **Consistent token usage**: No hard-coded colors, all use design tokens
- **Theme consistency**: Works in all theme variants
- **Color meaning**: Same colors mean same things throughout
- **Accessible focus**: Focus indicators visible with sufficient contrast
- **Tinted neutrals**: No pure gray or pure black—add subtle color tint (0.01 chroma)
- **Gray on color**: Never put gray text on colored backgrounds—use a shade of that color or transparency

### Interaction States

Every interactive element needs all states:

- **Default**: Resting state
- **Hover**: Subtle feedback (color, scale, shadow)
- **Focus**: Keyboard focus indicator (never remove without replacement)
- **Active**: Click/tap feedback
- **Disabled**: Clearly non-interactive
- **Loading**: Async action feedback
- **Error**: Validation or error state
- **Success**: Successful completion

**Missing states create confusion and broken experiences**.

### Micro-interactions & Transitions

- **Smooth transitions**: All state changes animated appropriately (150-300ms)
- **Consistent easing**: Use ease-out-quart/quint/expo for natural deceleration. Never bounce or elastic—they feel dated.
- **No jank**: 60fps animations, only animate transform and opacity
- **Appropriate motion**: Motion serves purpose, not decoration
- **Reduced motion**: Respects `prefers-reduced-motion`

### Content & Copy

- **Consistent terminology**: Same things called same names throughout
- **Consistent capitalization**: Title Case vs Sentence case applied consistently
- **Grammar & spelling**: No typos
- **Appropriate length**: Not too wordy, not too terse
- **Punctuation consistency**: Periods on sentences, not on labels (unless all labels have them)

### Icons & Images

- **Consistent style**: All icons from same family or matching style
- **Appropriate sizing**: Icons sized consistently for context
- **Proper alignment**: Icons align with adjacent text optically
- **Alt text**: All images have descriptive alt text
- **Loading states**: Images don't cause layout shift, proper aspect ratios
- **Retina support**: 2x assets for high-DPI screens

### Forms & Inputs

- **Label consistency**: All inputs properly labeled
- **Required indicators**: Clear and consistent
- **Error messages**: Helpful and consistent
- **Tab order**: Logical keyboard navigation
- **Auto-focus**: Appropriate (don't overuse)
- **Validation timing**: Consistent (on blur vs on submit)

### Edge Cases & Error States

- **Loading states**: All async actions have loading feedback
- **Empty states**: Helpful empty states, not just blank space
- **Error states**: Clear error messages with recovery paths
- **Success states**: Confirmation of successful actions
- **Long content**: Handles very long names, descriptions, etc.
- **No content**: Handles missing data gracefully
- **Offline**: Appropriate offline handling (if applicable)

### Responsiveness

- **All breakpoints**: Test mobile, tablet, desktop
- **Touch targets**: 44x44px minimum on touch devices
- **Readable text**: No text smaller than 14px on mobile
- **No horizontal scroll**: Content fits viewport
- **Appropriate reflow**: Content adapts logically

### Performance

- **Fast initial load**: Optimize critical path
- **No layout shift**: Elements don't jump after load (CLS)
- **Smooth interactions**: No lag or jank
- **Optimized images**: Appropriate formats and sizes
- **Lazy loading**: Off-screen content loads lazily

### Code Quality

- **Remove console logs**: No debug logging in production
- **Remove commented code**: Clean up dead code
- **Remove unused imports**: Clean up unused dependencies
- **Consistent naming**: Variables and functions follow conventions
- **Type safety**: No TypeScript `any` or ignored errors
- **Accessibility**: Proper ARIA labels and semantic HTML

## Polish Checklist

Go through systematically:

- [ ] Visual alignment perfect at all breakpoints
- [ ] Spacing uses design tokens consistently
- [ ] Typography hierarchy consistent
- [ ] All interactive states implemented
- [ ] All transitions smooth (60fps)
- [ ] Copy is consistent and polished
- [ ] Icons are consistent and properly sized
- [ ] All forms properly labeled and validated
- [ ] Error states are helpful
- [ ] Loading states are clear
- [ ] Empty states are welcoming
- [ ] Touch targets are 44x44px minimum
- [ ] Contrast ratios meet WCAG AA
- [ ] Keyboard navigation works
- [ ] Focus indicators visible
- [ ] No console errors or warnings
- [ ] No layout shift on load
- [ ] Works in all supported browsers
- [ ] Respects reduced motion preference
- [ ] Code is clean (no TODOs, console.logs, commented code)

**IMPORTANT**: Polish is about details. Zoom in. Squint at it. Use it yourself. The little things add up.

**NEVER**:
- Polish before it's functionally complete
- Spend hours on polish if it ships in 30 minutes (triage)
- Introduce bugs while polishing (test thoroughly)
- Ignore systematic issues (if spacing is off everywhere, fix the system)
- Perfect one thing while leaving others rough (consistent quality level)

## Final Verification

Before marking as done:

- **Use it yourself**: Actually interact with the feature
- **Test on real devices**: Not just browser DevTools
- **Ask someone else to review**: Fresh eyes catch things
- **Compare to design**: Match intended design
- **Check all states**: Don't just test happy path

Remember: You have impeccable attention to detail and exquisite taste. Polish until it feels effortless, looks intentional, and works flawlessly. Sweat the details - they matter.


must-09564fec-0

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: "Make this dashboard feel more alive with subtle hover states and a bit more personality, but don't go overboard." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

AGENTS.md

AGENTS.md

SKILL.md

SKILL.md

must-ae5a86ac-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: performance constraints.

- **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)

- Validation: Shake on error, check mark on success, smooth color transitions

- **Success/error**: Color transitions, icon animations, gentle scale pulse

must-ae5a86ac-1

/* AVOID - feel dated and tacky */

must-ae5a86ac-2

/* Prefer for simple, declarative animations */

must-ae5a86ac-3

- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties

must-ae5a86ac-4

Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.

must-1bba0795-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's appropriate for the domain (playful vs professional vs quirky vs elegant).

must-1bba0795-1

**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.

must-1bba0795-2

- Delight moments should be quick (< 1 second)

must-1bba0795-3

- Don't announce every delight moment

must-1bba0795-4

- Respect the user's state (don't be playful during critical errors)

must-1bba0795-5

- Delight should remain fresh with repeated use

open-question-1bba0795-0

**Playful error messages**:

open-question-1bba0795-1

"Error 404"

open-question-1bba0795-2

"Connection failed"

open-question-1bba0795-3

- Error state illustrations (friendly monsters, quirky characters)

open-question-1bba0795-4

- Error sounds (empathetic, not harsh)

must-1bba0795-6

- Don't play on every interaction (sound fatigue is real)

must-1bba0795-7

**WARNING**: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy — instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.

Howler.js

Howler.js

must-1bba0795-8

- Make every interaction delightful (special moments should be special)

must-1bba0795-9

Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct.

must-2d98965c-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: quality bar (MVP vs flagship).

- Edge cases and error states

must-2d98965c-1

**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete.

- **Error**: Validation or error state

**Missing states create confusion and broken experiences**.

must-2d98965c-2

- **Loading states**: Images don't cause layout shift, proper aspect ratios

- **Error messages**: Helpful and consistent

must-2d98965c-3

- **Auto-focus**: Appropriate (don't overuse)

- **Error states**: Clear error messages with recovery paths

- **No content**: Handles missing data gracefully

must-2d98965c-4

- **No layout shift**: Elements don't jump after load (CLS)

- [ ] Error states are helpful

must-2d98965c-5

- **Check all states**: Don't just test happy path


**Considering skill priorities**

I need to look at the skills in order: first the caveman for concise responses, then frontend design since prep is necessary. Next is animate for hover effects and micro-interactions, and finally delight for adding personality—but I don’t want to be too verbose about that. There’s also this quality bar to think about, but I don’t believe polish is needed just yet. I should prepare for those skills, keeping in mind that context is essential.

**Evaluating skill inclusion**

I’m pondering whether to include teach-impeccable in the skills list since the user wants me to select from existing frontend skills. While it’s in the directory, I need to follow the constraints closely. It seems my selection should be caveman, frontend-design, animate, and delight. For the ordering, I could specify: "caveman -> frontend-design (run context protocol; if no context, run teach-impeccable) -> animate -> delight". Oh! I can keep the “Why” line concise to fit three lines as requested.

**Establishing skill structure**

I see that animate and delight are relevant skills for this task, and I've got to ensure I invoke frontend-design first, as per the protocol. For the three lines, I’ll format them like this:

First, for skills: “Skills: caveman, frontend-design, animate, delight.” That keeps it simple and aligned with what the user asked for.

Next, for the order, I should probably start with frontend-design since it’s about preparation. So, I'll go with: “Order: frontend-design, caveman, animate, delight.” It still honors the guideline to always load caveman!

**Preparing final responses**

It looks like the order should indeed be "frontend-design -> animate -> delight," while remembering to load caveman too. I’ll list it as preloaded, but I'll still include the sequence.

So, I’ll format it like this: “Order: 1) caveman (auto), 2) frontend-design (run context-gathering; if no context, run teach-impeccable), 3) animate, 4) delight.”

For the justification, I’ll keep it concise: "Why: frontend-design for context & constraints, animate for hover/micro-interactions, delight to add personality, caveman for concise communication."

This’ll all be neatly in three lines, no extra breaks or trailing spaces!

**Confirming skill selection**

So, I’ll stick to using ASCII characters like "->" in a compact way. For the third line, I’ll state: “Why: frontend-design ensures context and performance; animate adds subtle hover effects; delight provides tasteful personality; caveman allows terse communication.”

I must confirm that the caveman skill exists, even if it’s not under the frontend directory. But since the requirement is to always load caveman, I’ll ensure to include it. Ultimately, I’ll structure the output to be concise and fit well within the three prescribed lines.


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


must-09564fec-0

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: "Make this dashboard feel more alive with subtle hover states and a bit more personality, but don't go overboard." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

AGENTS.md

AGENTS.md

SKILL.md

SKILL.md

must-ae5a86ac-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: performance constraints.

- **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)

- Validation: Shake on error, check mark on success, smooth color transitions

- **Success/error**: Color transitions, icon animations, gentle scale pulse

must-ae5a86ac-1

/* AVOID - feel dated and tacky */

must-ae5a86ac-2

/* Prefer for simple, declarative animations */

must-ae5a86ac-3

- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties

must-ae5a86ac-4

Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.

must-1bba0795-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's appropriate for the domain (playful vs professional vs quirky vs elegant).

must-1bba0795-1

**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.

must-1bba0795-2

- Delight moments should be quick (< 1 second)

must-1bba0795-3

- Don't announce every delight moment

must-1bba0795-4

- Respect the user's state (don't be playful during critical errors)

must-1bba0795-5

- Delight should remain fresh with repeated use

open-question-1bba0795-0

**Playful error messages**:

open-question-1bba0795-1

"Error 404"

open-question-1bba0795-2

"Connection failed"

open-question-1bba0795-3

- Error state illustrations (friendly monsters, quirky characters)

open-question-1bba0795-4

- Error sounds (empathetic, not harsh)

must-1bba0795-6

- Don't play on every interaction (sound fatigue is real)

must-1bba0795-7

**WARNING**: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy — instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.

Howler.js

Howler.js

must-1bba0795-8

- Make every interaction delightful (special moments should be special)

must-1bba0795-9

Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct.

must-2d98965c-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: quality bar (MVP vs flagship).

- Edge cases and error states

must-2d98965c-1

**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete.

- **Error**: Validation or error state

**Missing states create confusion and broken experiences**.

must-2d98965c-2

- **Loading states**: Images don't cause layout shift, proper aspect ratios

- **Error messages**: Helpful and consistent

must-2d98965c-3

- **Auto-focus**: Appropriate (don't overuse)

- **Error states**: Clear error messages with recovery paths

- **No content**: Handles missing data gracefully

must-2d98965c-4

- **No layout shift**: Elements don't jump after load (CLS)

- [ ] Error states are helpful

must-2d98965c-5

- **Check all states**: Don't just test happy path

NOTICE.md

NOTICE.md

must-79a91116-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-79a91116-1

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

must-79a91116-2

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

must-79a91116-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-79a91116-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-79a91116-5

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

must-79a91116-6

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

must-79a91116-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-79a91116-8

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

must-79a91116-9

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

must-79a91116-10

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

must-79a91116-11

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

must-79a91116-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-79a91116-13

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

must-79a91116-14

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

must-79a91116-15

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

must-79a91116-16

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

must-79a91116-17

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

must-79a91116-18

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

must-79a91116-19

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

must-79a91116-20

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

must-79a91116-21

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

must-79a91116-22

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

must-79a91116-23

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

reference/motion-design.md

reference/motion-design.md

must-79a91116-24

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

must-79a91116-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-79a91116-26

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

must-79a91116-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-79a91116-28

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

must-79a91116-29

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

reference/ux-writing.md

reference/ux-writing.md

must-79a91116-30

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

must-79a91116-31

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

must-79a91116-32

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

must-79a91116-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-79a91116-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.


**Crafting skill response**

I read the frontend-design SKILL.md, and I’m ready to prepare the three-line response. I'll include "Teach-impeccable" only if there's no context. The order needs to focus on frontend-design first, followed by animate and delight, while caveman is always part of the skills list.

Here’s my minimal output:
Skills: caveman, frontend-design, animate, delight. Order: frontend-design (run context protocol; if no context => teach-impeccable) -> animate -> delight; caveman loaded concurrently. The goal is to ensure a concise and effective interaction.

**Refining skills response**

I'm thinking the response can be shorter while still including all necessary details. Here it is:

Skills: caveman, frontend-design, animate, delight.
Order: frontend-design (context; fallback: teach-impeccable) -> animate -> delight — caveman loaded concurrently.
Why: frontend-design sets constraints and personality; animate adds subtle hover interactions; delight injects restrained personality; caveman ensures terse outputs.

Now, I’m considering that caveman might not be directly in the directory, but including it is essential. I’ll note it as auto-loaded to stay safe!

**Finalizing skills output**

I need to make sure I format this correctly with "Skills: ...\nOrder: ...\nWhy: ...". I'm thinking no trailing spaces or extra newlines are necessary, which is fine. Now, I’ll create my final output while respecting the order for the skills.

Here’s what I’ve crafted:

Skills: caveman, frontend-design, animate, delight.
Order: frontend-design (context; fallback: teach-impeccable) -> animate -> delight — caveman loaded concurrently.
Why: frontend-design captures brand personality and quality; animate adds subtle hover interactions; delight brings in tasteful personality without excess; caveman for terse replies.

I believe this is ready!

Skills: caveman, frontend-design, animate, delight
Order: frontend-design (run context protocol; fallback: teach-impeccable if no context) -> animate -> delight — caveman loaded concurrently
Why: frontend-design is mandatory to capture brand/personality & quality bar; animate implements subtle hover/micro-interactions; delight adds restrained personality; caveman ensures concise communication.