IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Inspect the skill folders if needed. User request: "Build a distinctive onboarding experience for first-time users. It should feel polished and not like generic AI UI." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...


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


must-d0d69e29-0


**Selecting skills for loading**

I need to pick skills from this directory, aiming for three: onboard, delight, and frontend-design. I also see that I must always include the 'caveman' skill, which is a hard requirement. The project's instructions are clear: I have to load caveman, but I should focus on frontend skills. So, in the "Skills: ..." response, I'll include both caveman and the three frontend skills, just to be safe!

**Determining skill order**

I need to check the AGENTS.md instructions, which say to always load the 'caveman' skill first. After that, I’ll select two or three relevant skills like 'onboard', 'delight', and 'frontend-design'. Now, the order is crucial for loading these skills: I'm thinking 'caveman', then maybe 'onboard', followed by 'delight', and lastly 'frontend-design'. However, I'll need to inspect the relevant skill folders for reasoning. So, let's take a look at the 'onboard' SKILL.md file.


---
name: onboard
description: Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.
---

## 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: the "aha moment" you want users to reach, and users' experience level.

---

Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.

## Assess Onboarding Needs

Understand what users need to learn and why:

1. **Identify the challenge**:
   - What are users trying to accomplish?
   - What's confusing or unclear about current experience?
   - Where do users get stuck or drop off?
   - What's the "aha moment" we want users to reach?

2. **Understand the users**:
   - What's their experience level? (Beginners, power users, mixed?)
   - What's their motivation? (Excited and exploring? Required by work?)
   - What's their time commitment? (5 minutes? 30 minutes?)
   - What alternatives do they know? (Coming from competitor? New to category?)

3. **Define success**:
   - What's the minimum users need to learn to be successful?
   - What's the key action we want them to take? (First project? First invite?)
   - How do we know onboarding worked? (Completion rate? Time to value?)

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

## Onboarding Principles

Follow these core principles:

### Show, Don't Tell
- Demonstrate with working examples, not just descriptions
- Provide real functionality in onboarding, not separate tutorial mode
- Use progressive disclosure - teach one thing at a time

### Make It Optional (When Possible)
- Let experienced users skip onboarding
- Don't block access to product
- Provide "Skip" or "I'll explore on my own" options

### Time to Value
- Get users to their "aha moment" ASAP
- Front-load most important concepts
- Teach 20% that delivers 80% of value
- Save advanced features for contextual discovery

### Context Over Ceremony
- Teach features when users need them, not upfront
- Empty states are onboarding opportunities
- Tooltips and hints at point of use

### Respect User Intelligence
- Don't patronize or over-explain
- Be concise and clear
- Assume users can figure out standard patterns

## Design Onboarding Experiences

Create appropriate onboarding for the context:

### Initial Product Onboarding

**Welcome Screen**:
- Clear value proposition (what is this product?)
- What users will learn/accomplish
- Time estimate (honest about commitment)
- Option to skip (for experienced users)

**Account Setup**:
- Minimal required information (collect more later)
- Explain why you're asking for each piece of information
- Smart defaults where possible
- Social login when appropriate

**Core Concept Introduction**:
- Introduce 1-3 core concepts (not everything)
- Use simple language and examples
- Interactive when possible (do, don't just read)
- Progress indication (step 1 of 3)

**First Success**:
- Guide users to accomplish something real
- Pre-populated examples or templates
- Celebrate completion (but don't overdo it)
- Clear next steps

### Feature Discovery & Adoption

**Empty States**:
Instead of blank space, show:
- What will appear here (description + screenshot/illustration)
- Why it's valuable
- Clear CTA to create first item
- Example or template option

Example:
```
No projects yet
Projects help you organize your work and collaborate with your team.
[Create your first project] or [Start from template]
```

**Contextual Tooltips**:
- Appear at relevant moment (first time user sees feature)
- Point directly at relevant UI element
- Brief explanation + benefit
- Dismissable (with "Don't show again" option)
- Optional "Learn more" link

**Feature Announcements**:
- Highlight new features when they're released
- Show what's new and why it matters
- Let users try immediately
- Dismissable

**Progressive Onboarding**:
- Teach features when users encounter them
- Badges or indicators on new/unused features
- Unlock complexity gradually (don't show all options immediately)

### Guided Tours & Walkthroughs

**When to use**:
- Complex interfaces with many features
- Significant changes to existing product
- Industry-specific tools needing domain knowledge

**How to design**:
- Spotlight specific UI elements (dim rest of page)
- Keep steps short (3-7 steps max per tour)
- Allow users to click through tour freely
- Include "Skip tour" option
- Make replayable (help menu)

**Best practices**:
- Interactive > passive (let users click real buttons)
- Focus on workflow, not features ("Create a project" not "This is the project button")
- Provide sample data so actions work

### Interactive Tutorials

**When to use**:
- Users need hands-on practice
- Concepts are complex or unfamiliar
- High stakes (better to practice in safe environment)

**How to design**:
- Sandbox environment with sample data
- Clear objectives ("Create a chart showing sales by region")
- Step-by-step guidance
- Validation (confirm they did it right)
- Graduation moment (you're ready!)

### Documentation & Help

**In-product help**:
- Contextual help links throughout interface
- Keyboard shortcut reference
- Search-able help center
- Video tutorials for complex workflows

**Help patterns**:
- `?` icon near complex features
- "Learn more" links in tooltips
- Keyboard shortcut hints (`⌘K` shown on search box)

## Empty State Design

Every empty state needs:

### What Will Be Here
"Your recent projects will appear here"

### Why It Matters
"Projects help you organize your work and collaborate with your team"

### How to Get Started
[Create project] or [Import from template]

### Visual Interest
Illustration or icon (not just text on blank page)

### Contextual Help
"Need help getting started? [Watch 2-min tutorial]"

**Empty state types**:
- **First use**: Never used this feature (emphasize value, provide template)
- **User cleared**: Intentionally deleted everything (light touch, easy to recreate)
- **No results**: Search or filter returned nothing (suggest different query, clear filters)
- **No permissions**: Can't access (explain why, how to get access)
- **Error state**: Failed to load (explain what happened, retry option)

## Implementation Patterns

### Technical approaches:

**Tooltip libraries**: Tippy.js, Popper.js
**Tour libraries**: Intro.js, Shepherd.js, React Joyride
**Modal patterns**: Focus trap, backdrop, ESC to close
**Progress tracking**: LocalStorage for "seen" states
**Analytics**: Track completion, drop-off points

**Storage patterns**:
```javascript
// Track which onboarding steps user has seen
localStorage.setItem('onboarding-completed', 'true');
localStorage.setItem('feature-tooltip-seen-reports', 'true');
```

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

**NEVER**:
- Force users through long onboarding before they can use product
- Patronize users with obvious explanations
- Show same tooltip repeatedly (respect dismissals)
- Block all UI during tour (let users explore)
- Create separate tutorial mode disconnected from real product
- Overwhelm with information upfront (progressive disclosure!)
- Hide "Skip" or make it hard to find
- Forget about returning users (don't show initial onboarding again)

## Verify Onboarding Quality

Test with real users:

- **Time to completion**: Can users complete onboarding quickly?
- **Comprehension**: Do users understand after completing?
- **Action**: Do users take desired next step?
- **Skip rate**: Are too many users skipping? (Maybe it's too long/not valuable)
- **Completion rate**: Are users completing? (If low, simplify)
- **Time to value**: How long until users get first value?

Remember: You're a product educator with excellent teaching instincts. Get users to their "aha moment" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence.


must-d0d69e29-0

must-7cb7a4d7-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: the "aha moment" you want users to reach, and users' experience level.

must-7cb7a4d7-1

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

- Interactive when possible (do, don't just read)

must-7cb7a4d7-5

- Celebrate completion (but don't overdo it)

must-7cb7a4d7-6

- Dismissable (with "Don't show again" option)

must-7cb7a4d7-7

- Unlock complexity gradually (don't show all options immediately)

- **Error state**: Failed to load (explain what happened, retry option)

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

must-7cb7a4d7-9

- Forget about returning users (don't show initial onboarding again)


---
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-d0d69e29-0

must-7cb7a4d7-0

must-7cb7a4d7-1

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

must-7cb7a4d7-5

must-7cb7a4d7-6

must-7cb7a4d7-7

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

must-7cb7a4d7-9

NOTICE.md

NOTICE.md

must-dce96591-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-dce96591-1

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

must-dce96591-2

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

must-dce96591-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-dce96591-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-dce96591-5

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

must-dce96591-6

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

must-dce96591-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-dce96591-8

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

must-dce96591-9

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

must-dce96591-10

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

must-dce96591-11

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

must-dce96591-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-dce96591-13

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

must-dce96591-14

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

must-dce96591-15

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

must-dce96591-16

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

must-dce96591-17

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

must-dce96591-18

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

must-dce96591-19

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

must-dce96591-20

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

must-dce96591-21

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

must-dce96591-22

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

must-dce96591-23

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

reference/motion-design.md

reference/motion-design.md

must-dce96591-24

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

must-dce96591-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-dce96591-26

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

must-dce96591-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-dce96591-28

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

must-dce96591-29

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

reference/ux-writing.md

reference/ux-writing.md

must-dce96591-30

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

must-dce96591-31

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

must-dce96591-32

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

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


**Checking design instructions**

I see that the frontend-design skill needs to run the teach-impeccable directive if there's no design context provided in the current instructions or the .impeccable.md file. Since there's a .impeccable.md file located in the project root, I should go ahead and read it. This will help me ensure that I'm following the right design guidelines for this project. Let's get that clear!


ENOENT: no such file or directory, access '/home/alex/.pi/agent/skills/.impeccable.md'


must-d0d69e29-0

IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Inspect the skill folders if needed. User request: "Build a distinctive onboarding experience for first-time users. It should feel polished and not like generic AI UI." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

must-7cb7a4d7-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: the "aha moment" you want users to reach, and users' experience level.

must-7cb7a4d7-1

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

- Interactive when possible (do, don't just read)

must-7cb7a4d7-5

- Celebrate completion (but don't overdo it)

must-7cb7a4d7-6

- Dismissable (with "Don't show again" option)

must-7cb7a4d7-7

- Unlock complexity gradually (don't show all options immediately)

- **Error state**: Failed to load (explain what happened, retry option)

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

must-7cb7a4d7-9

- Forget about returning users (don't show initial onboarding again)

NOTICE.md

NOTICE.md

must-dce96591-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-dce96591-1

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

must-dce96591-2

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

must-dce96591-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-dce96591-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-dce96591-5

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

must-dce96591-6

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

must-dce96591-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-dce96591-8

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

must-dce96591-9

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

must-dce96591-10

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

must-dce96591-11

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

must-dce96591-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-dce96591-13

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

must-dce96591-14

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

must-dce96591-15

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

must-dce96591-16

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

must-dce96591-17

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

must-dce96591-18

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

must-dce96591-19

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

must-dce96591-20

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

must-dce96591-21

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

must-dce96591-22

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

must-dce96591-23

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

reference/motion-design.md

reference/motion-design.md

must-dce96591-24

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

must-dce96591-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-dce96591-26

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

must-dce96591-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-dce96591-28

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

must-dce96591-29

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

reference/ux-writing.md

reference/ux-writing.md

must-dce96591-30

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

must-dce96591-31

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

must-dce96591-32

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

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

ENOENT: no such file or directory, access '/home/alex/.pi/agent/skills/.impeccable.md'


No files found matching pattern


.git/
caveman/
find-docs/
frontend/
playwright-cli/
research/
superpowers/


.git/
.gitignore
.gitmodules
AGENTS.md
auth.json
bin/
extensions/
sessions/
settings.json
skills/
web-search.json


must-d0d69e29-0

IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Inspect the skill folders if needed. User request: "Build a distinctive onboarding experience for first-time users. It should feel polished and not like generic AI UI." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

must-7cb7a4d7-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: the "aha moment" you want users to reach, and users' experience level.

must-7cb7a4d7-1

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

- Interactive when possible (do, don't just read)

must-7cb7a4d7-5

- Celebrate completion (but don't overdo it)

must-7cb7a4d7-6

- Dismissable (with "Don't show again" option)

must-7cb7a4d7-7

- Unlock complexity gradually (don't show all options immediately)

- **Error state**: Failed to load (explain what happened, retry option)

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

must-7cb7a4d7-9

- Forget about returning users (don't show initial onboarding again)

NOTICE.md

NOTICE.md

must-dce96591-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-dce96591-1

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

must-dce96591-2

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

must-dce96591-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-dce96591-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-dce96591-5

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

must-dce96591-6

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

must-dce96591-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-dce96591-8

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

must-dce96591-9

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

must-dce96591-10

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

must-dce96591-11

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

must-dce96591-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-dce96591-13

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

must-dce96591-14

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

must-dce96591-15

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

must-dce96591-16

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

must-dce96591-17

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

must-dce96591-18

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

must-dce96591-19

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

must-dce96591-20

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

must-dce96591-21

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

must-dce96591-22

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

must-dce96591-23

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

reference/motion-design.md

reference/motion-design.md

must-dce96591-24

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

must-dce96591-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-dce96591-26

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

must-dce96591-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-dce96591-28

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

must-dce96591-29

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

reference/ux-writing.md

reference/ux-writing.md

must-dce96591-30

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

must-dce96591-31

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

must-dce96591-32

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

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

ENOENT: no such file or directory, access '/home/alex/.pi/agent/skills/.impeccable.md'

AGENTS.md

AGENTS.md

auth.js

auth.js

settings.js

settings.js

web-search.js

web-search.js


**Deciding on frontend skills**

I need to select which frontend skills to load from the directory because the user specifically asked for that. The main skill seems to be "onboard," and "frontend-design" is a requirement. I'm also considering whether to include "delight" or "polish." Let's take a closer look at the "delight" skill file to make a more informed decision. It's important to keep things minimal while ensuring we have what's necessary for a polished onboarding experience.


---
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-d0d69e29-0

IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Inspect the skill folders if needed. User request: "Build a distinctive onboarding experience for first-time users. It should feel polished and not like generic AI UI." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

must-7cb7a4d7-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: the "aha moment" you want users to reach, and users' experience level.

must-7cb7a4d7-1

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

- Interactive when possible (do, don't just read)

must-7cb7a4d7-5

- Celebrate completion (but don't overdo it)

must-7cb7a4d7-6

- Dismissable (with "Don't show again" option)

must-7cb7a4d7-7

- Unlock complexity gradually (don't show all options immediately)

- **Error state**: Failed to load (explain what happened, retry option)

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

must-7cb7a4d7-9

- Forget about returning users (don't show initial onboarding again)

NOTICE.md

NOTICE.md

must-dce96591-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-dce96591-1

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

must-dce96591-2

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

must-dce96591-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-dce96591-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-dce96591-5

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

must-dce96591-6

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

must-dce96591-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-dce96591-8

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

must-dce96591-9

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

must-dce96591-10

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

must-dce96591-11

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

must-dce96591-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-dce96591-13

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

must-dce96591-14

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

must-dce96591-15

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

must-dce96591-16

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

must-dce96591-17

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

must-dce96591-18

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

must-dce96591-19

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

must-dce96591-20

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

must-dce96591-21

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

must-dce96591-22

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

must-dce96591-23

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

reference/motion-design.md

reference/motion-design.md

must-dce96591-24

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

must-dce96591-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-dce96591-26

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

must-dce96591-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-dce96591-28

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

must-dce96591-29

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

reference/ux-writing.md

reference/ux-writing.md

must-dce96591-30

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

must-dce96591-31

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

must-dce96591-32

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

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

ENOENT: no such file or directory, access '/home/alex/.pi/agent/skills/.impeccable.md'

AGENTS.md

AGENTS.md

auth.js

auth.js

settings.js

settings.js

web-search.js

web-search.js

must-7ee1427d-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-7ee1427d-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-7ee1427d-2

- Delight moments should be quick (< 1 second)

must-7ee1427d-3

- Don't announce every delight moment

must-7ee1427d-4

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

must-7ee1427d-5

- Delight should remain fresh with repeated use

**Playful error messages**:

"Error 404"

"Connection failed"

- Error state illustrations (friendly monsters, quirky characters)

- Error sounds (empathetic, not harsh)

must-7ee1427d-6

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

must-7ee1427d-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-7ee1427d-8

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

must-7ee1427d-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-d0d69e29-0

IMPORTANT: This is a real scenario. Choose which existing frontend skill or skills to load from this directory. Inspect the skill folders if needed. User request: "Build a distinctive onboarding experience for first-time users. It should feel polished and not like generic AI UI." Return exactly three lines: Skills: ...\nOrder: ...\nWhy: ...

must-7cb7a4d7-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: the "aha moment" you want users to reach, and users' experience level.

must-7cb7a4d7-1

**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.

must-7cb7a4d7-2

- Don't block access to product

must-7cb7a4d7-3

- Don't patronize or over-explain

must-7cb7a4d7-4

- Interactive when possible (do, don't just read)

must-7cb7a4d7-5

- Celebrate completion (but don't overdo it)

must-7cb7a4d7-6

- Dismissable (with "Don't show again" option)

must-7cb7a4d7-7

- Unlock complexity gradually (don't show all options immediately)

- **Error state**: Failed to load (explain what happened, retry option)

Tippy.js

Tippy.js

Popper.js

Popper.js

Intro.js

Intro.js

Shepherd.js

Shepherd.js

must-7cb7a4d7-8

**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.

must-7cb7a4d7-9

- Forget about returning users (don't show initial onboarding again)

NOTICE.md

NOTICE.md

must-dce96591-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-dce96591-1

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

must-dce96591-2

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

must-dce96591-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-dce96591-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-dce96591-5

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

must-dce96591-6

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

must-dce96591-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-dce96591-8

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

must-dce96591-9

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

must-dce96591-10

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

must-dce96591-11

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

must-dce96591-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-dce96591-13

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

must-dce96591-14

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

must-dce96591-15

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

must-dce96591-16

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

must-dce96591-17

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

must-dce96591-18

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

must-dce96591-19

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

must-dce96591-20

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

must-dce96591-21

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

must-dce96591-22

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

must-dce96591-23

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

reference/motion-design.md

reference/motion-design.md

must-dce96591-24

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

must-dce96591-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-dce96591-26

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

must-dce96591-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-dce96591-28

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

must-dce96591-29

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

reference/ux-writing.md

reference/ux-writing.md

must-dce96591-30

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

must-dce96591-31

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

must-dce96591-32

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

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

ENOENT: no such file or directory, access '/home/alex/.pi/agent/skills/.impeccable.md'

AGENTS.md

AGENTS.md

auth.js

auth.js

settings.js

settings.js

web-search.js

web-search.js

must-7ee1427d-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-7ee1427d-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-7ee1427d-2

- Delight moments should be quick (< 1 second)

must-7ee1427d-3

- Don't announce every delight moment

must-7ee1427d-4

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

must-7ee1427d-5

- Delight should remain fresh with repeated use

**Playful error messages**:

"Error 404"

"Connection failed"

- Error state illustrations (friendly monsters, quirky characters)

- Error sounds (empathetic, not harsh)

must-7ee1427d-6

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

must-7ee1427d-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-7ee1427d-8

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

must-7ee1427d-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-a004b249-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-a004b249-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-a004b249-2

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

- **Error messages**: Helpful and consistent

must-a004b249-3

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

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

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

must-a004b249-4

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

- [ ] Error states are helpful

must-a004b249-5

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


**Considering onboarding skills**

Building a distinctive onboarding experience for first-time users calls for a polished touch, distinct from generic AI interfaces. The user explicitly asked for specific skills, including frontend design and delight elements, to enhance the overall experience. While polish skills are essential for later stages and to ensure quality, it might not be necessary to load them right at the start. Since polish is meant for the last step, it’s worth focusing on onboarding, frontend design, and delight first.

**Selecting skills for loading**

The instructions are clear: I must load the "caveman" skill, along with any other appropriate skills. However, the user specifically asked for a list of exactly three lines: Skills, Order, and Why. I could consider including 3-4 skills like frontend design, onboarding, and delight, but I need to select from the directory. Since "caveman" isn't in the directory, I need to focus on skills like frontend-design, onboard, delight, and possibly polish, while still ensuring caveman is always loaded.

**Choosing frontend skills**

The project instruction to "always load caveman skill" is global and needs to be followed. In this case, I should select skills from the directory, which includes "onboard," "frontend-design," and "delight." I know that the loading order matters, with "frontend-design" needing to come before "onboard" and "delight." To meet the user's formatting requirements, I can provide a compact list: Skills: caveman, frontend-design, onboard. Order: caveman, frontend-design, onboard. This keeps everything clear and concise!

**Understanding skill selection**

I need to ensure that I follow the frontend-design constraints focused on branding. The onboarding skill is essential for a polished experience, while the "caveman" skill should be included for brevity. The "delight" skill is necessary to avoid a generic AI interface and add that extra touch. The project instructions also emphasize always loading the "caveman" skill and being brief. Given that the user asked for a concise response in three lines, I’ll stick to the essentials while ensuring clarity.

**Determining skills and order**

I need to select skills from the directory: "frontend-design," "onboard," and "delight," while always including the "caveman" skill for brevity. The loading order should prioritize "frontend-design" first to establish context, followed by "onboard" for the onboarding flow, and finally "delight" for those polished touches. My rationale for each skill should be brief and clear: "frontend-design for context & aesthetics; onboard for flow; delight for tasteful polish; caveman for concise outputs." I'll present everything in the required three-line format.

**Clarifying skill selection**

The user has requested a straightforward response in three lines, focusing on skills from the frontend directory. I need to include "frontend-design," "onboard," and "delight," while also adhering to the instruction to always load the "caveman" skill for brevity. The order of loading should start with "frontend-design" to establish context first. For the reasoning line, I can succinctly explain that "frontend-design provides context; onboard builds flows; delight adds polish; caveman offers concise outputs." This keeps everything clear and meets the requirements!

**Determining the skills to load**

I’m considering how to respond about which skills to load for the user. I'll list "frontend-design," "onboard," and "delight," while including "caveman" because project instructions require its inclusion. While the user referred specifically to the directory for skills, "caveman" is required.

I should also clarify the loading sequence. I think the optimal order is "caveman," "frontend-design," "onboard," and then "delight." My reasoning will succinctly explain how each skill contributes to the overall experience. Let's finalize those lines clearly.

Skills: caveman, frontend-design, onboard, delight
Order: caveman -> frontend-design -> onboard -> delight
Why: frontend-design enforces the Context Gathering Protocol and prevents AI‑slop; onboard designs the first-run flow to reach the "aha" moment; delight adds tasteful micro‑interactions and polished moments that elevate without distracting.