diff --git a/.agents/skills/adapt/SKILL.md b/.agents/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.agents/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.agents/skills/animate/SKILL.md b/.agents/skills/animate/SKILL.md deleted file mode 100644 index 89933bfb5..000000000 --- a/.agents/skills/animate/SKILL.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.agents/skills/audit/SKILL.md b/.agents/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.agents/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.agents/skills/bolder/SKILL.md b/.agents/skills/bolder/SKILL.md deleted file mode 100644 index e80f55ed1..000000000 --- a/.agents/skills/bolder/SKILL.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too safe or boring: - -1. **Identify weakness sources**: - - **Generic choices**: System fonts, basic colors, standard layouts - - **Timid scale**: Everything is medium-sized with no drama - - **Low contrast**: Everything has similar visual weight - - **Static**: No motion, no energy, no life - - **Predictable**: Standard patterns with no surprises - - **Flat hierarchy**: Nothing stands out or commands attention - -2. **Understand the context**: - - What's the brand personality? (How far can we push?) - - What's the purpose? (Marketing can be bolder than financial dashboards) - - Who's the audience? (What will resonate?) - - What are the constraints? (Brand guidelines, accessibility, performance) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. - -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." - -## Plan Amplification - -Create a strategy to increase impact while maintaining coherence: - -- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) -- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. -- **Risk budget**: How experimental can we be? Push boundaries within constraints. -- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) - -**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. - -## Amplify the Design - -Systematically increase impact across these dimensions: - -### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) -- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) -- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 -- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) - -### Color Intensification -- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) -- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop -- **Dominant color strategy**: Let one bold color own 60% of the design -- **Sharp accents**: High-contrast accent colors that pop -- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette -- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) - -### Spatial Drama -- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings -- **Break the grid**: Let hero elements escape containers and cross boundaries -- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry -- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) -- **Overlap**: Layer elements intentionally for depth - -### Visual Effects -- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) -- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) -- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) -- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) -- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand - -### Motion & Animation -- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays -- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences -- **Micro-interactions**: Satisfying hover effects, click feedback, state changes -- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) - -### Composition Boldness -- **Hero moments**: Create clear focal points with dramatic treatment -- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements -- **Full-bleed elements**: Use full viewport width/height for impact -- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits - -**NEVER**: -- Add effects randomly without purpose (chaos ≠ bold) -- Sacrifice readability for aesthetics (body text must be readable) -- Make everything bold (then nothing is bold - need contrast) -- Ignore accessibility (bold design must still meet WCAG standards) -- Overwhelm with motion (animation fatigue is real) -- Copy trendy aesthetics blindly (bold means distinctive, not derivative) - -## Verify Quality - -Ensure amplification maintains usability and coherence: - -- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. -- **Still functional**: Can users accomplish tasks without distraction? -- **Coherent**: Does everything feel intentional and unified? -- **Memorable**: Will users remember this experience? -- **Performant**: Do all these effects run smoothly? -- **Accessible**: Does it still meet accessibility standards? - -**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." - -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/.agents/skills/clarify/SKILL.md b/.agents/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.agents/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.agents/skills/colorize/SKILL.md b/.agents/skills/colorize/SKILL.md deleted file mode 100644 index 76075804f..000000000 --- a/.agents/skills/colorize/SKILL.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. - ---- - -## Assess Color Opportunity - -Analyze the current state and identify opportunities: - -1. **Understand current state**: - - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? - - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? - - **Context**: What's appropriate for this domain and audience? - - **Brand**: Are there existing brand colors we should use? - -2. **Identify where color adds value**: - - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) - - **Hierarchy**: Drawing attention to important elements - - **Categorization**: Different sections, types, or states - - **Emotional tone**: Warmth, energy, trust, creativity - - **Wayfinding**: Helping users navigate and understand structure - - **Delight**: Moments of visual interest and personality - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. - -## Plan Color Strategy - -Create a purposeful color introduction plan: - -- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) -- **Dominant color**: Which color owns 60% of colored elements? -- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) -- **Application strategy**: Where does each color appear and why? - -**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. - -## Introduce Color Strategically - -Add color systematically across these dimensions: - -### Semantic Color -- **State indicators**: - - Success: Green tones (emerald, forest, mint) - - Error: Red/pink tones (rose, crimson, coral) - - Warning: Orange/amber tones - - Info: Blue tones (sky, ocean, indigo) - - Neutral: Gray/slate for inactive states - -- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) -- **Progress indicators**: Colored bars, rings, or charts showing completion or health - -### Accent Color Application -- **Primary actions**: Color the most important buttons/CTAs -- **Links**: Add color to clickable text (maintain accessibility) -- **Icons**: Colorize key icons for recognition and personality -- **Headers/titles**: Add color to section headers or key labels -- **Hover states**: Introduce color on interaction - -### Background & Surfaces -- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) -- **Colored sections**: Use subtle background colors to separate areas -- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) -- **Cards & surfaces**: Tint cards or surfaces slightly for warmth - -**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. - -### Data Visualization -- **Charts & graphs**: Use color to encode categories or values -- **Heatmaps**: Color intensity shows density or importance -- **Comparison**: Color coding for different datasets or timeframes - -### Borders & Accents -- **Accent borders**: Add colored left/top borders to cards or sections -- **Underlines**: Color underlines for emphasis or active states -- **Dividers**: Subtle colored dividers instead of gray lines -- **Focus rings**: Colored focus indicators matching brand - -### Typography Color -- **Colored headings**: Use brand colors for section headings (maintain contrast) -- **Highlight text**: Color for emphasis or categories -- **Labels & tags**: Small colored labels for metadata or categories - -### Decorative Elements -- **Illustrations**: Add colored illustrations or icons -- **Shapes**: Geometric shapes in brand colors as background elements -- **Gradients**: Colorful gradient overlays or mesh backgrounds -- **Blobs/organic shapes**: Soft colored shapes for visual interest - -## Balance & Refinement - -Ensure color addition improves rather than overwhelms: - -### Maintain Hierarchy -- **Dominant color** (60%): Primary brand color or most used accent -- **Secondary color** (30%): Supporting color for variety -- **Accent color** (10%): High contrast for key moments -- **Neutrals** (remaining): Gray/black/white for structure - -### Accessibility -- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) -- **Don't rely on color alone**: Use icons, labels, or patterns alongside color -- **Test for color blindness**: Verify red/green combinations work for all users - -### Cohesion -- **Consistent palette**: Use colors from defined palette, not arbitrary choices -- **Systematic application**: Same color meanings throughout (green always = success) -- **Temperature consistency**: Warm palette stays warm, cool stays cool - -**NEVER**: -- Use every color in the rainbow (choose 2-4 colors beyond neutrals) -- Apply color randomly without semantic meaning -- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead -- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication -- Use pure black (`#000`) or pure white (`#fff`) for large areas -- Violate WCAG contrast requirements -- Use color as the only indicator (accessibility issue) -- Make everything colorful (defeats the purpose) -- Default to purple-blue gradients (AI slop aesthetic) - -## Verify Color Addition - -Test that colorization improves the experience: - -- **Better hierarchy**: Does color guide attention appropriately? -- **Clearer meaning**: Does color help users understand states/categories? -- **More engaging**: Does the interface feel warmer and more inviting? -- **Still accessible**: Do all color combinations meet WCAG standards? -- **Not overwhelming**: Is color balanced and purposeful? - -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/.agents/skills/delight/SKILL.md b/.agents/skills/delight/SKILL.md deleted file mode 100644 index fedebff9c..000000000 --- a/.agents/skills/delight/SKILL.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.agents/skills/distill/SKILL.md b/.agents/skills/distill/SKILL.md deleted file mode 100644 index f3f721c99..000000000 --- a/.agents/skills/distill/SKILL.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel complex or cluttered: - -1. **Identify complexity sources**: - - **Too many elements**: Competing buttons, redundant information, visual clutter - - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - - **Information overload**: Everything visible at once, no progressive disclosure - - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - - **Confusing hierarchy**: Unclear what matters most - - **Feature creep**: Too many options, actions, or paths forward - -2. **Find the essence**: - - What's the primary user goal? (There should be ONE) - - What's actually necessary vs nice-to-have? - - What can be removed, hidden, or combined? - - What's the 20% that delivers 80% of value? - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. - -## Plan Simplification - -Create a ruthless editing strategy: - -- **Core purpose**: What's the ONE thing this should accomplish? -- **Essential elements**: What's truly necessary to achieve that purpose? -- **Progressive disclosure**: What can be hidden until needed? -- **Consolidation opportunities**: What can be combined or integrated? - -**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. - -## Simplify the Design - -Systematically remove complexity across these dimensions: - -### Information Architecture -- **Reduce scope**: Remove secondary actions, optional features, redundant information -- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) -- **Combine related actions**: Merge similar buttons, consolidate forms, group related content -- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden -- **Remove redundancy**: If it's said elsewhere, don't repeat it here - -### Visual Simplification -- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors -- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights -- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function -- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards -- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead -- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps - -### Layout Simplification -- **Linear flow**: Replace complex grids with simple vertical flow where possible -- **Remove sidebars**: Move secondary content inline or hide it -- **Full-width**: Use available space generously instead of complex multi-column layouts -- **Consistent alignment**: Pick left or center, stick with it -- **Generous white space**: Let content breathe, don't pack everything tight - -### Interaction Simplification -- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) -- **Smart defaults**: Make common choices automatic, only ask when necessary -- **Inline actions**: Replace modal flows with inline editing where possible -- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? -- **Clear CTAs**: ONE obvious next step, not five competing actions - -### Content Simplification -- **Shorter copy**: Cut every sentence in half, then do it again -- **Active voice**: "Save changes" not "Changes will be saved" -- **Remove jargon**: Plain language always wins -- **Scannable structure**: Short paragraphs, bullet points, clear headings -- **Essential information only**: Remove marketing fluff, legalese, hedging -- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once - -### Code Simplification -- **Remove unused code**: Dead CSS, unused components, orphaned files -- **Flatten component trees**: Reduce nesting depth -- **Consolidate styles**: Merge similar styles, use utilities consistently -- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? - -**NEVER**: -- Remove necessary functionality (simplicity ≠ feature-less) -- Sacrifice accessibility for simplicity (clear labels and ARIA still required) -- Make things so simple they're unclear (mystery ≠ minimalism) -- Remove information users need to make decisions -- Eliminate hierarchy completely (some things should stand out) -- Oversimplify complex domains (match complexity to actual task complexity) - -## Verify Simplification - -Ensure simplification improves usability: - -- **Faster task completion**: Can users accomplish goals more quickly? -- **Reduced cognitive load**: Is it easier to understand what to do? -- **Still complete**: Are all necessary features still accessible? -- **Clearer hierarchy**: Is it obvious what matters most? -- **Better performance**: Does simpler design load faster? - -## Document Removed Complexity - -If you removed features or options: -- Document why they were removed -- Consider if they need alternative access points -- Note any user feedback to monitor - -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/.agents/skills/harden/SKILL.md b/.agents/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.agents/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.agents/skills/impeccable/SKILL.md b/.agents/skills/impeccable/SKILL.md index bc4574d35..14acacac2 100644 --- a/.agents/skills/impeccable/SKILL.md +++ b/.agents/skills/impeccable/SKILL.md @@ -1,16 +1,18 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +25,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +34,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +270,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +284,96 @@ Remember: the model is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .agents/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github/copilot-instructions.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.gemini/skills/adapt/SKILL.md b/.agents/skills/impeccable/reference/adapt.md similarity index 90% rename from .gemini/skills/adapt/SKILL.md rename to .agents/skills/impeccable/reference/adapt.md index 35b00e3f9..249653d4c 100644 --- a/.gemini/skills/adapt/SKILL.md +++ b/.agents/skills/impeccable/reference/adapt.md @@ -1,14 +1,7 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 ---- +> **Additional context needed**: target platforms/devices and usage contexts. Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. --- @@ -194,4 +187,4 @@ Test thoroughly across contexts: - **Edge cases**: Very small screens (320px), very large screens (4K) - **Slow connections**: Test on throttled network -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.gemini/skills/animate/SKILL.md b/.agents/skills/impeccable/reference/animate.md similarity index 91% rename from .gemini/skills/animate/SKILL.md rename to .agents/skills/impeccable/reference/animate.md index 02294bc19..0186ce081 100644 --- a/.gemini/skills/animate/SKILL.md +++ b/.agents/skills/impeccable/reference/animate.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -170,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.kiro/skills/audit/SKILL.md b/.agents/skills/impeccable/reference/audit.md similarity index 80% rename from .kiro/skills/audit/SKILL.md rename to .agents/skills/impeccable/reference/audit.md index 7fddc7b21..206fafb5c 100644 --- a/.kiro/skills/audit/SKILL.md +++ b/.agents/skills/impeccable/reference/audit.md @@ -1,15 +1,3 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -64,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -107,7 +95,7 @@ For each issue, document: - **Impact**: How it affects users - **WCAG/Standard**: Which standard it violates (if applicable) - **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) ### Patterns & Systemic Issues @@ -126,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `/command-name`** — Brief description (specific context from audit findings) 2. **[P?] `/command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/audit` after fixes to see your score improve. +> Re-run `/impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. @@ -143,4 +131,4 @@ After presenting the summary, tell the user: - Forget to prioritize (everything can't be P0) - Report false positives without verification -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.pi/skills/bolder/SKILL.md b/.agents/skills/impeccable/reference/bolder.md similarity index 88% rename from .pi/skills/bolder/SKILL.md rename to .agents/skills/impeccable/reference/bolder.md index e276b4d0b..cb3481663 100644 --- a/.pi/skills/bolder/SKILL.md +++ b/.agents/skills/impeccable/reference/bolder.md @@ -1,14 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -34,7 +25,7 @@ If any of these are unclear from the codebase, ask the user directly to clarify **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -52,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -112,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.pi/skills/clarify/SKILL.md b/.agents/skills/impeccable/reference/clarify.md similarity index 89% rename from .pi/skills/clarify/SKILL.md rename to .agents/skills/impeccable/reference/clarify.md index 468541090..dc116e745 100644 --- a/.pi/skills/clarify/SKILL.md +++ b/.agents/skills/impeccable/reference/clarify.md @@ -1,14 +1,7 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 ---- +> **Additional context needed**: audience technical level and users' mental state in context. Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. --- @@ -178,4 +171,4 @@ Test that copy improvements work: - **Consistency**: Does it match terminology elsewhere? - **Tone**: Is it appropriate for the situation? -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.agents/skills/critique/reference/cognitive-load.md b/.agents/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .agents/skills/critique/reference/cognitive-load.md rename to .agents/skills/impeccable/reference/cognitive-load.md diff --git a/.kiro/skills/colorize/SKILL.md b/.agents/skills/impeccable/reference/colorize.md similarity index 90% rename from .kiro/skills/colorize/SKILL.md rename to .agents/skills/impeccable/reference/colorize.md index 509a71c06..a4ce5072e 100644 --- a/.kiro/skills/colorize/SKILL.md +++ b/.agents/skills/impeccable/reference/colorize.md @@ -1,14 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -138,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.agents/skills/impeccable/reference/craft.md b/.agents/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.agents/skills/impeccable/reference/craft.md +++ b/.agents/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.agents/skills/critique/SKILL.md b/.agents/skills/impeccable/reference/critique.md similarity index 84% rename from .agents/skills/critique/SKILL.md rename to .agents/skills/impeccable/reference/critique.md index a827f2241..c6a867d50 100644 --- a/.agents/skills/critique/SKILL.md +++ b/.agents/skills/impeccable/reference/critique.md @@ -1,18 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -30,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -44,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -94,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -140,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `.github/copilot-instructions.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -176,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -196,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -209,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.kiro/skills/delight/SKILL.md b/.agents/skills/impeccable/reference/delight.md similarity index 92% rename from .kiro/skills/delight/SKILL.md rename to .agents/skills/impeccable/reference/delight.md index f323738dd..8a781e70e 100644 --- a/.kiro/skills/delight/SKILL.md +++ b/.agents/skills/impeccable/reference/delight.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -299,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.gemini/skills/distill/SKILL.md b/.agents/skills/impeccable/reference/distill.md similarity index 91% rename from .gemini/skills/distill/SKILL.md rename to .agents/skills/impeccable/reference/distill.md index e462d1c27..4f47dc0b4 100644 --- a/.gemini/skills/distill/SKILL.md +++ b/.agents/skills/impeccable/reference/distill.md @@ -1,14 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -117,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.pi/skills/harden/SKILL.md b/.agents/skills/impeccable/reference/harden.md similarity index 96% rename from .pi/skills/harden/SKILL.md rename to .agents/skills/impeccable/reference/harden.md index 78eaa9881..af8b8a703 100644 --- a/.pi/skills/harden/SKILL.md +++ b/.agents/skills/impeccable/reference/harden.md @@ -1,9 +1,3 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 ---- - Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. ## Assess Hardening Needs @@ -384,4 +378,4 @@ Test thoroughly with edge cases: - **Errors**: Force API errors, test all error states - **Empty**: Remove all data, test empty states -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.agents/skills/critique/reference/heuristics-scoring.md b/.agents/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .agents/skills/critique/reference/heuristics-scoring.md rename to .agents/skills/impeccable/reference/heuristics-scoring.md diff --git a/.gemini/skills/layout/SKILL.md b/.agents/skills/impeccable/reference/layout.md similarity index 89% rename from .gemini/skills/layout/SKILL.md rename to .agents/skills/impeccable/reference/layout.md index e3355c314..cd6b778e7 100644 --- a/.gemini/skills/layout/SKILL.md +++ b/.agents/skills/impeccable/reference/layout.md @@ -1,14 +1,5 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 ---- - Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak about the current spatial design: ## Plan Layout Improvements -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. Create a systematic plan: @@ -120,4 +111,4 @@ Create a systematic plan: - **Consistency**: Is the spacing system applied uniformly? - **Responsiveness**: Does the layout adapt gracefully across screen sizes? -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.cursor/skills/optimize/SKILL.md b/.agents/skills/impeccable/reference/optimize.md similarity index 96% rename from .cursor/skills/optimize/SKILL.md rename to .agents/skills/impeccable/reference/optimize.md index 6d82e1265..4abf575ec 100644 --- a/.cursor/skills/optimize/SKILL.md +++ b/.agents/skills/impeccable/reference/optimize.md @@ -1,9 +1,3 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 ---- - Identify and fix performance issues to create faster, smoother user experiences. ## Assess Performance Issues @@ -261,4 +255,4 @@ Test that optimizations worked: - **No regressions**: Ensure functionality still works - **User perception**: Does it *feel* faster? -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.pi/skills/overdrive/SKILL.md b/.agents/skills/impeccable/reference/overdrive.md similarity index 78% rename from .pi/skills/overdrive/SKILL.md rename to .agents/skills/impeccable/reference/overdrive.md index 11bd0f4a8..d84a147dc 100644 --- a/.pi/skills/overdrive/SKILL.md +++ b/.agents/skills/impeccable/reference/overdrive.md @@ -1,9 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 ---- - Start your response with: ``` @@ -11,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -31,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -89,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -126,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -137,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.agents/skills/critique/reference/personas.md b/.agents/skills/impeccable/reference/personas.md similarity index 100% rename from .agents/skills/critique/reference/personas.md rename to .agents/skills/impeccable/reference/personas.md diff --git a/.pi/skills/polish/SKILL.md b/.agents/skills/impeccable/reference/polish.md similarity index 93% rename from .pi/skills/polish/SKILL.md rename to .agents/skills/impeccable/reference/polish.md index 4c84dc128..597c68847 100644 --- a/.pi/skills/polish/SKILL.md +++ b/.agents/skills/impeccable/reference/polish.md @@ -1,14 +1,4 @@ ---- -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. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: quality bar (MVP vs flagship). - ---- +> **Additional context needed**: 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. @@ -219,4 +209,4 @@ After polishing, ensure code quality: - **Consolidate tokens**: If you introduced new values, check whether they should be tokens. - **Verify DRYness**: Look for duplication introduced during polishing and consolidate. -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. \ No newline at end of file +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. diff --git a/.kiro/skills/quieter/SKILL.md b/.agents/skills/impeccable/reference/quieter.md similarity index 89% rename from .kiro/skills/quieter/SKILL.md rename to .agents/skills/impeccable/reference/quieter.md index ca17da694..a8ad41809 100644 --- a/.kiro/skills/quieter/SKILL.md +++ b/.agents/skills/impeccable/reference/quieter.md @@ -1,14 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -98,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.kiro/skills/shape/SKILL.md b/.agents/skills/impeccable/reference/shape.md similarity index 80% rename from .kiro/skills/shape/SKILL.md rename to .agents/skills/impeccable/reference/shape.md index 6a94ee74c..0ae281943 100644 --- a/.kiro/skills/shape/SKILL.md +++ b/.agents/skills/impeccable/reference/shape.md @@ -1,24 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -56,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -91,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.agents/skills/impeccable/reference/teach.md b/.agents/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..5ebd3ed67 --- /dev/null +++ b/.agents/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github/copilot-instructions.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.cursor/skills/typeset/SKILL.md b/.agents/skills/impeccable/reference/typeset.md similarity index 87% rename from .cursor/skills/typeset/SKILL.md rename to .agents/skills/impeccable/reference/typeset.md index a5fff11a8..2e49ab6c0 100644 --- a/.cursor/skills/typeset/SKILL.md +++ b/.agents/skills/impeccable/reference/typeset.md @@ -1,14 +1,5 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 ---- - Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak or generic about the current type: ## Plan Typography Improvements -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. Create a systematic plan: @@ -111,4 +102,4 @@ Build a clear type scale: - **Performance**: Are web fonts loading efficiently without layout shift? - **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.agents/skills/impeccable/scripts/cleanup-deprecated.mjs b/.agents/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.agents/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.agents/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.agents/skills/impeccable/scripts/command-metadata.json b/.agents/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.agents/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.agents/skills/impeccable/scripts/pin.mjs b/.agents/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.agents/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.agents/skills/layout/SKILL.md b/.agents/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.agents/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.agents/skills/optimize/SKILL.md b/.agents/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.agents/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.agents/skills/overdrive/SKILL.md b/.agents/skills/overdrive/SKILL.md deleted file mode 100644 index 862a4c9c4..000000000 --- a/.agents/skills/overdrive/SKILL.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Start your response with: - -``` -──────────── ⚡ OVERDRIVE ───────────── -》》》 Entering overdrive mode... -``` - -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. - -### Propose Before Building - -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: - -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. -2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). -3. Only proceed with the direction the user confirms. - -Skipping this step risks building something embarrassing that needs to be thrown away. - -### Iterate with Browser Automation - -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. - ---- - -## Assess What "Extraordinary" Means Here - -The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** - -### For visual/marketing surfaces -Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. - -### For functional UI -Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. - -### For performance-critical UI -The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. - -### For data-heavy interfaces -Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. - -**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. - -## The Toolkit - -Organized by what you're trying to achieve, not by technology name. - -### Make transitions feel cinematic -- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. -- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes -- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. - -### Tie animation to scroll position -- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) - -### Render beyond CSS -- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. -- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. -- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. -- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. - -### Make data feel alive -- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. -- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. -- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. - -### Animate complex properties -- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. -- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. - -### Push performance boundaries -- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. -- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. -- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. - -### Interact with the device -- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. -- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. - -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. - -## Implement with Discipline - -### Progressive enhancement is non-negotiable - -Every technique must degrade gracefully. The experience without the enhancement must still be good. - -```css -@supports (animation-timeline: scroll()) { - .hero { animation-timeline: scroll(); } -} -``` - -```javascript -if ('gpu' in navigator) { /* WebGPU */ } -else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } -/* CSS-only fallback must still look good */ -``` - -### Performance rules - -- Target 60fps. If dropping below 50, simplify. -- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. -- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. -- Pause off-screen rendering. Kill what you can't see. -- Test on real mid-range devices, not just your development machine. - -### Polish is the difference - -The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. - -**NEVER**: -- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion -- Ship effects that cause jank on mid-range devices -- Use bleeding-edge APIs without a functional fallback -- Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills -- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise - -## Verify the Result - -- **The wow test**: Show it to someone who hasn't seen it. Do they react? -- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? -- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? -- **The accessibility test**: Enable reduced motion. Still beautiful? -- **The context test**: Does this make sense for THIS brand and audience? - -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file diff --git a/.agents/skills/polish/SKILL.md b/.agents/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.agents/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.agents/skills/quieter/SKILL.md b/.agents/skills/quieter/SKILL.md deleted file mode 100644 index 373ae6869..000000000 --- a/.agents/skills/quieter/SKILL.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too intense: - -1. **Identify intensity sources**: - - **Color saturation**: Overly bright or saturated colors - - **Contrast extremes**: Too much high-contrast juxtaposition - - **Visual weight**: Too many bold, heavy elements competing - - **Animation excess**: Too much motion or overly dramatic effects - - **Complexity**: Too many visual elements, patterns, or decorations - - **Scale**: Everything is large and loud with no hierarchy - -2. **Understand the context**: - - What's the purpose? (Marketing vs tool vs reading experience) - - Who's the audience? (Some contexts need energy) - - What's working? (Don't throw away good ideas) - - What's the core message? (Preserve what matters) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. - -## Plan Refinement - -Create a strategy to reduce intensity while maintaining impact: - -- **Color approach**: Desaturate or shift to more sophisticated tones? -- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? -- **Simplification approach**: What can be removed entirely? -- **Sophistication approach**: How can we signal quality through restraint? - -**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. - -## Refine the Design - -Systematically reduce intensity across these dimensions: - -### Color Refinement -- **Reduce saturation**: Shift from fully saturated to 70-85% saturation -- **Soften palette**: Replace bright colors with muted, sophisticated tones -- **Reduce color variety**: Use fewer colors more thoughtfully -- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) -- **Gentler contrasts**: High contrast only where it matters most -- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness -- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead - -### Visual Weight Reduction -- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate -- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness -- **White space**: Increase breathing room, reduce density -- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely - -### Simplification -- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose -- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes -- **Reduce layering**: Flatten visual hierarchy where possible -- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows - -### Motion Reduction -- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing -- **Remove decorative animations**: Keep functional motion, remove flourishes -- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback -- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic -- **Remove animations entirely** if they're not serving a clear purpose - -### Composition Refinement -- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling -- **Align to grid**: Bring rogue elements back into systematic alignment -- **Even out spacing**: Replace extreme spacing variations with consistent rhythm - -**NEVER**: -- Make everything the same size/weight (hierarchy still matters) -- Remove all color (quiet ≠ grayscale) -- Eliminate all personality (maintain character through refinement) -- Sacrifice usability for aesthetics (functional elements still need clear affordances) -- Make everything small and light (some anchors needed) - -## Verify Quality - -Ensure refinement maintains quality: - -- **Still functional**: Can users still accomplish tasks easily? -- **Still distinctive**: Does it have character, or is it generic now? -- **Better reading**: Is text easier to read for extended periods? -- **Sophistication**: Does it feel more refined and premium? - -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/.agents/skills/shape/SKILL.md b/.agents/skills/shape/SKILL.md deleted file mode 100644 index 7e83008b5..000000000 --- a/.agents/skills/shape/SKILL.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. - -## Philosophy - -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. - -## Phase 1: Discovery Interview - -**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. - -Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. - -### Purpose & Context -- What is this feature for? What problem does it solve? -- Who specifically will use it? (Not "users"; be specific: role, context, frequency) -- What does success look like? How will you know this feature is working? -- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) - -### Content & Data -- What content or data does this feature display or collect? -- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) -- What are the edge cases? (Empty state, error state, first-time use, power user) -- Is any content dynamic? What changes and how often? - -### Design Goals -- What's the single most important thing a user should do or understand here? -- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) -- Are there existing patterns in the product this should be consistent with? -- Are there specific examples (inside or outside the product) that capture what you're going for? - -### Constraints -- Are there technical constraints? (Framework, performance budget, browser support) -- Are there content constraints? (Localization, dynamic text length, user-generated content) -- Mobile/responsive requirements? -- Accessibility requirements beyond WCAG AA? - -### Anti-Goals -- What should this NOT be? What would be a wrong direction? -- What's the biggest risk of getting this wrong? - -## Phase 2: Design Brief - -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. - -### Brief Structure - -**1. Feature Summary** (2-3 sentences) -What this is, who it's for, what it needs to accomplish. - -**2. Primary User Action** -The single most important thing a user should do or understand here. - -**3. Design Direction** -How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. - -**4. Layout Strategy** -High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. - -**5. Key States** -List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. - -**6. Interaction Model** -How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? - -**7. Content Requirements** -What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. - -**8. Recommended References** -Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). - -**9. Open Questions** -Anything unresolved that the implementer should resolve during build. - ---- - -ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. - -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file diff --git a/.agents/skills/typeset/SKILL.md b/.agents/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.agents/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 404f96f73..7fcd222d2 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -2,7 +2,7 @@ "$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "impeccable", "metadata": { - "description": "Design fluency for AI harnesses. 1 skill, 18 commands, and curated anti-patterns for impeccable frontend design." + "description": "Design fluency for AI harnesses. 1 skill, 20 commands, and curated anti-patterns for impeccable frontend design." }, "owner": { "name": "Paul Bakaus", @@ -11,7 +11,7 @@ "plugins": [ { "name": "impeccable", - "description": "Design vocabulary and skills for frontend development. Includes 18 commands (/polish, /distill, /audit, /typeset, /overdrive, etc.) and an enhanced impeccable skill with curated anti-patterns.", + "description": "Design fluency for frontend development. 1 skill with 20 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.", "version": "2.1.1", "author": { "name": "Paul Bakaus", diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 32f8179c7..25dce892c 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "impeccable", - "description": "Design vocabulary and skills for frontend development. Includes 18 commands (/polish, /distill, /audit, /typeset, /overdrive, etc.) and an enhanced impeccable skill with curated anti-patterns.", + "description": "Design fluency for frontend development. 1 skill with 20 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.", "version": "2.1.1", "author": { "name": "Paul Bakaus", diff --git a/.claude/skills/adapt/SKILL.md b/.claude/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.claude/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.claude/skills/audit/SKILL.md b/.claude/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.claude/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.claude/skills/clarify/SKILL.md b/.claude/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.claude/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.claude/skills/harden/SKILL.md b/.claude/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.claude/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.claude/skills/impeccable/SKILL.md b/.claude/skills/impeccable/SKILL.md index 18ecca274..5c0676008 100644 --- a/.claude/skills/impeccable/SKILL.md +++ b/.claude/skills/impeccable/SKILL.md @@ -1,16 +1,20 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. +allowed-tools: + - Bash(npx impeccable *) --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +27,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +36,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +272,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +286,96 @@ Remember: Claude is capable of extraordinary creative work. Don't hold back. Sho --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -STOP and call the AskUserQuestion tool to clarify. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .claude/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then STOP and call the AskUserQuestion tool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.pi/skills/adapt/SKILL.md b/.claude/skills/impeccable/reference/adapt.md similarity index 90% rename from .pi/skills/adapt/SKILL.md rename to .claude/skills/impeccable/reference/adapt.md index 35b00e3f9..249653d4c 100644 --- a/.pi/skills/adapt/SKILL.md +++ b/.claude/skills/impeccable/reference/adapt.md @@ -1,14 +1,7 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 ---- +> **Additional context needed**: target platforms/devices and usage contexts. Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. --- @@ -194,4 +187,4 @@ Test thoroughly across contexts: - **Edge cases**: Very small screens (320px), very large screens (4K) - **Slow connections**: Test on throttled network -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.claude/skills/animate/SKILL.md b/.claude/skills/impeccable/reference/animate.md similarity index 90% rename from .claude/skills/animate/SKILL.md rename to .claude/skills/impeccable/reference/animate.md index a3b21a220..fdb5b579a 100644 --- a/.claude/skills/animate/SKILL.md +++ b/.claude/skills/impeccable/reference/animate.md @@ -1,16 +1,7 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -172,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.cursor/skills/audit/SKILL.md b/.claude/skills/impeccable/reference/audit.md similarity index 80% rename from .cursor/skills/audit/SKILL.md rename to .claude/skills/impeccable/reference/audit.md index 7fddc7b21..206fafb5c 100644 --- a/.cursor/skills/audit/SKILL.md +++ b/.claude/skills/impeccable/reference/audit.md @@ -1,15 +1,3 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -64,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -107,7 +95,7 @@ For each issue, document: - **Impact**: How it affects users - **WCAG/Standard**: Which standard it violates (if applicable) - **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) ### Patterns & Systemic Issues @@ -126,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `/command-name`** — Brief description (specific context from audit findings) 2. **[P?] `/command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/audit` after fixes to see your score improve. +> Re-run `/impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. @@ -143,4 +131,4 @@ After presenting the summary, tell the user: - Forget to prioritize (everything can't be P0) - Report false positives without verification -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.claude/skills/bolder/SKILL.md b/.claude/skills/impeccable/reference/bolder.md similarity index 87% rename from .claude/skills/bolder/SKILL.md rename to .claude/skills/impeccable/reference/bolder.md index 2e15db324..32c12a6bf 100644 --- a/.claude/skills/bolder/SKILL.md +++ b/.claude/skills/impeccable/reference/bolder.md @@ -1,16 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -36,7 +25,7 @@ If any of these are unclear from the codebase, STOP and call the AskUserQuestion **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -54,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -114,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.gemini/skills/clarify/SKILL.md b/.claude/skills/impeccable/reference/clarify.md similarity index 89% rename from .gemini/skills/clarify/SKILL.md rename to .claude/skills/impeccable/reference/clarify.md index 468541090..dc116e745 100644 --- a/.gemini/skills/clarify/SKILL.md +++ b/.claude/skills/impeccable/reference/clarify.md @@ -1,14 +1,7 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 ---- +> **Additional context needed**: audience technical level and users' mental state in context. Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. --- @@ -178,4 +171,4 @@ Test that copy improvements work: - **Consistency**: Does it match terminology elsewhere? - **Tone**: Is it appropriate for the situation? -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.claude/skills/critique/reference/cognitive-load.md b/.claude/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .claude/skills/critique/reference/cognitive-load.md rename to .claude/skills/impeccable/reference/cognitive-load.md diff --git a/.claude/skills/colorize/SKILL.md b/.claude/skills/impeccable/reference/colorize.md similarity index 89% rename from .claude/skills/colorize/SKILL.md rename to .claude/skills/impeccable/reference/colorize.md index 5b4e961de..5cd4db209 100644 --- a/.claude/skills/colorize/SKILL.md +++ b/.claude/skills/impeccable/reference/colorize.md @@ -1,16 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -140,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.claude/skills/impeccable/reference/craft.md b/.claude/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.claude/skills/impeccable/reference/craft.md +++ b/.claude/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.claude/skills/critique/SKILL.md b/.claude/skills/impeccable/reference/critique.md similarity index 84% rename from .claude/skills/critique/SKILL.md rename to .claude/skills/impeccable/reference/critique.md index f0c2d92d0..e0d63443f 100644 --- a/.claude/skills/critique/SKILL.md +++ b/.claude/skills/impeccable/reference/critique.md @@ -1,20 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" -allowed-tools: - - Bash(npx impeccable *) ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -32,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -46,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -96,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -142,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `CLAUDE.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -178,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. STOP and call the AskUserQuestion tool to clarify. These answers will shape the action plan. @@ -198,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -211,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.claude/skills/delight/SKILL.md b/.claude/skills/impeccable/reference/delight.md similarity index 92% rename from .claude/skills/delight/SKILL.md rename to .claude/skills/impeccable/reference/delight.md index 441102c72..c3a24aeb6 100644 --- a/.claude/skills/delight/SKILL.md +++ b/.claude/skills/impeccable/reference/delight.md @@ -1,16 +1,7 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -301,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.claude/skills/distill/SKILL.md b/.claude/skills/impeccable/reference/distill.md similarity index 90% rename from .claude/skills/distill/SKILL.md rename to .claude/skills/impeccable/reference/distill.md index 765d01437..441b9fd93 100644 --- a/.claude/skills/distill/SKILL.md +++ b/.claude/skills/impeccable/reference/distill.md @@ -1,16 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -119,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.cursor/skills/harden/SKILL.md b/.claude/skills/impeccable/reference/harden.md similarity index 96% rename from .cursor/skills/harden/SKILL.md rename to .claude/skills/impeccable/reference/harden.md index 78eaa9881..af8b8a703 100644 --- a/.cursor/skills/harden/SKILL.md +++ b/.claude/skills/impeccable/reference/harden.md @@ -1,9 +1,3 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 ---- - Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. ## Assess Hardening Needs @@ -384,4 +378,4 @@ Test thoroughly with edge cases: - **Errors**: Force API errors, test all error states - **Empty**: Remove all data, test empty states -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.claude/skills/critique/reference/heuristics-scoring.md b/.claude/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .claude/skills/critique/reference/heuristics-scoring.md rename to .claude/skills/impeccable/reference/heuristics-scoring.md diff --git a/.pi/skills/layout/SKILL.md b/.claude/skills/impeccable/reference/layout.md similarity index 89% rename from .pi/skills/layout/SKILL.md rename to .claude/skills/impeccable/reference/layout.md index e3355c314..cd6b778e7 100644 --- a/.pi/skills/layout/SKILL.md +++ b/.claude/skills/impeccable/reference/layout.md @@ -1,14 +1,5 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 ---- - Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak about the current spatial design: ## Plan Layout Improvements -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. Create a systematic plan: @@ -120,4 +111,4 @@ Create a systematic plan: - **Consistency**: Is the spacing system applied uniformly? - **Responsiveness**: Does the layout adapt gracefully across screen sizes? -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.gemini/skills/optimize/SKILL.md b/.claude/skills/impeccable/reference/optimize.md similarity index 96% rename from .gemini/skills/optimize/SKILL.md rename to .claude/skills/impeccable/reference/optimize.md index 6d82e1265..4abf575ec 100644 --- a/.gemini/skills/optimize/SKILL.md +++ b/.claude/skills/impeccable/reference/optimize.md @@ -1,9 +1,3 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 ---- - Identify and fix performance issues to create faster, smoother user experiences. ## Assess Performance Issues @@ -261,4 +255,4 @@ Test that optimizations worked: - **No regressions**: Ensure functionality still works - **User perception**: Does it *feel* faster? -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.claude/skills/overdrive/SKILL.md b/.claude/skills/impeccable/reference/overdrive.md similarity index 77% rename from .claude/skills/overdrive/SKILL.md rename to .claude/skills/impeccable/reference/overdrive.md index a2cfe05a5..e91734d77 100644 --- a/.claude/skills/overdrive/SKILL.md +++ b/.claude/skills/impeccable/reference/overdrive.md @@ -1,11 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Start your response with: ``` @@ -13,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **STOP and call the AskUserQuestion tool to clarify.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -33,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -91,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -128,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -139,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.claude/skills/critique/reference/personas.md b/.claude/skills/impeccable/reference/personas.md similarity index 100% rename from .claude/skills/critique/reference/personas.md rename to .claude/skills/impeccable/reference/personas.md diff --git a/.cursor/skills/polish/SKILL.md b/.claude/skills/impeccable/reference/polish.md similarity index 93% rename from .cursor/skills/polish/SKILL.md rename to .claude/skills/impeccable/reference/polish.md index 4c84dc128..597c68847 100644 --- a/.cursor/skills/polish/SKILL.md +++ b/.claude/skills/impeccable/reference/polish.md @@ -1,14 +1,4 @@ ---- -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. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: quality bar (MVP vs flagship). - ---- +> **Additional context needed**: 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. @@ -219,4 +209,4 @@ After polishing, ensure code quality: - **Consolidate tokens**: If you introduced new values, check whether they should be tokens. - **Verify DRYness**: Look for duplication introduced during polishing and consolidate. -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. \ No newline at end of file +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. diff --git a/.claude/skills/quieter/SKILL.md b/.claude/skills/impeccable/reference/quieter.md similarity index 88% rename from .claude/skills/quieter/SKILL.md rename to .claude/skills/impeccable/reference/quieter.md index a2457d65a..1b9de9450 100644 --- a/.claude/skills/quieter/SKILL.md +++ b/.claude/skills/impeccable/reference/quieter.md @@ -1,16 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -100,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.claude/skills/shape/SKILL.md b/.claude/skills/impeccable/reference/shape.md similarity index 79% rename from .claude/skills/shape/SKILL.md rename to .claude/skills/impeccable/reference/shape.md index 4bcfbc3b6..7e933b923 100644 --- a/.claude/skills/shape/SKILL.md +++ b/.claude/skills/impeccable/reference/shape.md @@ -1,26 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -58,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -93,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. STOP and call the AskUserQuestion tool to clarify. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.claude/skills/impeccable/reference/teach.md b/.claude/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..6fa81b276 --- /dev/null +++ b/.claude/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +STOP and call the AskUserQuestion tool to clarify. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then STOP and call the AskUserQuestion tool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.gemini/skills/typeset/SKILL.md b/.claude/skills/impeccable/reference/typeset.md similarity index 87% rename from .gemini/skills/typeset/SKILL.md rename to .claude/skills/impeccable/reference/typeset.md index a5fff11a8..2e49ab6c0 100644 --- a/.gemini/skills/typeset/SKILL.md +++ b/.claude/skills/impeccable/reference/typeset.md @@ -1,14 +1,5 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 ---- - Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak or generic about the current type: ## Plan Typography Improvements -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. Create a systematic plan: @@ -111,4 +102,4 @@ Build a clear type scale: - **Performance**: Are web fonts loading efficiently without layout shift? - **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.claude/skills/impeccable/scripts/cleanup-deprecated.mjs b/.claude/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.claude/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.claude/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.claude/skills/impeccable/scripts/command-metadata.json b/.claude/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.claude/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.claude/skills/impeccable/scripts/pin.mjs b/.claude/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.claude/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.claude/skills/layout/SKILL.md b/.claude/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.claude/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.claude/skills/optimize/SKILL.md b/.claude/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.claude/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.claude/skills/polish/SKILL.md b/.claude/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.claude/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.claude/skills/typeset/SKILL.md b/.claude/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.claude/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.codex/skills/adapt/SKILL.md b/.codex/skills/adapt/SKILL.md deleted file mode 100644 index 152d607b5..000000000 --- a/.codex/skills/adapt/SKILL.md +++ /dev/null @@ -1,198 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.codex/skills/animate/SKILL.md b/.codex/skills/animate/SKILL.md deleted file mode 100644 index d2888c25a..000000000 --- a/.codex/skills/animate/SKILL.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -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. -version: 2.1.1 -argument-hint: "[target]" ---- - -Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach 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. \ No newline at end of file diff --git a/.codex/skills/bolder/SKILL.md b/.codex/skills/bolder/SKILL.md deleted file mode 100644 index e77f88117..000000000 --- a/.codex/skills/bolder/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -argument-hint: "[target]" ---- - -Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too safe or boring: - -1. **Identify weakness sources**: - - **Generic choices**: System fonts, basic colors, standard layouts - - **Timid scale**: Everything is medium-sized with no drama - - **Low contrast**: Everything has similar visual weight - - **Static**: No motion, no energy, no life - - **Predictable**: Standard patterns with no surprises - - **Flat hierarchy**: Nothing stands out or commands attention - -2. **Understand the context**: - - What's the brand personality? (How far can we push?) - - What's the purpose? (Marketing can be bolder than financial dashboards) - - Who's the audience? (What will resonate?) - - What are the constraints? (Brand guidelines, accessibility, performance) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. - -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." - -## Plan Amplification - -Create a strategy to increase impact while maintaining coherence: - -- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) -- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. -- **Risk budget**: How experimental can we be? Push boundaries within constraints. -- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) - -**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. - -## Amplify the Design - -Systematically increase impact across these dimensions: - -### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) -- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) -- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 -- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) - -### Color Intensification -- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) -- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop -- **Dominant color strategy**: Let one bold color own 60% of the design -- **Sharp accents**: High-contrast accent colors that pop -- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette -- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) - -### Spatial Drama -- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings -- **Break the grid**: Let hero elements escape containers and cross boundaries -- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry -- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) -- **Overlap**: Layer elements intentionally for depth - -### Visual Effects -- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) -- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) -- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) -- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) -- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand - -### Motion & Animation -- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays -- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences -- **Micro-interactions**: Satisfying hover effects, click feedback, state changes -- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) - -### Composition Boldness -- **Hero moments**: Create clear focal points with dramatic treatment -- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements -- **Full-bleed elements**: Use full viewport width/height for impact -- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits - -**NEVER**: -- Add effects randomly without purpose (chaos ≠ bold) -- Sacrifice readability for aesthetics (body text must be readable) -- Make everything bold (then nothing is bold - need contrast) -- Ignore accessibility (bold design must still meet WCAG standards) -- Overwhelm with motion (animation fatigue is real) -- Copy trendy aesthetics blindly (bold means distinctive, not derivative) - -## Verify Quality - -Ensure amplification maintains usability and coherence: - -- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. -- **Still functional**: Can users accomplish tasks without distraction? -- **Coherent**: Does everything feel intentional and unified? -- **Memorable**: Will users remember this experience? -- **Performant**: Do all these effects run smoothly? -- **Accessible**: Does it still meet accessibility standards? - -**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." - -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/.codex/skills/clarify/SKILL.md b/.codex/skills/clarify/SKILL.md deleted file mode 100644 index 57d0aa6b0..000000000 --- a/.codex/skills/clarify/SKILL.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.codex/skills/colorize/SKILL.md b/.codex/skills/colorize/SKILL.md deleted file mode 100644 index c9f743ced..000000000 --- a/.codex/skills/colorize/SKILL.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -argument-hint: "[target]" ---- - -Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. Additionally gather: existing brand colors. - ---- - -## Assess Color Opportunity - -Analyze the current state and identify opportunities: - -1. **Understand current state**: - - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? - - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? - - **Context**: What's appropriate for this domain and audience? - - **Brand**: Are there existing brand colors we should use? - -2. **Identify where color adds value**: - - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) - - **Hierarchy**: Drawing attention to important elements - - **Categorization**: Different sections, types, or states - - **Emotional tone**: Warmth, energy, trust, creativity - - **Wayfinding**: Helping users navigate and understand structure - - **Delight**: Moments of visual interest and personality - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. - -## Plan Color Strategy - -Create a purposeful color introduction plan: - -- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) -- **Dominant color**: Which color owns 60% of colored elements? -- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) -- **Application strategy**: Where does each color appear and why? - -**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. - -## Introduce Color Strategically - -Add color systematically across these dimensions: - -### Semantic Color -- **State indicators**: - - Success: Green tones (emerald, forest, mint) - - Error: Red/pink tones (rose, crimson, coral) - - Warning: Orange/amber tones - - Info: Blue tones (sky, ocean, indigo) - - Neutral: Gray/slate for inactive states - -- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) -- **Progress indicators**: Colored bars, rings, or charts showing completion or health - -### Accent Color Application -- **Primary actions**: Color the most important buttons/CTAs -- **Links**: Add color to clickable text (maintain accessibility) -- **Icons**: Colorize key icons for recognition and personality -- **Headers/titles**: Add color to section headers or key labels -- **Hover states**: Introduce color on interaction - -### Background & Surfaces -- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) -- **Colored sections**: Use subtle background colors to separate areas -- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) -- **Cards & surfaces**: Tint cards or surfaces slightly for warmth - -**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. - -### Data Visualization -- **Charts & graphs**: Use color to encode categories or values -- **Heatmaps**: Color intensity shows density or importance -- **Comparison**: Color coding for different datasets or timeframes - -### Borders & Accents -- **Accent borders**: Add colored left/top borders to cards or sections -- **Underlines**: Color underlines for emphasis or active states -- **Dividers**: Subtle colored dividers instead of gray lines -- **Focus rings**: Colored focus indicators matching brand - -### Typography Color -- **Colored headings**: Use brand colors for section headings (maintain contrast) -- **Highlight text**: Color for emphasis or categories -- **Labels & tags**: Small colored labels for metadata or categories - -### Decorative Elements -- **Illustrations**: Add colored illustrations or icons -- **Shapes**: Geometric shapes in brand colors as background elements -- **Gradients**: Colorful gradient overlays or mesh backgrounds -- **Blobs/organic shapes**: Soft colored shapes for visual interest - -## Balance & Refinement - -Ensure color addition improves rather than overwhelms: - -### Maintain Hierarchy -- **Dominant color** (60%): Primary brand color or most used accent -- **Secondary color** (30%): Supporting color for variety -- **Accent color** (10%): High contrast for key moments -- **Neutrals** (remaining): Gray/black/white for structure - -### Accessibility -- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) -- **Don't rely on color alone**: Use icons, labels, or patterns alongside color -- **Test for color blindness**: Verify red/green combinations work for all users - -### Cohesion -- **Consistent palette**: Use colors from defined palette, not arbitrary choices -- **Systematic application**: Same color meanings throughout (green always = success) -- **Temperature consistency**: Warm palette stays warm, cool stays cool - -**NEVER**: -- Use every color in the rainbow (choose 2-4 colors beyond neutrals) -- Apply color randomly without semantic meaning -- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead -- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication -- Use pure black (`#000`) or pure white (`#fff`) for large areas -- Violate WCAG contrast requirements -- Use color as the only indicator (accessibility issue) -- Make everything colorful (defeats the purpose) -- Default to purple-blue gradients (AI slop aesthetic) - -## Verify Color Addition - -Test that colorization improves the experience: - -- **Better hierarchy**: Does color guide attention appropriately? -- **Clearer meaning**: Does color help users understand states/categories? -- **More engaging**: Does the interface feel warmer and more inviting? -- **Still accessible**: Do all color combinations meet WCAG standards? -- **Not overwhelming**: Is color balanced and purposeful? - -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/.codex/skills/delight/SKILL.md b/.codex/skills/delight/SKILL.md deleted file mode 100644 index 01638978d..000000000 --- a/.codex/skills/delight/SKILL.md +++ /dev/null @@ -1,303 +0,0 @@ ---- -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. -version: 2.1.1 -argument-hint: "[target]" ---- - -Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach 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. \ No newline at end of file diff --git a/.codex/skills/distill/SKILL.md b/.codex/skills/distill/SKILL.md deleted file mode 100644 index 8cb1d40e2..000000000 --- a/.codex/skills/distill/SKILL.md +++ /dev/null @@ -1,121 +0,0 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -argument-hint: "[target]" ---- - -Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel complex or cluttered: - -1. **Identify complexity sources**: - - **Too many elements**: Competing buttons, redundant information, visual clutter - - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - - **Information overload**: Everything visible at once, no progressive disclosure - - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - - **Confusing hierarchy**: Unclear what matters most - - **Feature creep**: Too many options, actions, or paths forward - -2. **Find the essence**: - - What's the primary user goal? (There should be ONE) - - What's actually necessary vs nice-to-have? - - What can be removed, hidden, or combined? - - What's the 20% that delivers 80% of value? - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. - -## Plan Simplification - -Create a ruthless editing strategy: - -- **Core purpose**: What's the ONE thing this should accomplish? -- **Essential elements**: What's truly necessary to achieve that purpose? -- **Progressive disclosure**: What can be hidden until needed? -- **Consolidation opportunities**: What can be combined or integrated? - -**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. - -## Simplify the Design - -Systematically remove complexity across these dimensions: - -### Information Architecture -- **Reduce scope**: Remove secondary actions, optional features, redundant information -- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) -- **Combine related actions**: Merge similar buttons, consolidate forms, group related content -- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden -- **Remove redundancy**: If it's said elsewhere, don't repeat it here - -### Visual Simplification -- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors -- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights -- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function -- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards -- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead -- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps - -### Layout Simplification -- **Linear flow**: Replace complex grids with simple vertical flow where possible -- **Remove sidebars**: Move secondary content inline or hide it -- **Full-width**: Use available space generously instead of complex multi-column layouts -- **Consistent alignment**: Pick left or center, stick with it -- **Generous white space**: Let content breathe, don't pack everything tight - -### Interaction Simplification -- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) -- **Smart defaults**: Make common choices automatic, only ask when necessary -- **Inline actions**: Replace modal flows with inline editing where possible -- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? -- **Clear CTAs**: ONE obvious next step, not five competing actions - -### Content Simplification -- **Shorter copy**: Cut every sentence in half, then do it again -- **Active voice**: "Save changes" not "Changes will be saved" -- **Remove jargon**: Plain language always wins -- **Scannable structure**: Short paragraphs, bullet points, clear headings -- **Essential information only**: Remove marketing fluff, legalese, hedging -- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once - -### Code Simplification -- **Remove unused code**: Dead CSS, unused components, orphaned files -- **Flatten component trees**: Reduce nesting depth -- **Consolidate styles**: Merge similar styles, use utilities consistently -- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? - -**NEVER**: -- Remove necessary functionality (simplicity ≠ feature-less) -- Sacrifice accessibility for simplicity (clear labels and ARIA still required) -- Make things so simple they're unclear (mystery ≠ minimalism) -- Remove information users need to make decisions -- Eliminate hierarchy completely (some things should stand out) -- Oversimplify complex domains (match complexity to actual task complexity) - -## Verify Simplification - -Ensure simplification improves usability: - -- **Faster task completion**: Can users accomplish goals more quickly? -- **Reduced cognitive load**: Is it easier to understand what to do? -- **Still complete**: Are all necessary features still accessible? -- **Clearer hierarchy**: Is it obvious what matters most? -- **Better performance**: Does simpler design load faster? - -## Document Removed Complexity - -If you removed features or options: -- Document why they were removed -- Consider if they need alternative access points -- Note any user feedback to monitor - -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/.codex/skills/harden/SKILL.md b/.codex/skills/harden/SKILL.md deleted file mode 100644 index ccfa6f644..000000000 --- a/.codex/skills/harden/SKILL.md +++ /dev/null @@ -1,388 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.codex/skills/impeccable/SKILL.md b/.codex/skills/impeccable/SKILL.md index 6dd46e1b6..b96bef77e 100644 --- a/.codex/skills/impeccable/SKILL.md +++ b/.codex/skills/impeccable/SKILL.md @@ -1,15 +1,17 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `$layout`, `/normalize` was folded into `$polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through $impeccable (e.g., `$impeccable audit`). I'll clean up the old standalone skill files. Use `$impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -22,8 +24,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -33,7 +33,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -269,7 +269,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -283,82 +283,96 @@ Remember: GPT is capable of extraordinary creative work. Don't hold back. Show w --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `$impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `$impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `$impeccable craft [feature]` - Shape, then build a feature end-to-end +> `$impeccable shape [feature]` - Plan UX/UI before writing code +> `$impeccable teach` - Set up design context for this project (one-time) +> `$impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `$impeccable critique [target]` - UX design review with heuristic scoring +> `$impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `$impeccable polish [target]` - Final quality pass before shipping +> `$impeccable bolder [target]` - Amplify safe/bland designs +> `$impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `$impeccable distill [target]` - Strip to essence, remove complexity +> `$impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `$impeccable animate [target]` - Add purposeful animations and motion +> `$impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `$impeccable typeset [target]` - Improve typography hierarchy and fonts +> `$impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `$impeccable delight [target]` - Add personality and memorable touches +> `$impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `$impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `$impeccable adapt [target]` - Adapt for different devices and screen sizes +> `$impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `$impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates $audit) +> `$impeccable unpin ` - Remove a pinned shortcut +> +> Or use `$impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke $impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `$impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `$audit` instead of `$impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .codex/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `$impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.cursor/skills/adapt/SKILL.md b/.codex/skills/impeccable/reference/adapt.md similarity index 90% rename from .cursor/skills/adapt/SKILL.md rename to .codex/skills/impeccable/reference/adapt.md index 35b00e3f9..249653d4c 100644 --- a/.cursor/skills/adapt/SKILL.md +++ b/.codex/skills/impeccable/reference/adapt.md @@ -1,14 +1,7 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 ---- +> **Additional context needed**: target platforms/devices and usage contexts. Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. --- @@ -194,4 +187,4 @@ Test thoroughly across contexts: - **Edge cases**: Very small screens (320px), very large screens (4K) - **Slow connections**: Test on throttled network -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.kiro/skills/animate/SKILL.md b/.codex/skills/impeccable/reference/animate.md similarity index 91% rename from .kiro/skills/animate/SKILL.md rename to .codex/skills/impeccable/reference/animate.md index 02294bc19..0186ce081 100644 --- a/.kiro/skills/animate/SKILL.md +++ b/.codex/skills/impeccable/reference/animate.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -170,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.codex/skills/audit/SKILL.md b/.codex/skills/impeccable/reference/audit.md similarity index 79% rename from .codex/skills/audit/SKILL.md rename to .codex/skills/impeccable/reference/audit.md index 84a55b188..a86b3be95 100644 --- a/.codex/skills/audit/SKILL.md +++ b/.codex/skills/impeccable/reference/audit.md @@ -1,16 +1,3 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -65,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -108,7 +95,7 @@ For each issue, document: - **Impact**: How it affects users - **WCAG/Standard**: Which standard it violates (if applicable) - **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: $animate, $quieter, $shape, $optimize, $adapt, $clarify, $layout, $distill, $delight, $audit, $harden, $polish, $bolder, $typeset, $critique, $colorize, $overdrive) +- **Suggested command**: Which command to use (prefer: $impeccable adapt, $impeccable animate, $impeccable audit, $impeccable bolder, $impeccable clarify, $impeccable colorize, $impeccable critique, $impeccable delight, $impeccable distill, $impeccable harden, $impeccable layout, $impeccable optimize, $impeccable overdrive, $impeccable polish, $impeccable quieter, $impeccable shape, $impeccable typeset) ### Patterns & Systemic Issues @@ -127,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `$command-name`** — Brief description (specific context from audit findings) 2. **[P?] `$command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: $animate, $quieter, $shape, $optimize, $adapt, $clarify, $layout, $distill, $delight, $audit, $harden, $polish, $bolder, $typeset, $critique, $colorize, $overdrive. Map findings to the most appropriate command. End with `$polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: $impeccable adapt, $impeccable animate, $impeccable audit, $impeccable bolder, $impeccable clarify, $impeccable colorize, $impeccable critique, $impeccable delight, $impeccable distill, $impeccable harden, $impeccable layout, $impeccable optimize, $impeccable overdrive, $impeccable polish, $impeccable quieter, $impeccable shape, $impeccable typeset. Map findings to the most appropriate command. End with `$impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `$audit` after fixes to see your score improve. +> Re-run `$impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. @@ -144,4 +131,4 @@ After presenting the summary, tell the user: - Forget to prioritize (everything can't be P0) - Report false positives without verification -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.cursor/skills/bolder/SKILL.md b/.codex/skills/impeccable/reference/bolder.md similarity index 88% rename from .cursor/skills/bolder/SKILL.md rename to .codex/skills/impeccable/reference/bolder.md index e276b4d0b..cb3481663 100644 --- a/.cursor/skills/bolder/SKILL.md +++ b/.codex/skills/impeccable/reference/bolder.md @@ -1,14 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -34,7 +25,7 @@ If any of these are unclear from the codebase, ask the user directly to clarify **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -52,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -112,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.kiro/skills/clarify/SKILL.md b/.codex/skills/impeccable/reference/clarify.md similarity index 89% rename from .kiro/skills/clarify/SKILL.md rename to .codex/skills/impeccable/reference/clarify.md index 468541090..dc116e745 100644 --- a/.kiro/skills/clarify/SKILL.md +++ b/.codex/skills/impeccable/reference/clarify.md @@ -1,14 +1,7 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 ---- +> **Additional context needed**: audience technical level and users' mental state in context. Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. --- @@ -178,4 +171,4 @@ Test that copy improvements work: - **Consistency**: Does it match terminology elsewhere? - **Tone**: Is it appropriate for the situation? -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.codex/skills/critique/reference/cognitive-load.md b/.codex/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .codex/skills/critique/reference/cognitive-load.md rename to .codex/skills/impeccable/reference/cognitive-load.md diff --git a/.gemini/skills/colorize/SKILL.md b/.codex/skills/impeccable/reference/colorize.md similarity index 90% rename from .gemini/skills/colorize/SKILL.md rename to .codex/skills/impeccable/reference/colorize.md index 509a71c06..a4ce5072e 100644 --- a/.gemini/skills/colorize/SKILL.md +++ b/.codex/skills/impeccable/reference/colorize.md @@ -1,14 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -138,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.codex/skills/impeccable/reference/craft.md b/.codex/skills/impeccable/reference/craft.md index 6748e3259..3b95aac83 100644 --- a/.codex/skills/impeccable/reference/craft.md +++ b/.codex/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run $shape, passing along whatever feature description the user provided. +Run $impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run $shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run $impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.codex/skills/critique/SKILL.md b/.codex/skills/impeccable/reference/critique.md similarity index 84% rename from .codex/skills/critique/SKILL.md rename to .codex/skills/impeccable/reference/critique.md index 185049999..41ec68c4d 100644 --- a/.codex/skills/critique/SKILL.md +++ b/.codex/skills/impeccable/reference/critique.md @@ -1,17 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -argument-hint: "[area (feature, page, component...)]" ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke $impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run $impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -29,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -43,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -93,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -139,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: $animate, $quieter, $shape, $optimize, $adapt, $clarify, $layout, $distill, $delight, $audit, $harden, $polish, $bolder, $typeset, $critique, $colorize, $overdrive) +- **Suggested command**: Which command could address this (from: $impeccable adapt, $impeccable animate, $impeccable audit, $impeccable bolder, $impeccable clarify, $impeccable colorize, $impeccable critique, $impeccable delight, $impeccable distill, $impeccable harden, $impeccable layout, $impeccable optimize, $impeccable overdrive, $impeccable polish, $impeccable quieter, $impeccable shape, $impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `AGENTS.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -175,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -183,7 +172,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene 1. **Priority direction**: Based on the issues found, ask which category matters most to the user right now. For example: "I found problems with visual hierarchy, color usage, and information overload. Which area should we tackle first?" Offer the top 2-3 issue categories as options. -2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer$bolder/more playful?" Offer 2-3 tonal directions as options based on what would fix the issues found. +2. **Design intent**: If the critique found a tonal mismatch, ask whether it was intentional. For example: "The interface feels clinical and corporate. Is that the intended tone, or should it feel warmer/bolder/more playful?" Offer 2-3 tonal directions as options based on what would fix the issues found. 3. **Scope**: Ask how much the user wants to take on. For example: "I found N issues. Want to address everything, or focus on the top 3?" Offer scope options like "Top 3 only", "All issues", "Critical issues only". @@ -195,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -208,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: $animate, $quieter, $shape, $optimize, $adapt, $clarify, $layout, $distill, $delight, $audit, $harden, $polish, $bolder, $typeset, $critique, $colorize, $overdrive +- Only recommend commands from: $impeccable adapt, $impeccable animate, $impeccable audit, $impeccable bolder, $impeccable clarify, $impeccable colorize, $impeccable critique, $impeccable delight, $impeccable distill, $impeccable harden, $impeccable layout, $impeccable optimize, $impeccable overdrive, $impeccable polish, $impeccable quieter, $impeccable shape, $impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `$polish` as the final step if any fixes were recommended +- End with `$impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `$critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `$impeccable critique` after fixes to see your score improve. diff --git a/.pi/skills/delight/SKILL.md b/.codex/skills/impeccable/reference/delight.md similarity index 92% rename from .pi/skills/delight/SKILL.md rename to .codex/skills/impeccable/reference/delight.md index f323738dd..8a781e70e 100644 --- a/.pi/skills/delight/SKILL.md +++ b/.codex/skills/impeccable/reference/delight.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -299,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.cursor/skills/distill/SKILL.md b/.codex/skills/impeccable/reference/distill.md similarity index 91% rename from .cursor/skills/distill/SKILL.md rename to .codex/skills/impeccable/reference/distill.md index e462d1c27..4f47dc0b4 100644 --- a/.cursor/skills/distill/SKILL.md +++ b/.codex/skills/impeccable/reference/distill.md @@ -1,14 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -117,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.gemini/skills/harden/SKILL.md b/.codex/skills/impeccable/reference/harden.md similarity index 96% rename from .gemini/skills/harden/SKILL.md rename to .codex/skills/impeccable/reference/harden.md index 78eaa9881..af8b8a703 100644 --- a/.gemini/skills/harden/SKILL.md +++ b/.codex/skills/impeccable/reference/harden.md @@ -1,9 +1,3 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 ---- - Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. ## Assess Hardening Needs @@ -384,4 +378,4 @@ Test thoroughly with edge cases: - **Errors**: Force API errors, test all error states - **Empty**: Remove all data, test empty states -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.codex/skills/critique/reference/heuristics-scoring.md b/.codex/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .codex/skills/critique/reference/heuristics-scoring.md rename to .codex/skills/impeccable/reference/heuristics-scoring.md diff --git a/.kiro/skills/layout/SKILL.md b/.codex/skills/impeccable/reference/layout.md similarity index 89% rename from .kiro/skills/layout/SKILL.md rename to .codex/skills/impeccable/reference/layout.md index e3355c314..cd6b778e7 100644 --- a/.kiro/skills/layout/SKILL.md +++ b/.codex/skills/impeccable/reference/layout.md @@ -1,14 +1,5 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 ---- - Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak about the current spatial design: ## Plan Layout Improvements -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. Create a systematic plan: @@ -120,4 +111,4 @@ Create a systematic plan: - **Consistency**: Is the spacing system applied uniformly? - **Responsiveness**: Does the layout adapt gracefully across screen sizes? -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.pi/skills/optimize/SKILL.md b/.codex/skills/impeccable/reference/optimize.md similarity index 96% rename from .pi/skills/optimize/SKILL.md rename to .codex/skills/impeccable/reference/optimize.md index 6d82e1265..4abf575ec 100644 --- a/.pi/skills/optimize/SKILL.md +++ b/.codex/skills/impeccable/reference/optimize.md @@ -1,9 +1,3 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 ---- - Identify and fix performance issues to create faster, smoother user experiences. ## Assess Performance Issues @@ -261,4 +255,4 @@ Test that optimizations worked: - **No regressions**: Ensure functionality still works - **User perception**: Does it *feel* faster? -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.cursor/skills/overdrive/SKILL.md b/.codex/skills/impeccable/reference/overdrive.md similarity index 78% rename from .cursor/skills/overdrive/SKILL.md rename to .codex/skills/impeccable/reference/overdrive.md index 11bd0f4a8..d84a147dc 100644 --- a/.cursor/skills/overdrive/SKILL.md +++ b/.codex/skills/impeccable/reference/overdrive.md @@ -1,9 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 ---- - Start your response with: ``` @@ -11,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -31,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -89,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -126,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -137,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.codex/skills/critique/reference/personas.md b/.codex/skills/impeccable/reference/personas.md similarity index 100% rename from .codex/skills/critique/reference/personas.md rename to .codex/skills/impeccable/reference/personas.md diff --git a/.gemini/skills/polish/SKILL.md b/.codex/skills/impeccable/reference/polish.md similarity index 93% rename from .gemini/skills/polish/SKILL.md rename to .codex/skills/impeccable/reference/polish.md index 4c84dc128..597c68847 100644 --- a/.gemini/skills/polish/SKILL.md +++ b/.codex/skills/impeccable/reference/polish.md @@ -1,14 +1,4 @@ ---- -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. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: quality bar (MVP vs flagship). - ---- +> **Additional context needed**: 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. @@ -219,4 +209,4 @@ After polishing, ensure code quality: - **Consolidate tokens**: If you introduced new values, check whether they should be tokens. - **Verify DRYness**: Look for duplication introduced during polishing and consolidate. -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. \ No newline at end of file +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. diff --git a/.gemini/skills/quieter/SKILL.md b/.codex/skills/impeccable/reference/quieter.md similarity index 89% rename from .gemini/skills/quieter/SKILL.md rename to .codex/skills/impeccable/reference/quieter.md index ca17da694..a8ad41809 100644 --- a/.gemini/skills/quieter/SKILL.md +++ b/.codex/skills/impeccable/reference/quieter.md @@ -1,14 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -98,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.codex/skills/shape/SKILL.md b/.codex/skills/impeccable/reference/shape.md similarity index 79% rename from .codex/skills/shape/SKILL.md rename to .codex/skills/impeccable/reference/shape.md index 3e747afc2..8a6701e0f 100644 --- a/.codex/skills/shape/SKILL.md +++ b/.codex/skills/impeccable/reference/shape.md @@ -1,25 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -argument-hint: "[feature to shape]" ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke $impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run $impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to $impeccable craft, $impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to $impeccable craft, or directly to $impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -57,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -92,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to $impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use $impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to $impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use $impeccable craft instead, which runs this command internally.) diff --git a/.codex/skills/impeccable/reference/teach.md b/.codex/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..2d9f768f1 --- /dev/null +++ b/.codex/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.kiro/skills/typeset/SKILL.md b/.codex/skills/impeccable/reference/typeset.md similarity index 87% rename from .kiro/skills/typeset/SKILL.md rename to .codex/skills/impeccable/reference/typeset.md index a5fff11a8..2e49ab6c0 100644 --- a/.kiro/skills/typeset/SKILL.md +++ b/.codex/skills/impeccable/reference/typeset.md @@ -1,14 +1,5 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 ---- - Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak or generic about the current type: ## Plan Typography Improvements -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. Create a systematic plan: @@ -111,4 +102,4 @@ Build a clear type scale: - **Performance**: Are web fonts loading efficiently without layout shift? - **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.codex/skills/impeccable/scripts/cleanup-deprecated.mjs b/.codex/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.codex/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.codex/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.codex/skills/impeccable/scripts/command-metadata.json b/.codex/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.codex/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.codex/skills/impeccable/scripts/pin.mjs b/.codex/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.codex/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.codex/skills/layout/SKILL.md b/.codex/skills/layout/SKILL.md deleted file mode 100644 index 0e212c0b6..000000000 --- a/.codex/skills/layout/SKILL.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.codex/skills/optimize/SKILL.md b/.codex/skills/optimize/SKILL.md deleted file mode 100644 index a9ec152d4..000000000 --- a/.codex/skills/optimize/SKILL.md +++ /dev/null @@ -1,265 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.codex/skills/overdrive/SKILL.md b/.codex/skills/overdrive/SKILL.md deleted file mode 100644 index c63cbb867..000000000 --- a/.codex/skills/overdrive/SKILL.md +++ /dev/null @@ -1,141 +0,0 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -argument-hint: "[target]" ---- - -Start your response with: - -``` -──────────── ⚡ OVERDRIVE ───────────── -》》》 Entering overdrive mode... -``` - -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. - -### Propose Before Building - -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: - -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. -2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). -3. Only proceed with the direction the user confirms. - -Skipping this step risks building something embarrassing that needs to be thrown away. - -### Iterate with Browser Automation - -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. - ---- - -## Assess What "Extraordinary" Means Here - -The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** - -### For visual/marketing surfaces -Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. - -### For functional UI -Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. - -### For performance-critical UI -The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. - -### For data-heavy interfaces -Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. - -**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. - -## The Toolkit - -Organized by what you're trying to achieve, not by technology name. - -### Make transitions feel cinematic -- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. -- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes -- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. - -### Tie animation to scroll position -- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) - -### Render beyond CSS -- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. -- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. -- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. -- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. - -### Make data feel alive -- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. -- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. -- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. - -### Animate complex properties -- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. -- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. - -### Push performance boundaries -- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. -- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. -- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. - -### Interact with the device -- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. -- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. - -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. - -## Implement with Discipline - -### Progressive enhancement is non-negotiable - -Every technique must degrade gracefully. The experience without the enhancement must still be good. - -```css -@supports (animation-timeline: scroll()) { - .hero { animation-timeline: scroll(); } -} -``` - -```javascript -if ('gpu' in navigator) { /* WebGPU */ } -else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } -/* CSS-only fallback must still look good */ -``` - -### Performance rules - -- Target 60fps. If dropping below 50, simplify. -- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. -- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. -- Pause off-screen rendering. Kill what you can't see. -- Test on real mid-range devices, not just your development machine. - -### Polish is the difference - -The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. - -**NEVER**: -- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion -- Ship effects that cause jank on mid-range devices -- Use bleeding-edge APIs without a functional fallback -- Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills -- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise - -## Verify the Result - -- **The wow test**: Show it to someone who hasn't seen it. Do they react? -- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? -- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? -- **The accessibility test**: Enable reduced motion. Still beautiful? -- **The context test**: Does this make sense for THIS brand and audience? - -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file diff --git a/.codex/skills/polish/SKILL.md b/.codex/skills/polish/SKILL.md deleted file mode 100644 index 47fe1199e..000000000 --- a/.codex/skills/polish/SKILL.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -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. -version: 2.1.1 -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.codex/skills/quieter/SKILL.md b/.codex/skills/quieter/SKILL.md deleted file mode 100644 index b01b87eb5..000000000 --- a/.codex/skills/quieter/SKILL.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -argument-hint: "[target]" ---- - -Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too intense: - -1. **Identify intensity sources**: - - **Color saturation**: Overly bright or saturated colors - - **Contrast extremes**: Too much high-contrast juxtaposition - - **Visual weight**: Too many bold, heavy elements competing - - **Animation excess**: Too much motion or overly dramatic effects - - **Complexity**: Too many visual elements, patterns, or decorations - - **Scale**: Everything is large and loud with no hierarchy - -2. **Understand the context**: - - What's the purpose? (Marketing vs tool vs reading experience) - - Who's the audience? (Some contexts need energy) - - What's working? (Don't throw away good ideas) - - What's the core message? (Preserve what matters) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. - -## Plan Refinement - -Create a strategy to reduce intensity while maintaining impact: - -- **Color approach**: Desaturate or shift to more sophisticated tones? -- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? -- **Simplification approach**: What can be removed entirely? -- **Sophistication approach**: How can we signal quality through restraint? - -**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. - -## Refine the Design - -Systematically reduce intensity across these dimensions: - -### Color Refinement -- **Reduce saturation**: Shift from fully saturated to 70-85% saturation -- **Soften palette**: Replace bright colors with muted, sophisticated tones -- **Reduce color variety**: Use fewer colors more thoughtfully -- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) -- **Gentler contrasts**: High contrast only where it matters most -- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness -- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead - -### Visual Weight Reduction -- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate -- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness -- **White space**: Increase breathing room, reduce density -- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely - -### Simplification -- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose -- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes -- **Reduce layering**: Flatten visual hierarchy where possible -- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows - -### Motion Reduction -- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing -- **Remove decorative animations**: Keep functional motion, remove flourishes -- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback -- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic -- **Remove animations entirely** if they're not serving a clear purpose - -### Composition Refinement -- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling -- **Align to grid**: Bring rogue elements back into systematic alignment -- **Even out spacing**: Replace extreme spacing variations with consistent rhythm - -**NEVER**: -- Make everything the same size/weight (hierarchy still matters) -- Remove all color (quiet ≠ grayscale) -- Eliminate all personality (maintain character through refinement) -- Sacrifice usability for aesthetics (functional elements still need clear affordances) -- Make everything small and light (some anchors needed) - -## Verify Quality - -Ensure refinement maintains quality: - -- **Still functional**: Can users still accomplish tasks easily? -- **Still distinctive**: Does it have character, or is it generic now? -- **Better reading**: Is text easier to read for extended periods? -- **Sophistication**: Does it feel more refined and premium? - -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/.codex/skills/typeset/SKILL.md b/.codex/skills/typeset/SKILL.md deleted file mode 100644 index 3a371d1c2..000000000 --- a/.codex/skills/typeset/SKILL.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke $impeccable — 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 $impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.cursor/skills/impeccable/SKILL.md b/.cursor/skills/impeccable/SKILL.md index 8893bb42a..79ed6debb 100644 --- a/.cursor/skills/impeccable/SKILL.md +++ b/.cursor/skills/impeccable/SKILL.md @@ -1,14 +1,16 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -21,8 +23,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -32,7 +32,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -268,7 +268,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -282,82 +282,96 @@ Remember: the model is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .cursor/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .cursorrules. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.kiro/skills/adapt/SKILL.md b/.cursor/skills/impeccable/reference/adapt.md similarity index 90% rename from .kiro/skills/adapt/SKILL.md rename to .cursor/skills/impeccable/reference/adapt.md index 35b00e3f9..249653d4c 100644 --- a/.kiro/skills/adapt/SKILL.md +++ b/.cursor/skills/impeccable/reference/adapt.md @@ -1,14 +1,7 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 ---- +> **Additional context needed**: target platforms/devices and usage contexts. Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. --- @@ -194,4 +187,4 @@ Test thoroughly across contexts: - **Edge cases**: Very small screens (320px), very large screens (4K) - **Slow connections**: Test on throttled network -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.cursor/skills/animate/SKILL.md b/.cursor/skills/impeccable/reference/animate.md similarity index 91% rename from .cursor/skills/animate/SKILL.md rename to .cursor/skills/impeccable/reference/animate.md index 02294bc19..0186ce081 100644 --- a/.cursor/skills/animate/SKILL.md +++ b/.cursor/skills/impeccable/reference/animate.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -170,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.pi/skills/audit/SKILL.md b/.cursor/skills/impeccable/reference/audit.md similarity index 80% rename from .pi/skills/audit/SKILL.md rename to .cursor/skills/impeccable/reference/audit.md index 7fddc7b21..206fafb5c 100644 --- a/.pi/skills/audit/SKILL.md +++ b/.cursor/skills/impeccable/reference/audit.md @@ -1,15 +1,3 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -64,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -107,7 +95,7 @@ For each issue, document: - **Impact**: How it affects users - **WCAG/Standard**: Which standard it violates (if applicable) - **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) ### Patterns & Systemic Issues @@ -126,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `/command-name`** — Brief description (specific context from audit findings) 2. **[P?] `/command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/audit` after fixes to see your score improve. +> Re-run `/impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. @@ -143,4 +131,4 @@ After presenting the summary, tell the user: - Forget to prioritize (everything can't be P0) - Report false positives without verification -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.gemini/skills/bolder/SKILL.md b/.cursor/skills/impeccable/reference/bolder.md similarity index 88% rename from .gemini/skills/bolder/SKILL.md rename to .cursor/skills/impeccable/reference/bolder.md index e276b4d0b..cb3481663 100644 --- a/.gemini/skills/bolder/SKILL.md +++ b/.cursor/skills/impeccable/reference/bolder.md @@ -1,14 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -34,7 +25,7 @@ If any of these are unclear from the codebase, ask the user directly to clarify **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -52,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -112,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.cursor/skills/clarify/SKILL.md b/.cursor/skills/impeccable/reference/clarify.md similarity index 89% rename from .cursor/skills/clarify/SKILL.md rename to .cursor/skills/impeccable/reference/clarify.md index 468541090..dc116e745 100644 --- a/.cursor/skills/clarify/SKILL.md +++ b/.cursor/skills/impeccable/reference/clarify.md @@ -1,14 +1,7 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 ---- +> **Additional context needed**: audience technical level and users' mental state in context. Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. --- @@ -178,4 +171,4 @@ Test that copy improvements work: - **Consistency**: Does it match terminology elsewhere? - **Tone**: Is it appropriate for the situation? -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.cursor/skills/critique/reference/cognitive-load.md b/.cursor/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .cursor/skills/critique/reference/cognitive-load.md rename to .cursor/skills/impeccable/reference/cognitive-load.md diff --git a/.cursor/skills/colorize/SKILL.md b/.cursor/skills/impeccable/reference/colorize.md similarity index 90% rename from .cursor/skills/colorize/SKILL.md rename to .cursor/skills/impeccable/reference/colorize.md index 509a71c06..a4ce5072e 100644 --- a/.cursor/skills/colorize/SKILL.md +++ b/.cursor/skills/impeccable/reference/colorize.md @@ -1,14 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -138,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.cursor/skills/impeccable/reference/craft.md b/.cursor/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.cursor/skills/impeccable/reference/craft.md +++ b/.cursor/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.cursor/skills/critique/SKILL.md b/.cursor/skills/impeccable/reference/critique.md similarity index 85% rename from .cursor/skills/critique/SKILL.md rename to .cursor/skills/impeccable/reference/critique.md index addaa3224..8a8ebeb35 100644 --- a/.cursor/skills/critique/SKILL.md +++ b/.cursor/skills/impeccable/reference/critique.md @@ -1,16 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -28,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -42,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -92,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -138,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `.cursorrules` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -174,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -194,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -207,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.cursor/skills/delight/SKILL.md b/.cursor/skills/impeccable/reference/delight.md similarity index 92% rename from .cursor/skills/delight/SKILL.md rename to .cursor/skills/impeccable/reference/delight.md index f323738dd..8a781e70e 100644 --- a/.cursor/skills/delight/SKILL.md +++ b/.cursor/skills/impeccable/reference/delight.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -299,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.kiro/skills/distill/SKILL.md b/.cursor/skills/impeccable/reference/distill.md similarity index 91% rename from .kiro/skills/distill/SKILL.md rename to .cursor/skills/impeccable/reference/distill.md index e462d1c27..4f47dc0b4 100644 --- a/.kiro/skills/distill/SKILL.md +++ b/.cursor/skills/impeccable/reference/distill.md @@ -1,14 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -117,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.kiro/skills/harden/SKILL.md b/.cursor/skills/impeccable/reference/harden.md similarity index 96% rename from .kiro/skills/harden/SKILL.md rename to .cursor/skills/impeccable/reference/harden.md index 78eaa9881..af8b8a703 100644 --- a/.kiro/skills/harden/SKILL.md +++ b/.cursor/skills/impeccable/reference/harden.md @@ -1,9 +1,3 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 ---- - Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. ## Assess Hardening Needs @@ -384,4 +378,4 @@ Test thoroughly with edge cases: - **Errors**: Force API errors, test all error states - **Empty**: Remove all data, test empty states -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.cursor/skills/critique/reference/heuristics-scoring.md b/.cursor/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .cursor/skills/critique/reference/heuristics-scoring.md rename to .cursor/skills/impeccable/reference/heuristics-scoring.md diff --git a/.cursor/skills/layout/SKILL.md b/.cursor/skills/impeccable/reference/layout.md similarity index 89% rename from .cursor/skills/layout/SKILL.md rename to .cursor/skills/impeccable/reference/layout.md index e3355c314..cd6b778e7 100644 --- a/.cursor/skills/layout/SKILL.md +++ b/.cursor/skills/impeccable/reference/layout.md @@ -1,14 +1,5 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 ---- - Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak about the current spatial design: ## Plan Layout Improvements -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. Create a systematic plan: @@ -120,4 +111,4 @@ Create a systematic plan: - **Consistency**: Is the spacing system applied uniformly? - **Responsiveness**: Does the layout adapt gracefully across screen sizes? -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.kiro/skills/optimize/SKILL.md b/.cursor/skills/impeccable/reference/optimize.md similarity index 96% rename from .kiro/skills/optimize/SKILL.md rename to .cursor/skills/impeccable/reference/optimize.md index 6d82e1265..4abf575ec 100644 --- a/.kiro/skills/optimize/SKILL.md +++ b/.cursor/skills/impeccable/reference/optimize.md @@ -1,9 +1,3 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 ---- - Identify and fix performance issues to create faster, smoother user experiences. ## Assess Performance Issues @@ -261,4 +255,4 @@ Test that optimizations worked: - **No regressions**: Ensure functionality still works - **User perception**: Does it *feel* faster? -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.kiro/skills/overdrive/SKILL.md b/.cursor/skills/impeccable/reference/overdrive.md similarity index 78% rename from .kiro/skills/overdrive/SKILL.md rename to .cursor/skills/impeccable/reference/overdrive.md index 11bd0f4a8..d84a147dc 100644 --- a/.kiro/skills/overdrive/SKILL.md +++ b/.cursor/skills/impeccable/reference/overdrive.md @@ -1,9 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 ---- - Start your response with: ``` @@ -11,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -31,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -89,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -126,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -137,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.cursor/skills/critique/reference/personas.md b/.cursor/skills/impeccable/reference/personas.md similarity index 100% rename from .cursor/skills/critique/reference/personas.md rename to .cursor/skills/impeccable/reference/personas.md diff --git a/.kiro/skills/polish/SKILL.md b/.cursor/skills/impeccable/reference/polish.md similarity index 93% rename from .kiro/skills/polish/SKILL.md rename to .cursor/skills/impeccable/reference/polish.md index 4c84dc128..597c68847 100644 --- a/.kiro/skills/polish/SKILL.md +++ b/.cursor/skills/impeccable/reference/polish.md @@ -1,14 +1,4 @@ ---- -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. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: quality bar (MVP vs flagship). - ---- +> **Additional context needed**: 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. @@ -219,4 +209,4 @@ After polishing, ensure code quality: - **Consolidate tokens**: If you introduced new values, check whether they should be tokens. - **Verify DRYness**: Look for duplication introduced during polishing and consolidate. -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. \ No newline at end of file +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. diff --git a/.cursor/skills/quieter/SKILL.md b/.cursor/skills/impeccable/reference/quieter.md similarity index 89% rename from .cursor/skills/quieter/SKILL.md rename to .cursor/skills/impeccable/reference/quieter.md index ca17da694..a8ad41809 100644 --- a/.cursor/skills/quieter/SKILL.md +++ b/.cursor/skills/impeccable/reference/quieter.md @@ -1,14 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -98,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.pi/skills/shape/SKILL.md b/.cursor/skills/impeccable/reference/shape.md similarity index 80% rename from .pi/skills/shape/SKILL.md rename to .cursor/skills/impeccable/reference/shape.md index 6a94ee74c..0ae281943 100644 --- a/.pi/skills/shape/SKILL.md +++ b/.cursor/skills/impeccable/reference/shape.md @@ -1,24 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -56,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -91,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.cursor/skills/impeccable/reference/teach.md b/.cursor/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..952cf898a --- /dev/null +++ b/.cursor/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .cursorrules. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.pi/skills/typeset/SKILL.md b/.cursor/skills/impeccable/reference/typeset.md similarity index 87% rename from .pi/skills/typeset/SKILL.md rename to .cursor/skills/impeccable/reference/typeset.md index a5fff11a8..2e49ab6c0 100644 --- a/.pi/skills/typeset/SKILL.md +++ b/.cursor/skills/impeccable/reference/typeset.md @@ -1,14 +1,5 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 ---- - Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -45,7 +36,7 @@ Analyze what's weak or generic about the current type: ## Plan Typography Improvements -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. Create a systematic plan: @@ -111,4 +102,4 @@ Build a clear type scale: - **Performance**: Are web fonts loading efficiently without layout shift? - **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.cursor/skills/impeccable/scripts/cleanup-deprecated.mjs b/.cursor/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.cursor/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.cursor/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.cursor/skills/impeccable/scripts/command-metadata.json b/.cursor/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.cursor/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.cursor/skills/impeccable/scripts/pin.mjs b/.cursor/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.cursor/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.gemini/skills/impeccable/SKILL.md b/.gemini/skills/impeccable/SKILL.md index 51433d569..49b489705 100644 --- a/.gemini/skills/impeccable/SKILL.md +++ b/.gemini/skills/impeccable/SKILL.md @@ -1,13 +1,15 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -20,8 +22,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -31,7 +31,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -267,7 +267,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -281,82 +281,96 @@ Remember: Gemini is capable of extraordinary creative work. Don't hold back. Sho --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .gemini/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to GEMINI.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.gemini/skills/impeccable/reference/adapt.md b/.gemini/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.gemini/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.pi/skills/animate/SKILL.md b/.gemini/skills/impeccable/reference/animate.md similarity index 91% rename from .pi/skills/animate/SKILL.md rename to .gemini/skills/impeccable/reference/animate.md index 02294bc19..0186ce081 100644 --- a/.pi/skills/animate/SKILL.md +++ b/.gemini/skills/impeccable/reference/animate.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -170,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.gemini/skills/audit/SKILL.md b/.gemini/skills/impeccable/reference/audit.md similarity index 80% rename from .gemini/skills/audit/SKILL.md rename to .gemini/skills/impeccable/reference/audit.md index 7fddc7b21..206fafb5c 100644 --- a/.gemini/skills/audit/SKILL.md +++ b/.gemini/skills/impeccable/reference/audit.md @@ -1,15 +1,3 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -64,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -107,7 +95,7 @@ For each issue, document: - **Impact**: How it affects users - **WCAG/Standard**: Which standard it violates (if applicable) - **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) ### Patterns & Systemic Issues @@ -126,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `/command-name`** — Brief description (specific context from audit findings) 2. **[P?] `/command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/audit` after fixes to see your score improve. +> Re-run `/impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. @@ -143,4 +131,4 @@ After presenting the summary, tell the user: - Forget to prioritize (everything can't be P0) - Report false positives without verification -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.kiro/skills/bolder/SKILL.md b/.gemini/skills/impeccable/reference/bolder.md similarity index 88% rename from .kiro/skills/bolder/SKILL.md rename to .gemini/skills/impeccable/reference/bolder.md index e276b4d0b..cb3481663 100644 --- a/.kiro/skills/bolder/SKILL.md +++ b/.gemini/skills/impeccable/reference/bolder.md @@ -1,14 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -34,7 +25,7 @@ If any of these are unclear from the codebase, ask the user directly to clarify **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -52,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -112,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.gemini/skills/impeccable/reference/clarify.md b/.gemini/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.gemini/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.gemini/skills/critique/reference/cognitive-load.md b/.gemini/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .gemini/skills/critique/reference/cognitive-load.md rename to .gemini/skills/impeccable/reference/cognitive-load.md diff --git a/.pi/skills/colorize/SKILL.md b/.gemini/skills/impeccable/reference/colorize.md similarity index 90% rename from .pi/skills/colorize/SKILL.md rename to .gemini/skills/impeccable/reference/colorize.md index 509a71c06..a4ce5072e 100644 --- a/.pi/skills/colorize/SKILL.md +++ b/.gemini/skills/impeccable/reference/colorize.md @@ -1,14 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -138,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.gemini/skills/impeccable/reference/craft.md b/.gemini/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.gemini/skills/impeccable/reference/craft.md +++ b/.gemini/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.gemini/skills/critique/SKILL.md b/.gemini/skills/impeccable/reference/critique.md similarity index 85% rename from .gemini/skills/critique/SKILL.md rename to .gemini/skills/impeccable/reference/critique.md index e7f74e8f1..aa3c4a64a 100644 --- a/.gemini/skills/critique/SKILL.md +++ b/.gemini/skills/impeccable/reference/critique.md @@ -1,16 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -28,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -42,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -92,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -138,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `GEMINI.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -174,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -194,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -207,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.gemini/skills/delight/SKILL.md b/.gemini/skills/impeccable/reference/delight.md similarity index 92% rename from .gemini/skills/delight/SKILL.md rename to .gemini/skills/impeccable/reference/delight.md index f323738dd..8a781e70e 100644 --- a/.gemini/skills/delight/SKILL.md +++ b/.gemini/skills/impeccable/reference/delight.md @@ -1,14 +1,7 @@ ---- -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. -version: 2.1.1 ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -299,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.pi/skills/distill/SKILL.md b/.gemini/skills/impeccable/reference/distill.md similarity index 91% rename from .pi/skills/distill/SKILL.md rename to .gemini/skills/impeccable/reference/distill.md index e462d1c27..4f47dc0b4 100644 --- a/.pi/skills/distill/SKILL.md +++ b/.gemini/skills/impeccable/reference/distill.md @@ -1,14 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -117,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.gemini/skills/impeccable/reference/harden.md b/.gemini/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.gemini/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.gemini/skills/critique/reference/heuristics-scoring.md b/.gemini/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .gemini/skills/critique/reference/heuristics-scoring.md rename to .gemini/skills/impeccable/reference/heuristics-scoring.md diff --git a/.gemini/skills/impeccable/reference/layout.md b/.gemini/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.gemini/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.gemini/skills/impeccable/reference/optimize.md b/.gemini/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.gemini/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.gemini/skills/overdrive/SKILL.md b/.gemini/skills/impeccable/reference/overdrive.md similarity index 78% rename from .gemini/skills/overdrive/SKILL.md rename to .gemini/skills/impeccable/reference/overdrive.md index 11bd0f4a8..d84a147dc 100644 --- a/.gemini/skills/overdrive/SKILL.md +++ b/.gemini/skills/impeccable/reference/overdrive.md @@ -1,9 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 ---- - Start your response with: ``` @@ -11,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -31,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -89,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -126,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -137,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.gemini/skills/critique/reference/personas.md b/.gemini/skills/impeccable/reference/personas.md similarity index 100% rename from .gemini/skills/critique/reference/personas.md rename to .gemini/skills/impeccable/reference/personas.md diff --git a/.gemini/skills/impeccable/reference/polish.md b/.gemini/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.gemini/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.pi/skills/quieter/SKILL.md b/.gemini/skills/impeccable/reference/quieter.md similarity index 89% rename from .pi/skills/quieter/SKILL.md rename to .gemini/skills/impeccable/reference/quieter.md index ca17da694..a8ad41809 100644 --- a/.pi/skills/quieter/SKILL.md +++ b/.gemini/skills/impeccable/reference/quieter.md @@ -1,14 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -98,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.gemini/skills/shape/SKILL.md b/.gemini/skills/impeccable/reference/shape.md similarity index 80% rename from .gemini/skills/shape/SKILL.md rename to .gemini/skills/impeccable/reference/shape.md index 6a94ee74c..0ae281943 100644 --- a/.gemini/skills/shape/SKILL.md +++ b/.gemini/skills/impeccable/reference/shape.md @@ -1,24 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -56,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -91,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.gemini/skills/impeccable/reference/teach.md b/.gemini/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..b081ec456 --- /dev/null +++ b/.gemini/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to GEMINI.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.gemini/skills/impeccable/reference/typeset.md b/.gemini/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.gemini/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.gemini/skills/impeccable/scripts/cleanup-deprecated.mjs b/.gemini/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.gemini/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.gemini/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.gemini/skills/impeccable/scripts/command-metadata.json b/.gemini/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.gemini/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.gemini/skills/impeccable/scripts/pin.mjs b/.gemini/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.gemini/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.gitignore b/.gitignore index 11df7dc33..c9ddacd18 100644 --- a/.gitignore +++ b/.gitignore @@ -15,7 +15,11 @@ Thumbs.db # IDE .vscode/ .idea/ + +# Claude Code local state .claude/projects/ +.claude/scheduled_tasks.lock +.claude/settings.local.json # Environment .env @@ -34,7 +38,12 @@ extension/detector/ evals/ # Generated sub-pages (built from source/skills + content/site at build time) -public/skills/ +public/docs/ public/anti-patterns/ public/tutorials/ public/visual-mode/ + +# Note: harness skill directories (.claude/skills/, .cursor/skills/, etc.) +# are intentionally tracked. npx skills reads them from this repo at install +# time, and they enable clean submodule use. Run `bun run build` to refresh +# them after editing source/skills/. diff --git a/.kiro/skills/impeccable/SKILL.md b/.kiro/skills/impeccable/SKILL.md index 5fe89dbc3..80efc2f9a 100644 --- a/.kiro/skills/impeccable/SKILL.md +++ b/.kiro/skills/impeccable/SKILL.md @@ -1,14 +1,16 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -21,8 +23,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -32,7 +32,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -268,7 +268,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -282,82 +282,96 @@ Remember: Claude is capable of extraordinary creative work. Don't hold back. Sho --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .kiro/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .kiro/settings.json. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.kiro/skills/impeccable/reference/adapt.md b/.kiro/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.kiro/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.kiro/skills/impeccable/reference/animate.md b/.kiro/skills/impeccable/reference/animate.md new file mode 100644 index 000000000..0186ce081 --- /dev/null +++ b/.kiro/skills/impeccable/reference/animate.md @@ -0,0 +1,166 @@ +> **Additional context needed**: performance constraints. + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + + +--- + +## 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. diff --git a/.kiro/skills/impeccable/reference/audit.md b/.kiro/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.kiro/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.kiro/skills/impeccable/reference/bolder.md b/.kiro/skills/impeccable/reference/bolder.md new file mode 100644 index 000000000..cb3481663 --- /dev/null +++ b/.kiro/skills/impeccable/reference/bolder.md @@ -0,0 +1,106 @@ +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.kiro/skills/impeccable/reference/clarify.md b/.kiro/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.kiro/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.kiro/skills/critique/reference/cognitive-load.md b/.kiro/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .kiro/skills/critique/reference/cognitive-load.md rename to .kiro/skills/impeccable/reference/cognitive-load.md diff --git a/.kiro/skills/impeccable/reference/colorize.md b/.kiro/skills/impeccable/reference/colorize.md new file mode 100644 index 000000000..a4ce5072e --- /dev/null +++ b/.kiro/skills/impeccable/reference/colorize.md @@ -0,0 +1,134 @@ +> **Additional context needed**: existing brand colors. + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.kiro/skills/impeccable/reference/craft.md b/.kiro/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.kiro/skills/impeccable/reference/craft.md +++ b/.kiro/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.kiro/skills/critique/SKILL.md b/.kiro/skills/impeccable/reference/critique.md similarity index 85% rename from .kiro/skills/critique/SKILL.md rename to .kiro/skills/impeccable/reference/critique.md index 4299a6156..2d9f41a65 100644 --- a/.kiro/skills/critique/SKILL.md +++ b/.kiro/skills/impeccable/reference/critique.md @@ -1,16 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -28,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -42,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -92,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -138,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `.kiro/settings.json` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -174,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -194,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -207,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.kiro/skills/impeccable/reference/delight.md b/.kiro/skills/impeccable/reference/delight.md new file mode 100644 index 000000000..8a781e70e --- /dev/null +++ b/.kiro/skills/impeccable/reference/delight.md @@ -0,0 +1,295 @@ +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + + +--- + +## 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. diff --git a/.kiro/skills/impeccable/reference/distill.md b/.kiro/skills/impeccable/reference/distill.md new file mode 100644 index 000000000..4f47dc0b4 --- /dev/null +++ b/.kiro/skills/impeccable/reference/distill.md @@ -0,0 +1,111 @@ +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.kiro/skills/impeccable/reference/harden.md b/.kiro/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.kiro/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.kiro/skills/critique/reference/heuristics-scoring.md b/.kiro/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .kiro/skills/critique/reference/heuristics-scoring.md rename to .kiro/skills/impeccable/reference/heuristics-scoring.md diff --git a/.kiro/skills/impeccable/reference/layout.md b/.kiro/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.kiro/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.kiro/skills/impeccable/reference/optimize.md b/.kiro/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.kiro/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.kiro/skills/impeccable/reference/overdrive.md b/.kiro/skills/impeccable/reference/overdrive.md new file mode 100644 index 000000000..d84a147dc --- /dev/null +++ b/.kiro/skills/impeccable/reference/overdrive.md @@ -0,0 +1,130 @@ +Start your response with: + +``` +──────────── ⚡ OVERDRIVE ───────────── +》》》 Entering overdrive mode... +``` + +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. + +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. + +### Propose Before Building + +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: + +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). +3. Only proceed with the direction the user confirms. + +Skipping this step risks building something embarrassing that needs to be thrown away. + +### Iterate with Browser Automation + +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. + +--- + +## Assess What "Extraordinary" Means Here + +The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** + +### For visual/marketing surfaces +Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. + +### For functional UI +Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. + +### For performance-critical UI +The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. + +### For data-heavy interfaces +Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. + +**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. + +## The Toolkit + +Organized by what you're trying to achieve, not by technology name. + +### Make transitions feel cinematic +- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. +- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes +- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. + +### Tie animation to scroll position +- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) + +### Render beyond CSS +- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. +- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. +- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. +- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. + +### Make data feel alive +- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. +- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. +- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. + +### Animate complex properties +- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. +- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. + +### Push performance boundaries +- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. +- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. +- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. + +### Interact with the device +- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. +- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. + +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. + +## Implement with Discipline + +### Progressive enhancement is non-negotiable + +Every technique must degrade gracefully. The experience without the enhancement must still be good. + +```css +@supports (animation-timeline: scroll()) { + .hero { animation-timeline: scroll(); } +} +``` + +```javascript +if ('gpu' in navigator) { /* WebGPU */ } +else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } +/* CSS-only fallback must still look good */ +``` + +### Performance rules + +- Target 60fps. If dropping below 50, simplify. +- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. +- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. +- Pause off-screen rendering. Kill what you can't see. +- Test on real mid-range devices, not just your development machine. + +### Polish is the difference + +The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. + +**NEVER**: +- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion +- Ship effects that cause jank on mid-range devices +- Use bleeding-edge APIs without a functional fallback +- Add sound without explicit user opt-in +- Use technical ambition to mask weak design fundamentals; fix those first with other commands +- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise + +## Verify the Result + +- **The wow test**: Show it to someone who hasn't seen it. Do they react? +- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? +- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? +- **The accessibility test**: Enable reduced motion. Still beautiful? +- **The context test**: Does this make sense for THIS brand and audience? + +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.kiro/skills/critique/reference/personas.md b/.kiro/skills/impeccable/reference/personas.md similarity index 100% rename from .kiro/skills/critique/reference/personas.md rename to .kiro/skills/impeccable/reference/personas.md diff --git a/.kiro/skills/impeccable/reference/polish.md b/.kiro/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.kiro/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.kiro/skills/impeccable/reference/quieter.md b/.kiro/skills/impeccable/reference/quieter.md new file mode 100644 index 000000000..a8ad41809 --- /dev/null +++ b/.kiro/skills/impeccable/reference/quieter.md @@ -0,0 +1,92 @@ +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.cursor/skills/shape/SKILL.md b/.kiro/skills/impeccable/reference/shape.md similarity index 80% rename from .cursor/skills/shape/SKILL.md rename to .kiro/skills/impeccable/reference/shape.md index 6a94ee74c..0ae281943 100644 --- a/.cursor/skills/shape/SKILL.md +++ b/.kiro/skills/impeccable/reference/shape.md @@ -1,24 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -56,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -91,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.kiro/skills/impeccable/reference/teach.md b/.kiro/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..046f6065d --- /dev/null +++ b/.kiro/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .kiro/settings.json. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.kiro/skills/impeccable/reference/typeset.md b/.kiro/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.kiro/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.kiro/skills/impeccable/scripts/cleanup-deprecated.mjs b/.kiro/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.kiro/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.kiro/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.kiro/skills/impeccable/scripts/command-metadata.json b/.kiro/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.kiro/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.kiro/skills/impeccable/scripts/pin.mjs b/.kiro/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.kiro/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.opencode/skills/adapt/SKILL.md b/.opencode/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.opencode/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.opencode/skills/audit/SKILL.md b/.opencode/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.opencode/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.opencode/skills/clarify/SKILL.md b/.opencode/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.opencode/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.opencode/skills/harden/SKILL.md b/.opencode/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.opencode/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.opencode/skills/impeccable/SKILL.md b/.opencode/skills/impeccable/SKILL.md index da88f1585..219cb7402 100644 --- a/.opencode/skills/impeccable/SKILL.md +++ b/.opencode/skills/impeccable/SKILL.md @@ -1,16 +1,20 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. +allowed-tools: + - Bash(npx impeccable *) --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +27,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +36,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +272,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +286,96 @@ Remember: Claude is capable of extraordinary creative work. Don't hold back. Sho --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -STOP and call the `question` tool to clarify. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .opencode/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then STOP and call the `question` tool to clarify. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.opencode/skills/impeccable/reference/adapt.md b/.opencode/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.opencode/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.opencode/skills/animate/SKILL.md b/.opencode/skills/impeccable/reference/animate.md similarity index 90% rename from .opencode/skills/animate/SKILL.md rename to .opencode/skills/impeccable/reference/animate.md index 4eb931b05..dfe993cea 100644 --- a/.opencode/skills/animate/SKILL.md +++ b/.opencode/skills/impeccable/reference/animate.md @@ -1,16 +1,7 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: performance constraints. --- @@ -172,4 +163,4 @@ Test animations thoroughly: - **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. \ No newline at end of file +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. diff --git a/.opencode/skills/impeccable/reference/audit.md b/.opencode/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.opencode/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.opencode/skills/bolder/SKILL.md b/.opencode/skills/impeccable/reference/bolder.md similarity index 87% rename from .opencode/skills/bolder/SKILL.md rename to .opencode/skills/impeccable/reference/bolder.md index d0f2d7367..57bdc739d 100644 --- a/.opencode/skills/bolder/SKILL.md +++ b/.opencode/skills/impeccable/reference/bolder.md @@ -1,16 +1,5 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -36,7 +25,7 @@ If any of these are unclear from the codebase, STOP and call the `question` tool **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -54,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) @@ -114,4 +103,4 @@ Ensure amplification maintains usability and coherence: **The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.opencode/skills/impeccable/reference/clarify.md b/.opencode/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.opencode/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.opencode/skills/critique/reference/cognitive-load.md b/.opencode/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .opencode/skills/critique/reference/cognitive-load.md rename to .opencode/skills/impeccable/reference/cognitive-load.md diff --git a/.opencode/skills/colorize/SKILL.md b/.opencode/skills/impeccable/reference/colorize.md similarity index 89% rename from .opencode/skills/colorize/SKILL.md rename to .opencode/skills/impeccable/reference/colorize.md index 86353330e..1a2ae7439 100644 --- a/.opencode/skills/colorize/SKILL.md +++ b/.opencode/skills/impeccable/reference/colorize.md @@ -1,16 +1,7 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. --- @@ -140,4 +131,4 @@ Test that colorization improves the experience: - **Still accessible**: Do all color combinations meet WCAG standards? - **Not overwhelming**: Is color balanced and purposeful? -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.opencode/skills/impeccable/reference/craft.md b/.opencode/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.opencode/skills/impeccable/reference/craft.md +++ b/.opencode/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.opencode/skills/critique/SKILL.md b/.opencode/skills/impeccable/reference/critique.md similarity index 84% rename from .opencode/skills/critique/SKILL.md rename to .opencode/skills/impeccable/reference/critique.md index e83febd6b..ea2c4d7a7 100644 --- a/.opencode/skills/critique/SKILL.md +++ b/.opencode/skills/impeccable/reference/critique.md @@ -1,20 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" -allowed-tools: - - Bash(npx impeccable *) ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -32,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -46,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -96,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -142,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `AGENTS.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -178,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. STOP and call the `question` tool to clarify. These answers will shape the action plan. @@ -198,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -211,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.opencode/skills/delight/SKILL.md b/.opencode/skills/impeccable/reference/delight.md similarity index 92% rename from .opencode/skills/delight/SKILL.md rename to .opencode/skills/impeccable/reference/delight.md index 1b105a666..ee529ce38 100644 --- a/.opencode/skills/delight/SKILL.md +++ b/.opencode/skills/impeccable/reference/delight.md @@ -1,16 +1,7 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- @@ -301,4 +292,4 @@ Test that delight actually delights: - **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. \ No newline at end of file +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. diff --git a/.opencode/skills/distill/SKILL.md b/.opencode/skills/impeccable/reference/distill.md similarity index 90% rename from .opencode/skills/distill/SKILL.md rename to .opencode/skills/impeccable/reference/distill.md index 9342d1298..f4239bfae 100644 --- a/.opencode/skills/distill/SKILL.md +++ b/.opencode/skills/impeccable/reference/distill.md @@ -1,16 +1,5 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -119,4 +108,4 @@ If you removed features or options: - Consider if they need alternative access points - Note any user feedback to monitor -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.opencode/skills/impeccable/reference/harden.md b/.opencode/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.opencode/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.opencode/skills/critique/reference/heuristics-scoring.md b/.opencode/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .opencode/skills/critique/reference/heuristics-scoring.md rename to .opencode/skills/impeccable/reference/heuristics-scoring.md diff --git a/.opencode/skills/impeccable/reference/layout.md b/.opencode/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.opencode/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.opencode/skills/impeccable/reference/optimize.md b/.opencode/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.opencode/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.opencode/skills/overdrive/SKILL.md b/.opencode/skills/impeccable/reference/overdrive.md similarity index 77% rename from .opencode/skills/overdrive/SKILL.md rename to .opencode/skills/impeccable/reference/overdrive.md index 50bd442fe..4059d7e91 100644 --- a/.opencode/skills/overdrive/SKILL.md +++ b/.opencode/skills/impeccable/reference/overdrive.md @@ -1,11 +1,3 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Start your response with: ``` @@ -13,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **STOP and call the `question` tool to clarify.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -33,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -91,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -128,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result @@ -139,4 +127,4 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - **The accessibility test**: Enable reduced motion. Still beautiful? - **The context test**: Does this make sense for THIS brand and audience? -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.opencode/skills/critique/reference/personas.md b/.opencode/skills/impeccable/reference/personas.md similarity index 100% rename from .opencode/skills/critique/reference/personas.md rename to .opencode/skills/impeccable/reference/personas.md diff --git a/.opencode/skills/impeccable/reference/polish.md b/.opencode/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.opencode/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.opencode/skills/quieter/SKILL.md b/.opencode/skills/impeccable/reference/quieter.md similarity index 88% rename from .opencode/skills/quieter/SKILL.md rename to .opencode/skills/impeccable/reference/quieter.md index b6b7b000b..89968b824 100644 --- a/.opencode/skills/quieter/SKILL.md +++ b/.opencode/skills/impeccable/reference/quieter.md @@ -1,16 +1,5 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. --- @@ -100,4 +89,4 @@ Ensure refinement maintains quality: - **Better reading**: Is text easier to read for extended periods? - **Sophistication**: Does it feel more refined and premium? -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.opencode/skills/shape/SKILL.md b/.opencode/skills/impeccable/reference/shape.md similarity index 79% rename from .opencode/skills/shape/SKILL.md rename to .opencode/skills/impeccable/reference/shape.md index 4a3464660..34453fcc9 100644 --- a/.opencode/skills/shape/SKILL.md +++ b/.opencode/skills/impeccable/reference/shape.md @@ -1,26 +1,12 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -58,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -93,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. STOP and call the `question` tool to clarify. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.opencode/skills/impeccable/reference/teach.md b/.opencode/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..c72139b7d --- /dev/null +++ b/.opencode/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +STOP and call the `question` tool to clarify. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then STOP and call the `question` tool to clarify. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.opencode/skills/impeccable/reference/typeset.md b/.opencode/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.opencode/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.opencode/skills/impeccable/scripts/cleanup-deprecated.mjs b/.opencode/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.opencode/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.opencode/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.opencode/skills/impeccable/scripts/command-metadata.json b/.opencode/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.opencode/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.opencode/skills/impeccable/scripts/pin.mjs b/.opencode/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.opencode/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.opencode/skills/layout/SKILL.md b/.opencode/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.opencode/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.opencode/skills/optimize/SKILL.md b/.opencode/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.opencode/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.opencode/skills/polish/SKILL.md b/.opencode/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.opencode/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.opencode/skills/typeset/SKILL.md b/.opencode/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.opencode/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.pi/skills/impeccable/SKILL.md b/.pi/skills/impeccable/SKILL.md index 43e327949..ea2f01ccd 100644 --- a/.pi/skills/impeccable/SKILL.md +++ b/.pi/skills/impeccable/SKILL.md @@ -1,14 +1,18 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. +allowed-tools: + - Bash(npx impeccable *) --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -21,8 +25,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -32,7 +34,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -268,7 +270,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -282,82 +284,96 @@ Remember: the model is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .pi/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.pi/skills/impeccable/reference/adapt.md b/.pi/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.pi/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.pi/skills/impeccable/reference/animate.md b/.pi/skills/impeccable/reference/animate.md new file mode 100644 index 000000000..0186ce081 --- /dev/null +++ b/.pi/skills/impeccable/reference/animate.md @@ -0,0 +1,166 @@ +> **Additional context needed**: performance constraints. + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + + +--- + +## 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. diff --git a/.pi/skills/impeccable/reference/audit.md b/.pi/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.pi/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.pi/skills/impeccable/reference/bolder.md b/.pi/skills/impeccable/reference/bolder.md new file mode 100644 index 000000000..cb3481663 --- /dev/null +++ b/.pi/skills/impeccable/reference/bolder.md @@ -0,0 +1,106 @@ +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.pi/skills/impeccable/reference/clarify.md b/.pi/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.pi/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.pi/skills/critique/reference/cognitive-load.md b/.pi/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .pi/skills/critique/reference/cognitive-load.md rename to .pi/skills/impeccable/reference/cognitive-load.md diff --git a/.pi/skills/impeccable/reference/colorize.md b/.pi/skills/impeccable/reference/colorize.md new file mode 100644 index 000000000..a4ce5072e --- /dev/null +++ b/.pi/skills/impeccable/reference/colorize.md @@ -0,0 +1,134 @@ +> **Additional context needed**: existing brand colors. + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.pi/skills/impeccable/reference/craft.md b/.pi/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.pi/skills/impeccable/reference/craft.md +++ b/.pi/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.pi/skills/critique/SKILL.md b/.pi/skills/impeccable/reference/critique.md similarity index 85% rename from .pi/skills/critique/SKILL.md rename to .pi/skills/impeccable/reference/critique.md index 29e0a1ce4..c282a6c80 100644 --- a/.pi/skills/critique/SKILL.md +++ b/.pi/skills/impeccable/reference/critique.md @@ -1,18 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -allowed-tools: - - Bash(npx impeccable *) ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -30,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -44,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -94,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -140,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `AGENTS.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -176,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -196,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -209,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.pi/skills/impeccable/reference/delight.md b/.pi/skills/impeccable/reference/delight.md new file mode 100644 index 000000000..8a781e70e --- /dev/null +++ b/.pi/skills/impeccable/reference/delight.md @@ -0,0 +1,295 @@ +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + + +--- + +## 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. diff --git a/.pi/skills/impeccable/reference/distill.md b/.pi/skills/impeccable/reference/distill.md new file mode 100644 index 000000000..4f47dc0b4 --- /dev/null +++ b/.pi/skills/impeccable/reference/distill.md @@ -0,0 +1,111 @@ +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.pi/skills/impeccable/reference/harden.md b/.pi/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.pi/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.pi/skills/critique/reference/heuristics-scoring.md b/.pi/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .pi/skills/critique/reference/heuristics-scoring.md rename to .pi/skills/impeccable/reference/heuristics-scoring.md diff --git a/.pi/skills/impeccable/reference/layout.md b/.pi/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.pi/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.pi/skills/impeccable/reference/optimize.md b/.pi/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.pi/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.pi/skills/impeccable/reference/overdrive.md b/.pi/skills/impeccable/reference/overdrive.md new file mode 100644 index 000000000..d84a147dc --- /dev/null +++ b/.pi/skills/impeccable/reference/overdrive.md @@ -0,0 +1,130 @@ +Start your response with: + +``` +──────────── ⚡ OVERDRIVE ───────────── +》》》 Entering overdrive mode... +``` + +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. + +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. + +### Propose Before Building + +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: + +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). +3. Only proceed with the direction the user confirms. + +Skipping this step risks building something embarrassing that needs to be thrown away. + +### Iterate with Browser Automation + +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. + +--- + +## Assess What "Extraordinary" Means Here + +The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** + +### For visual/marketing surfaces +Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. + +### For functional UI +Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. + +### For performance-critical UI +The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. + +### For data-heavy interfaces +Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. + +**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. + +## The Toolkit + +Organized by what you're trying to achieve, not by technology name. + +### Make transitions feel cinematic +- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. +- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes +- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. + +### Tie animation to scroll position +- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) + +### Render beyond CSS +- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. +- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. +- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. +- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. + +### Make data feel alive +- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. +- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. +- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. + +### Animate complex properties +- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. +- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. + +### Push performance boundaries +- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. +- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. +- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. + +### Interact with the device +- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. +- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. + +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. + +## Implement with Discipline + +### Progressive enhancement is non-negotiable + +Every technique must degrade gracefully. The experience without the enhancement must still be good. + +```css +@supports (animation-timeline: scroll()) { + .hero { animation-timeline: scroll(); } +} +``` + +```javascript +if ('gpu' in navigator) { /* WebGPU */ } +else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } +/* CSS-only fallback must still look good */ +``` + +### Performance rules + +- Target 60fps. If dropping below 50, simplify. +- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. +- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. +- Pause off-screen rendering. Kill what you can't see. +- Test on real mid-range devices, not just your development machine. + +### Polish is the difference + +The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. + +**NEVER**: +- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion +- Ship effects that cause jank on mid-range devices +- Use bleeding-edge APIs without a functional fallback +- Add sound without explicit user opt-in +- Use technical ambition to mask weak design fundamentals; fix those first with other commands +- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise + +## Verify the Result + +- **The wow test**: Show it to someone who hasn't seen it. Do they react? +- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? +- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? +- **The accessibility test**: Enable reduced motion. Still beautiful? +- **The context test**: Does this make sense for THIS brand and audience? + +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.pi/skills/critique/reference/personas.md b/.pi/skills/impeccable/reference/personas.md similarity index 100% rename from .pi/skills/critique/reference/personas.md rename to .pi/skills/impeccable/reference/personas.md diff --git a/.pi/skills/impeccable/reference/polish.md b/.pi/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.pi/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.pi/skills/impeccable/reference/quieter.md b/.pi/skills/impeccable/reference/quieter.md new file mode 100644 index 000000000..a8ad41809 --- /dev/null +++ b/.pi/skills/impeccable/reference/quieter.md @@ -0,0 +1,92 @@ +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.pi/skills/impeccable/reference/shape.md b/.pi/skills/impeccable/reference/shape.md new file mode 100644 index 000000000..0ae281943 --- /dev/null +++ b/.pi/skills/impeccable/reference/shape.md @@ -0,0 +1,82 @@ +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. + +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. + +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. + +## Philosophy + +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. + +## Phase 1: Discovery Interview + +**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. + +Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. + +### Purpose & Context +- What is this feature for? What problem does it solve? +- Who specifically will use it? (Not "users"; be specific: role, context, frequency) +- What does success look like? How will you know this feature is working? +- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) + +### Content & Data +- What content or data does this feature display or collect? +- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) +- What are the edge cases? (Empty state, error state, first-time use, power user) +- Is any content dynamic? What changes and how often? + +### Design Goals +- What's the single most important thing a user should do or understand here? +- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) +- Are there existing patterns in the product this should be consistent with? +- Are there specific examples (inside or outside the product) that capture what you're going for? + +### Constraints +- Are there technical constraints? (Framework, performance budget, browser support) +- Are there content constraints? (Localization, dynamic text length, user-generated content) +- Mobile/responsive requirements? +- Accessibility requirements beyond WCAG AA? + +### Anti-Goals +- What should this NOT be? What would be a wrong direction? +- What's the biggest risk of getting this wrong? + +## Phase 2: Design Brief + +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. + +### Brief Structure + +**1. Feature Summary** (2-3 sentences) +What this is, who it's for, what it needs to accomplish. + +**2. Primary User Action** +The single most important thing a user should do or understand here. + +**3. Design Direction** +How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. + +**4. Layout Strategy** +High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. + +**5. Key States** +List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. + +**6. Interaction Model** +How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? + +**7. Content Requirements** +What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. + +**8. Recommended References** +Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). + +**9. Open Questions** +Anything unresolved that the implementer should resolve during build. + +--- + +ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. + +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.pi/skills/impeccable/reference/teach.md b/.pi/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..2d9f768f1 --- /dev/null +++ b/.pi/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.pi/skills/impeccable/reference/typeset.md b/.pi/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.pi/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.pi/skills/impeccable/scripts/cleanup-deprecated.mjs b/.pi/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.pi/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.pi/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.pi/skills/impeccable/scripts/command-metadata.json b/.pi/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.pi/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.pi/skills/impeccable/scripts/pin.mjs b/.pi/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.pi/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.rovodev/skills/adapt/SKILL.md b/.rovodev/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.rovodev/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.rovodev/skills/animate/SKILL.md b/.rovodev/skills/animate/SKILL.md deleted file mode 100644 index 89933bfb5..000000000 --- a/.rovodev/skills/animate/SKILL.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.rovodev/skills/audit/SKILL.md b/.rovodev/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.rovodev/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.rovodev/skills/bolder/SKILL.md b/.rovodev/skills/bolder/SKILL.md deleted file mode 100644 index e80f55ed1..000000000 --- a/.rovodev/skills/bolder/SKILL.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too safe or boring: - -1. **Identify weakness sources**: - - **Generic choices**: System fonts, basic colors, standard layouts - - **Timid scale**: Everything is medium-sized with no drama - - **Low contrast**: Everything has similar visual weight - - **Static**: No motion, no energy, no life - - **Predictable**: Standard patterns with no surprises - - **Flat hierarchy**: Nothing stands out or commands attention - -2. **Understand the context**: - - What's the brand personality? (How far can we push?) - - What's the purpose? (Marketing can be bolder than financial dashboards) - - Who's the audience? (What will resonate?) - - What are the constraints? (Brand guidelines, accessibility, performance) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. - -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." - -## Plan Amplification - -Create a strategy to increase impact while maintaining coherence: - -- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) -- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. -- **Risk budget**: How experimental can we be? Push boundaries within constraints. -- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) - -**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. - -## Amplify the Design - -Systematically increase impact across these dimensions: - -### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) -- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) -- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 -- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) - -### Color Intensification -- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) -- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop -- **Dominant color strategy**: Let one bold color own 60% of the design -- **Sharp accents**: High-contrast accent colors that pop -- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette -- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) - -### Spatial Drama -- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings -- **Break the grid**: Let hero elements escape containers and cross boundaries -- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry -- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) -- **Overlap**: Layer elements intentionally for depth - -### Visual Effects -- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) -- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) -- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) -- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) -- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand - -### Motion & Animation -- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays -- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences -- **Micro-interactions**: Satisfying hover effects, click feedback, state changes -- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) - -### Composition Boldness -- **Hero moments**: Create clear focal points with dramatic treatment -- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements -- **Full-bleed elements**: Use full viewport width/height for impact -- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits - -**NEVER**: -- Add effects randomly without purpose (chaos ≠ bold) -- Sacrifice readability for aesthetics (body text must be readable) -- Make everything bold (then nothing is bold - need contrast) -- Ignore accessibility (bold design must still meet WCAG standards) -- Overwhelm with motion (animation fatigue is real) -- Copy trendy aesthetics blindly (bold means distinctive, not derivative) - -## Verify Quality - -Ensure amplification maintains usability and coherence: - -- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. -- **Still functional**: Can users accomplish tasks without distraction? -- **Coherent**: Does everything feel intentional and unified? -- **Memorable**: Will users remember this experience? -- **Performant**: Do all these effects run smoothly? -- **Accessible**: Does it still meet accessibility standards? - -**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." - -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/.rovodev/skills/clarify/SKILL.md b/.rovodev/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.rovodev/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.rovodev/skills/colorize/SKILL.md b/.rovodev/skills/colorize/SKILL.md deleted file mode 100644 index 76075804f..000000000 --- a/.rovodev/skills/colorize/SKILL.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. - ---- - -## Assess Color Opportunity - -Analyze the current state and identify opportunities: - -1. **Understand current state**: - - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? - - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? - - **Context**: What's appropriate for this domain and audience? - - **Brand**: Are there existing brand colors we should use? - -2. **Identify where color adds value**: - - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) - - **Hierarchy**: Drawing attention to important elements - - **Categorization**: Different sections, types, or states - - **Emotional tone**: Warmth, energy, trust, creativity - - **Wayfinding**: Helping users navigate and understand structure - - **Delight**: Moments of visual interest and personality - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. - -## Plan Color Strategy - -Create a purposeful color introduction plan: - -- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) -- **Dominant color**: Which color owns 60% of colored elements? -- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) -- **Application strategy**: Where does each color appear and why? - -**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. - -## Introduce Color Strategically - -Add color systematically across these dimensions: - -### Semantic Color -- **State indicators**: - - Success: Green tones (emerald, forest, mint) - - Error: Red/pink tones (rose, crimson, coral) - - Warning: Orange/amber tones - - Info: Blue tones (sky, ocean, indigo) - - Neutral: Gray/slate for inactive states - -- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) -- **Progress indicators**: Colored bars, rings, or charts showing completion or health - -### Accent Color Application -- **Primary actions**: Color the most important buttons/CTAs -- **Links**: Add color to clickable text (maintain accessibility) -- **Icons**: Colorize key icons for recognition and personality -- **Headers/titles**: Add color to section headers or key labels -- **Hover states**: Introduce color on interaction - -### Background & Surfaces -- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) -- **Colored sections**: Use subtle background colors to separate areas -- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) -- **Cards & surfaces**: Tint cards or surfaces slightly for warmth - -**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. - -### Data Visualization -- **Charts & graphs**: Use color to encode categories or values -- **Heatmaps**: Color intensity shows density or importance -- **Comparison**: Color coding for different datasets or timeframes - -### Borders & Accents -- **Accent borders**: Add colored left/top borders to cards or sections -- **Underlines**: Color underlines for emphasis or active states -- **Dividers**: Subtle colored dividers instead of gray lines -- **Focus rings**: Colored focus indicators matching brand - -### Typography Color -- **Colored headings**: Use brand colors for section headings (maintain contrast) -- **Highlight text**: Color for emphasis or categories -- **Labels & tags**: Small colored labels for metadata or categories - -### Decorative Elements -- **Illustrations**: Add colored illustrations or icons -- **Shapes**: Geometric shapes in brand colors as background elements -- **Gradients**: Colorful gradient overlays or mesh backgrounds -- **Blobs/organic shapes**: Soft colored shapes for visual interest - -## Balance & Refinement - -Ensure color addition improves rather than overwhelms: - -### Maintain Hierarchy -- **Dominant color** (60%): Primary brand color or most used accent -- **Secondary color** (30%): Supporting color for variety -- **Accent color** (10%): High contrast for key moments -- **Neutrals** (remaining): Gray/black/white for structure - -### Accessibility -- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) -- **Don't rely on color alone**: Use icons, labels, or patterns alongside color -- **Test for color blindness**: Verify red/green combinations work for all users - -### Cohesion -- **Consistent palette**: Use colors from defined palette, not arbitrary choices -- **Systematic application**: Same color meanings throughout (green always = success) -- **Temperature consistency**: Warm palette stays warm, cool stays cool - -**NEVER**: -- Use every color in the rainbow (choose 2-4 colors beyond neutrals) -- Apply color randomly without semantic meaning -- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead -- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication -- Use pure black (`#000`) or pure white (`#fff`) for large areas -- Violate WCAG contrast requirements -- Use color as the only indicator (accessibility issue) -- Make everything colorful (defeats the purpose) -- Default to purple-blue gradients (AI slop aesthetic) - -## Verify Color Addition - -Test that colorization improves the experience: - -- **Better hierarchy**: Does color guide attention appropriately? -- **Clearer meaning**: Does color help users understand states/categories? -- **More engaging**: Does the interface feel warmer and more inviting? -- **Still accessible**: Do all color combinations meet WCAG standards? -- **Not overwhelming**: Is color balanced and purposeful? - -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/.rovodev/skills/delight/SKILL.md b/.rovodev/skills/delight/SKILL.md deleted file mode 100644 index fedebff9c..000000000 --- a/.rovodev/skills/delight/SKILL.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.rovodev/skills/distill/SKILL.md b/.rovodev/skills/distill/SKILL.md deleted file mode 100644 index f3f721c99..000000000 --- a/.rovodev/skills/distill/SKILL.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel complex or cluttered: - -1. **Identify complexity sources**: - - **Too many elements**: Competing buttons, redundant information, visual clutter - - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - - **Information overload**: Everything visible at once, no progressive disclosure - - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - - **Confusing hierarchy**: Unclear what matters most - - **Feature creep**: Too many options, actions, or paths forward - -2. **Find the essence**: - - What's the primary user goal? (There should be ONE) - - What's actually necessary vs nice-to-have? - - What can be removed, hidden, or combined? - - What's the 20% that delivers 80% of value? - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. - -## Plan Simplification - -Create a ruthless editing strategy: - -- **Core purpose**: What's the ONE thing this should accomplish? -- **Essential elements**: What's truly necessary to achieve that purpose? -- **Progressive disclosure**: What can be hidden until needed? -- **Consolidation opportunities**: What can be combined or integrated? - -**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. - -## Simplify the Design - -Systematically remove complexity across these dimensions: - -### Information Architecture -- **Reduce scope**: Remove secondary actions, optional features, redundant information -- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) -- **Combine related actions**: Merge similar buttons, consolidate forms, group related content -- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden -- **Remove redundancy**: If it's said elsewhere, don't repeat it here - -### Visual Simplification -- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors -- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights -- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function -- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards -- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead -- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps - -### Layout Simplification -- **Linear flow**: Replace complex grids with simple vertical flow where possible -- **Remove sidebars**: Move secondary content inline or hide it -- **Full-width**: Use available space generously instead of complex multi-column layouts -- **Consistent alignment**: Pick left or center, stick with it -- **Generous white space**: Let content breathe, don't pack everything tight - -### Interaction Simplification -- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) -- **Smart defaults**: Make common choices automatic, only ask when necessary -- **Inline actions**: Replace modal flows with inline editing where possible -- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? -- **Clear CTAs**: ONE obvious next step, not five competing actions - -### Content Simplification -- **Shorter copy**: Cut every sentence in half, then do it again -- **Active voice**: "Save changes" not "Changes will be saved" -- **Remove jargon**: Plain language always wins -- **Scannable structure**: Short paragraphs, bullet points, clear headings -- **Essential information only**: Remove marketing fluff, legalese, hedging -- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once - -### Code Simplification -- **Remove unused code**: Dead CSS, unused components, orphaned files -- **Flatten component trees**: Reduce nesting depth -- **Consolidate styles**: Merge similar styles, use utilities consistently -- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? - -**NEVER**: -- Remove necessary functionality (simplicity ≠ feature-less) -- Sacrifice accessibility for simplicity (clear labels and ARIA still required) -- Make things so simple they're unclear (mystery ≠ minimalism) -- Remove information users need to make decisions -- Eliminate hierarchy completely (some things should stand out) -- Oversimplify complex domains (match complexity to actual task complexity) - -## Verify Simplification - -Ensure simplification improves usability: - -- **Faster task completion**: Can users accomplish goals more quickly? -- **Reduced cognitive load**: Is it easier to understand what to do? -- **Still complete**: Are all necessary features still accessible? -- **Clearer hierarchy**: Is it obvious what matters most? -- **Better performance**: Does simpler design load faster? - -## Document Removed Complexity - -If you removed features or options: -- Document why they were removed -- Consider if they need alternative access points -- Note any user feedback to monitor - -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/.rovodev/skills/harden/SKILL.md b/.rovodev/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.rovodev/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.rovodev/skills/impeccable/SKILL.md b/.rovodev/skills/impeccable/SKILL.md index 6fe09857d..5a380eafa 100644 --- a/.rovodev/skills/impeccable/SKILL.md +++ b/.rovodev/skills/impeccable/SKILL.md @@ -1,16 +1,20 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. +allowed-tools: + - Bash(npx impeccable *) --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +27,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +36,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +272,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +286,96 @@ Remember: Rovo Dev is capable of extraordinary creative work. Don't hold back. S --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .rovodev/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.rovodev/skills/impeccable/reference/adapt.md b/.rovodev/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.rovodev/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.rovodev/skills/impeccable/reference/animate.md b/.rovodev/skills/impeccable/reference/animate.md new file mode 100644 index 000000000..0186ce081 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/animate.md @@ -0,0 +1,166 @@ +> **Additional context needed**: performance constraints. + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + + +--- + +## 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. diff --git a/.rovodev/skills/impeccable/reference/audit.md b/.rovodev/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.rovodev/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.rovodev/skills/impeccable/reference/bolder.md b/.rovodev/skills/impeccable/reference/bolder.md new file mode 100644 index 000000000..cb3481663 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/bolder.md @@ -0,0 +1,106 @@ +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.rovodev/skills/impeccable/reference/clarify.md b/.rovodev/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.rovodev/skills/critique/reference/cognitive-load.md b/.rovodev/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .rovodev/skills/critique/reference/cognitive-load.md rename to .rovodev/skills/impeccable/reference/cognitive-load.md diff --git a/.rovodev/skills/impeccable/reference/colorize.md b/.rovodev/skills/impeccable/reference/colorize.md new file mode 100644 index 000000000..a4ce5072e --- /dev/null +++ b/.rovodev/skills/impeccable/reference/colorize.md @@ -0,0 +1,134 @@ +> **Additional context needed**: existing brand colors. + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.rovodev/skills/impeccable/reference/craft.md b/.rovodev/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.rovodev/skills/impeccable/reference/craft.md +++ b/.rovodev/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.rovodev/skills/critique/SKILL.md b/.rovodev/skills/impeccable/reference/critique.md similarity index 84% rename from .rovodev/skills/critique/SKILL.md rename to .rovodev/skills/impeccable/reference/critique.md index 772383bfa..c282a6c80 100644 --- a/.rovodev/skills/critique/SKILL.md +++ b/.rovodev/skills/impeccable/reference/critique.md @@ -1,20 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" -allowed-tools: - - Bash(npx impeccable *) ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -32,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -46,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -96,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -142,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `AGENTS.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -178,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -198,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -211,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.rovodev/skills/impeccable/reference/delight.md b/.rovodev/skills/impeccable/reference/delight.md new file mode 100644 index 000000000..8a781e70e --- /dev/null +++ b/.rovodev/skills/impeccable/reference/delight.md @@ -0,0 +1,295 @@ +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + + +--- + +## 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. diff --git a/.rovodev/skills/impeccable/reference/distill.md b/.rovodev/skills/impeccable/reference/distill.md new file mode 100644 index 000000000..4f47dc0b4 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/distill.md @@ -0,0 +1,111 @@ +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.rovodev/skills/impeccable/reference/harden.md b/.rovodev/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.rovodev/skills/critique/reference/heuristics-scoring.md b/.rovodev/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .rovodev/skills/critique/reference/heuristics-scoring.md rename to .rovodev/skills/impeccable/reference/heuristics-scoring.md diff --git a/.rovodev/skills/impeccable/reference/layout.md b/.rovodev/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.rovodev/skills/impeccable/reference/optimize.md b/.rovodev/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.rovodev/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.rovodev/skills/impeccable/reference/overdrive.md b/.rovodev/skills/impeccable/reference/overdrive.md new file mode 100644 index 000000000..d84a147dc --- /dev/null +++ b/.rovodev/skills/impeccable/reference/overdrive.md @@ -0,0 +1,130 @@ +Start your response with: + +``` +──────────── ⚡ OVERDRIVE ───────────── +》》》 Entering overdrive mode... +``` + +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. + +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. + +### Propose Before Building + +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: + +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). +3. Only proceed with the direction the user confirms. + +Skipping this step risks building something embarrassing that needs to be thrown away. + +### Iterate with Browser Automation + +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. + +--- + +## Assess What "Extraordinary" Means Here + +The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** + +### For visual/marketing surfaces +Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. + +### For functional UI +Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. + +### For performance-critical UI +The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. + +### For data-heavy interfaces +Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. + +**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. + +## The Toolkit + +Organized by what you're trying to achieve, not by technology name. + +### Make transitions feel cinematic +- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. +- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes +- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. + +### Tie animation to scroll position +- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) + +### Render beyond CSS +- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. +- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. +- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. +- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. + +### Make data feel alive +- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. +- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. +- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. + +### Animate complex properties +- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. +- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. + +### Push performance boundaries +- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. +- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. +- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. + +### Interact with the device +- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. +- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. + +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. + +## Implement with Discipline + +### Progressive enhancement is non-negotiable + +Every technique must degrade gracefully. The experience without the enhancement must still be good. + +```css +@supports (animation-timeline: scroll()) { + .hero { animation-timeline: scroll(); } +} +``` + +```javascript +if ('gpu' in navigator) { /* WebGPU */ } +else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } +/* CSS-only fallback must still look good */ +``` + +### Performance rules + +- Target 60fps. If dropping below 50, simplify. +- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. +- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. +- Pause off-screen rendering. Kill what you can't see. +- Test on real mid-range devices, not just your development machine. + +### Polish is the difference + +The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. + +**NEVER**: +- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion +- Ship effects that cause jank on mid-range devices +- Use bleeding-edge APIs without a functional fallback +- Add sound without explicit user opt-in +- Use technical ambition to mask weak design fundamentals; fix those first with other commands +- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise + +## Verify the Result + +- **The wow test**: Show it to someone who hasn't seen it. Do they react? +- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? +- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? +- **The accessibility test**: Enable reduced motion. Still beautiful? +- **The context test**: Does this make sense for THIS brand and audience? + +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.rovodev/skills/critique/reference/personas.md b/.rovodev/skills/impeccable/reference/personas.md similarity index 100% rename from .rovodev/skills/critique/reference/personas.md rename to .rovodev/skills/impeccable/reference/personas.md diff --git a/.rovodev/skills/impeccable/reference/polish.md b/.rovodev/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.rovodev/skills/impeccable/reference/quieter.md b/.rovodev/skills/impeccable/reference/quieter.md new file mode 100644 index 000000000..a8ad41809 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/quieter.md @@ -0,0 +1,92 @@ +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.rovodev/skills/impeccable/reference/shape.md b/.rovodev/skills/impeccable/reference/shape.md new file mode 100644 index 000000000..0ae281943 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/shape.md @@ -0,0 +1,82 @@ +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. + +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. + +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. + +## Philosophy + +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. + +## Phase 1: Discovery Interview + +**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. + +Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. + +### Purpose & Context +- What is this feature for? What problem does it solve? +- Who specifically will use it? (Not "users"; be specific: role, context, frequency) +- What does success look like? How will you know this feature is working? +- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) + +### Content & Data +- What content or data does this feature display or collect? +- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) +- What are the edge cases? (Empty state, error state, first-time use, power user) +- Is any content dynamic? What changes and how often? + +### Design Goals +- What's the single most important thing a user should do or understand here? +- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) +- Are there existing patterns in the product this should be consistent with? +- Are there specific examples (inside or outside the product) that capture what you're going for? + +### Constraints +- Are there technical constraints? (Framework, performance budget, browser support) +- Are there content constraints? (Localization, dynamic text length, user-generated content) +- Mobile/responsive requirements? +- Accessibility requirements beyond WCAG AA? + +### Anti-Goals +- What should this NOT be? What would be a wrong direction? +- What's the biggest risk of getting this wrong? + +## Phase 2: Design Brief + +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. + +### Brief Structure + +**1. Feature Summary** (2-3 sentences) +What this is, who it's for, what it needs to accomplish. + +**2. Primary User Action** +The single most important thing a user should do or understand here. + +**3. Design Direction** +How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. + +**4. Layout Strategy** +High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. + +**5. Key States** +List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. + +**6. Interaction Model** +How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? + +**7. Content Requirements** +What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. + +**8. Recommended References** +Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). + +**9. Open Questions** +Anything unresolved that the implementer should resolve during build. + +--- + +ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. + +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.rovodev/skills/impeccable/reference/teach.md b/.rovodev/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..2d9f768f1 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to AGENTS.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.rovodev/skills/impeccable/reference/typeset.md b/.rovodev/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.rovodev/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.rovodev/skills/impeccable/scripts/cleanup-deprecated.mjs b/.rovodev/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.rovodev/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.rovodev/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.rovodev/skills/impeccable/scripts/command-metadata.json b/.rovodev/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.rovodev/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.rovodev/skills/impeccable/scripts/pin.mjs b/.rovodev/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.rovodev/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.rovodev/skills/layout/SKILL.md b/.rovodev/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.rovodev/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.rovodev/skills/optimize/SKILL.md b/.rovodev/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.rovodev/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.rovodev/skills/overdrive/SKILL.md b/.rovodev/skills/overdrive/SKILL.md deleted file mode 100644 index 862a4c9c4..000000000 --- a/.rovodev/skills/overdrive/SKILL.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Start your response with: - -``` -──────────── ⚡ OVERDRIVE ───────────── -》》》 Entering overdrive mode... -``` - -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. - -### Propose Before Building - -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: - -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. -2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). -3. Only proceed with the direction the user confirms. - -Skipping this step risks building something embarrassing that needs to be thrown away. - -### Iterate with Browser Automation - -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. - ---- - -## Assess What "Extraordinary" Means Here - -The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** - -### For visual/marketing surfaces -Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. - -### For functional UI -Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. - -### For performance-critical UI -The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. - -### For data-heavy interfaces -Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. - -**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. - -## The Toolkit - -Organized by what you're trying to achieve, not by technology name. - -### Make transitions feel cinematic -- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. -- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes -- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. - -### Tie animation to scroll position -- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) - -### Render beyond CSS -- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. -- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. -- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. -- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. - -### Make data feel alive -- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. -- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. -- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. - -### Animate complex properties -- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. -- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. - -### Push performance boundaries -- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. -- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. -- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. - -### Interact with the device -- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. -- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. - -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. - -## Implement with Discipline - -### Progressive enhancement is non-negotiable - -Every technique must degrade gracefully. The experience without the enhancement must still be good. - -```css -@supports (animation-timeline: scroll()) { - .hero { animation-timeline: scroll(); } -} -``` - -```javascript -if ('gpu' in navigator) { /* WebGPU */ } -else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } -/* CSS-only fallback must still look good */ -``` - -### Performance rules - -- Target 60fps. If dropping below 50, simplify. -- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. -- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. -- Pause off-screen rendering. Kill what you can't see. -- Test on real mid-range devices, not just your development machine. - -### Polish is the difference - -The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. - -**NEVER**: -- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion -- Ship effects that cause jank on mid-range devices -- Use bleeding-edge APIs without a functional fallback -- Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills -- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise - -## Verify the Result - -- **The wow test**: Show it to someone who hasn't seen it. Do they react? -- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? -- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? -- **The accessibility test**: Enable reduced motion. Still beautiful? -- **The context test**: Does this make sense for THIS brand and audience? - -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file diff --git a/.rovodev/skills/polish/SKILL.md b/.rovodev/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.rovodev/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.rovodev/skills/quieter/SKILL.md b/.rovodev/skills/quieter/SKILL.md deleted file mode 100644 index 373ae6869..000000000 --- a/.rovodev/skills/quieter/SKILL.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too intense: - -1. **Identify intensity sources**: - - **Color saturation**: Overly bright or saturated colors - - **Contrast extremes**: Too much high-contrast juxtaposition - - **Visual weight**: Too many bold, heavy elements competing - - **Animation excess**: Too much motion or overly dramatic effects - - **Complexity**: Too many visual elements, patterns, or decorations - - **Scale**: Everything is large and loud with no hierarchy - -2. **Understand the context**: - - What's the purpose? (Marketing vs tool vs reading experience) - - Who's the audience? (Some contexts need energy) - - What's working? (Don't throw away good ideas) - - What's the core message? (Preserve what matters) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. - -## Plan Refinement - -Create a strategy to reduce intensity while maintaining impact: - -- **Color approach**: Desaturate or shift to more sophisticated tones? -- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? -- **Simplification approach**: What can be removed entirely? -- **Sophistication approach**: How can we signal quality through restraint? - -**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. - -## Refine the Design - -Systematically reduce intensity across these dimensions: - -### Color Refinement -- **Reduce saturation**: Shift from fully saturated to 70-85% saturation -- **Soften palette**: Replace bright colors with muted, sophisticated tones -- **Reduce color variety**: Use fewer colors more thoughtfully -- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) -- **Gentler contrasts**: High contrast only where it matters most -- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness -- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead - -### Visual Weight Reduction -- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate -- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness -- **White space**: Increase breathing room, reduce density -- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely - -### Simplification -- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose -- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes -- **Reduce layering**: Flatten visual hierarchy where possible -- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows - -### Motion Reduction -- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing -- **Remove decorative animations**: Keep functional motion, remove flourishes -- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback -- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic -- **Remove animations entirely** if they're not serving a clear purpose - -### Composition Refinement -- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling -- **Align to grid**: Bring rogue elements back into systematic alignment -- **Even out spacing**: Replace extreme spacing variations with consistent rhythm - -**NEVER**: -- Make everything the same size/weight (hierarchy still matters) -- Remove all color (quiet ≠ grayscale) -- Eliminate all personality (maintain character through refinement) -- Sacrifice usability for aesthetics (functional elements still need clear affordances) -- Make everything small and light (some anchors needed) - -## Verify Quality - -Ensure refinement maintains quality: - -- **Still functional**: Can users still accomplish tasks easily? -- **Still distinctive**: Does it have character, or is it generic now? -- **Better reading**: Is text easier to read for extended periods? -- **Sophistication**: Does it feel more refined and premium? - -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/.rovodev/skills/shape/SKILL.md b/.rovodev/skills/shape/SKILL.md deleted file mode 100644 index 7e83008b5..000000000 --- a/.rovodev/skills/shape/SKILL.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. - -## Philosophy - -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. - -## Phase 1: Discovery Interview - -**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. - -Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. - -### Purpose & Context -- What is this feature for? What problem does it solve? -- Who specifically will use it? (Not "users"; be specific: role, context, frequency) -- What does success look like? How will you know this feature is working? -- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) - -### Content & Data -- What content or data does this feature display or collect? -- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) -- What are the edge cases? (Empty state, error state, first-time use, power user) -- Is any content dynamic? What changes and how often? - -### Design Goals -- What's the single most important thing a user should do or understand here? -- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) -- Are there existing patterns in the product this should be consistent with? -- Are there specific examples (inside or outside the product) that capture what you're going for? - -### Constraints -- Are there technical constraints? (Framework, performance budget, browser support) -- Are there content constraints? (Localization, dynamic text length, user-generated content) -- Mobile/responsive requirements? -- Accessibility requirements beyond WCAG AA? - -### Anti-Goals -- What should this NOT be? What would be a wrong direction? -- What's the biggest risk of getting this wrong? - -## Phase 2: Design Brief - -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. - -### Brief Structure - -**1. Feature Summary** (2-3 sentences) -What this is, who it's for, what it needs to accomplish. - -**2. Primary User Action** -The single most important thing a user should do or understand here. - -**3. Design Direction** -How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. - -**4. Layout Strategy** -High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. - -**5. Key States** -List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. - -**6. Interaction Model** -How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? - -**7. Content Requirements** -What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. - -**8. Recommended References** -Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). - -**9. Open Questions** -Anything unresolved that the implementer should resolve during build. - ---- - -ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. - -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file diff --git a/.rovodev/skills/typeset/SKILL.md b/.rovodev/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.rovodev/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.trae-cn/skills/adapt/SKILL.md b/.trae-cn/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.trae-cn/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.trae-cn/skills/animate/SKILL.md b/.trae-cn/skills/animate/SKILL.md deleted file mode 100644 index 89933bfb5..000000000 --- a/.trae-cn/skills/animate/SKILL.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.trae-cn/skills/audit/SKILL.md b/.trae-cn/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.trae-cn/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.trae-cn/skills/bolder/SKILL.md b/.trae-cn/skills/bolder/SKILL.md deleted file mode 100644 index e80f55ed1..000000000 --- a/.trae-cn/skills/bolder/SKILL.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too safe or boring: - -1. **Identify weakness sources**: - - **Generic choices**: System fonts, basic colors, standard layouts - - **Timid scale**: Everything is medium-sized with no drama - - **Low contrast**: Everything has similar visual weight - - **Static**: No motion, no energy, no life - - **Predictable**: Standard patterns with no surprises - - **Flat hierarchy**: Nothing stands out or commands attention - -2. **Understand the context**: - - What's the brand personality? (How far can we push?) - - What's the purpose? (Marketing can be bolder than financial dashboards) - - Who's the audience? (What will resonate?) - - What are the constraints? (Brand guidelines, accessibility, performance) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. - -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." - -## Plan Amplification - -Create a strategy to increase impact while maintaining coherence: - -- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) -- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. -- **Risk budget**: How experimental can we be? Push boundaries within constraints. -- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) - -**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. - -## Amplify the Design - -Systematically increase impact across these dimensions: - -### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) -- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) -- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 -- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) - -### Color Intensification -- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) -- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop -- **Dominant color strategy**: Let one bold color own 60% of the design -- **Sharp accents**: High-contrast accent colors that pop -- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette -- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) - -### Spatial Drama -- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings -- **Break the grid**: Let hero elements escape containers and cross boundaries -- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry -- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) -- **Overlap**: Layer elements intentionally for depth - -### Visual Effects -- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) -- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) -- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) -- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) -- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand - -### Motion & Animation -- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays -- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences -- **Micro-interactions**: Satisfying hover effects, click feedback, state changes -- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) - -### Composition Boldness -- **Hero moments**: Create clear focal points with dramatic treatment -- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements -- **Full-bleed elements**: Use full viewport width/height for impact -- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits - -**NEVER**: -- Add effects randomly without purpose (chaos ≠ bold) -- Sacrifice readability for aesthetics (body text must be readable) -- Make everything bold (then nothing is bold - need contrast) -- Ignore accessibility (bold design must still meet WCAG standards) -- Overwhelm with motion (animation fatigue is real) -- Copy trendy aesthetics blindly (bold means distinctive, not derivative) - -## Verify Quality - -Ensure amplification maintains usability and coherence: - -- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. -- **Still functional**: Can users accomplish tasks without distraction? -- **Coherent**: Does everything feel intentional and unified? -- **Memorable**: Will users remember this experience? -- **Performant**: Do all these effects run smoothly? -- **Accessible**: Does it still meet accessibility standards? - -**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." - -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/.trae-cn/skills/clarify/SKILL.md b/.trae-cn/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.trae-cn/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.trae-cn/skills/colorize/SKILL.md b/.trae-cn/skills/colorize/SKILL.md deleted file mode 100644 index 76075804f..000000000 --- a/.trae-cn/skills/colorize/SKILL.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. - ---- - -## Assess Color Opportunity - -Analyze the current state and identify opportunities: - -1. **Understand current state**: - - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? - - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? - - **Context**: What's appropriate for this domain and audience? - - **Brand**: Are there existing brand colors we should use? - -2. **Identify where color adds value**: - - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) - - **Hierarchy**: Drawing attention to important elements - - **Categorization**: Different sections, types, or states - - **Emotional tone**: Warmth, energy, trust, creativity - - **Wayfinding**: Helping users navigate and understand structure - - **Delight**: Moments of visual interest and personality - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. - -## Plan Color Strategy - -Create a purposeful color introduction plan: - -- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) -- **Dominant color**: Which color owns 60% of colored elements? -- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) -- **Application strategy**: Where does each color appear and why? - -**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. - -## Introduce Color Strategically - -Add color systematically across these dimensions: - -### Semantic Color -- **State indicators**: - - Success: Green tones (emerald, forest, mint) - - Error: Red/pink tones (rose, crimson, coral) - - Warning: Orange/amber tones - - Info: Blue tones (sky, ocean, indigo) - - Neutral: Gray/slate for inactive states - -- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) -- **Progress indicators**: Colored bars, rings, or charts showing completion or health - -### Accent Color Application -- **Primary actions**: Color the most important buttons/CTAs -- **Links**: Add color to clickable text (maintain accessibility) -- **Icons**: Colorize key icons for recognition and personality -- **Headers/titles**: Add color to section headers or key labels -- **Hover states**: Introduce color on interaction - -### Background & Surfaces -- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) -- **Colored sections**: Use subtle background colors to separate areas -- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) -- **Cards & surfaces**: Tint cards or surfaces slightly for warmth - -**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. - -### Data Visualization -- **Charts & graphs**: Use color to encode categories or values -- **Heatmaps**: Color intensity shows density or importance -- **Comparison**: Color coding for different datasets or timeframes - -### Borders & Accents -- **Accent borders**: Add colored left/top borders to cards or sections -- **Underlines**: Color underlines for emphasis or active states -- **Dividers**: Subtle colored dividers instead of gray lines -- **Focus rings**: Colored focus indicators matching brand - -### Typography Color -- **Colored headings**: Use brand colors for section headings (maintain contrast) -- **Highlight text**: Color for emphasis or categories -- **Labels & tags**: Small colored labels for metadata or categories - -### Decorative Elements -- **Illustrations**: Add colored illustrations or icons -- **Shapes**: Geometric shapes in brand colors as background elements -- **Gradients**: Colorful gradient overlays or mesh backgrounds -- **Blobs/organic shapes**: Soft colored shapes for visual interest - -## Balance & Refinement - -Ensure color addition improves rather than overwhelms: - -### Maintain Hierarchy -- **Dominant color** (60%): Primary brand color or most used accent -- **Secondary color** (30%): Supporting color for variety -- **Accent color** (10%): High contrast for key moments -- **Neutrals** (remaining): Gray/black/white for structure - -### Accessibility -- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) -- **Don't rely on color alone**: Use icons, labels, or patterns alongside color -- **Test for color blindness**: Verify red/green combinations work for all users - -### Cohesion -- **Consistent palette**: Use colors from defined palette, not arbitrary choices -- **Systematic application**: Same color meanings throughout (green always = success) -- **Temperature consistency**: Warm palette stays warm, cool stays cool - -**NEVER**: -- Use every color in the rainbow (choose 2-4 colors beyond neutrals) -- Apply color randomly without semantic meaning -- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead -- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication -- Use pure black (`#000`) or pure white (`#fff`) for large areas -- Violate WCAG contrast requirements -- Use color as the only indicator (accessibility issue) -- Make everything colorful (defeats the purpose) -- Default to purple-blue gradients (AI slop aesthetic) - -## Verify Color Addition - -Test that colorization improves the experience: - -- **Better hierarchy**: Does color guide attention appropriately? -- **Clearer meaning**: Does color help users understand states/categories? -- **More engaging**: Does the interface feel warmer and more inviting? -- **Still accessible**: Do all color combinations meet WCAG standards? -- **Not overwhelming**: Is color balanced and purposeful? - -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/.trae-cn/skills/delight/SKILL.md b/.trae-cn/skills/delight/SKILL.md deleted file mode 100644 index fedebff9c..000000000 --- a/.trae-cn/skills/delight/SKILL.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.trae-cn/skills/distill/SKILL.md b/.trae-cn/skills/distill/SKILL.md deleted file mode 100644 index f3f721c99..000000000 --- a/.trae-cn/skills/distill/SKILL.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel complex or cluttered: - -1. **Identify complexity sources**: - - **Too many elements**: Competing buttons, redundant information, visual clutter - - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - - **Information overload**: Everything visible at once, no progressive disclosure - - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - - **Confusing hierarchy**: Unclear what matters most - - **Feature creep**: Too many options, actions, or paths forward - -2. **Find the essence**: - - What's the primary user goal? (There should be ONE) - - What's actually necessary vs nice-to-have? - - What can be removed, hidden, or combined? - - What's the 20% that delivers 80% of value? - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. - -## Plan Simplification - -Create a ruthless editing strategy: - -- **Core purpose**: What's the ONE thing this should accomplish? -- **Essential elements**: What's truly necessary to achieve that purpose? -- **Progressive disclosure**: What can be hidden until needed? -- **Consolidation opportunities**: What can be combined or integrated? - -**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. - -## Simplify the Design - -Systematically remove complexity across these dimensions: - -### Information Architecture -- **Reduce scope**: Remove secondary actions, optional features, redundant information -- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) -- **Combine related actions**: Merge similar buttons, consolidate forms, group related content -- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden -- **Remove redundancy**: If it's said elsewhere, don't repeat it here - -### Visual Simplification -- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors -- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights -- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function -- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards -- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead -- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps - -### Layout Simplification -- **Linear flow**: Replace complex grids with simple vertical flow where possible -- **Remove sidebars**: Move secondary content inline or hide it -- **Full-width**: Use available space generously instead of complex multi-column layouts -- **Consistent alignment**: Pick left or center, stick with it -- **Generous white space**: Let content breathe, don't pack everything tight - -### Interaction Simplification -- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) -- **Smart defaults**: Make common choices automatic, only ask when necessary -- **Inline actions**: Replace modal flows with inline editing where possible -- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? -- **Clear CTAs**: ONE obvious next step, not five competing actions - -### Content Simplification -- **Shorter copy**: Cut every sentence in half, then do it again -- **Active voice**: "Save changes" not "Changes will be saved" -- **Remove jargon**: Plain language always wins -- **Scannable structure**: Short paragraphs, bullet points, clear headings -- **Essential information only**: Remove marketing fluff, legalese, hedging -- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once - -### Code Simplification -- **Remove unused code**: Dead CSS, unused components, orphaned files -- **Flatten component trees**: Reduce nesting depth -- **Consolidate styles**: Merge similar styles, use utilities consistently -- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? - -**NEVER**: -- Remove necessary functionality (simplicity ≠ feature-less) -- Sacrifice accessibility for simplicity (clear labels and ARIA still required) -- Make things so simple they're unclear (mystery ≠ minimalism) -- Remove information users need to make decisions -- Eliminate hierarchy completely (some things should stand out) -- Oversimplify complex domains (match complexity to actual task complexity) - -## Verify Simplification - -Ensure simplification improves usability: - -- **Faster task completion**: Can users accomplish goals more quickly? -- **Reduced cognitive load**: Is it easier to understand what to do? -- **Still complete**: Are all necessary features still accessible? -- **Clearer hierarchy**: Is it obvious what matters most? -- **Better performance**: Does simpler design load faster? - -## Document Removed Complexity - -If you removed features or options: -- Document why they were removed -- Consider if they need alternative access points -- Note any user feedback to monitor - -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/.trae-cn/skills/harden/SKILL.md b/.trae-cn/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.trae-cn/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.trae-cn/skills/impeccable/SKILL.md b/.trae-cn/skills/impeccable/SKILL.md index ad24d7747..5ef54ec67 100644 --- a/.trae-cn/skills/impeccable/SKILL.md +++ b/.trae-cn/skills/impeccable/SKILL.md @@ -1,16 +1,18 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +25,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +34,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +270,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +284,96 @@ Remember: the model is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .trae-cn/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to RULES.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.trae-cn/skills/impeccable/reference/adapt.md b/.trae-cn/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.trae-cn/skills/impeccable/reference/animate.md b/.trae-cn/skills/impeccable/reference/animate.md new file mode 100644 index 000000000..0186ce081 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/animate.md @@ -0,0 +1,166 @@ +> **Additional context needed**: performance constraints. + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + + +--- + +## 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. diff --git a/.trae-cn/skills/impeccable/reference/audit.md b/.trae-cn/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.trae-cn/skills/impeccable/reference/bolder.md b/.trae-cn/skills/impeccable/reference/bolder.md new file mode 100644 index 000000000..cb3481663 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/bolder.md @@ -0,0 +1,106 @@ +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.trae-cn/skills/impeccable/reference/clarify.md b/.trae-cn/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.trae-cn/skills/critique/reference/cognitive-load.md b/.trae-cn/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .trae-cn/skills/critique/reference/cognitive-load.md rename to .trae-cn/skills/impeccable/reference/cognitive-load.md diff --git a/.trae-cn/skills/impeccable/reference/colorize.md b/.trae-cn/skills/impeccable/reference/colorize.md new file mode 100644 index 000000000..a4ce5072e --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/colorize.md @@ -0,0 +1,134 @@ +> **Additional context needed**: existing brand colors. + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.trae-cn/skills/impeccable/reference/craft.md b/.trae-cn/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.trae-cn/skills/impeccable/reference/craft.md +++ b/.trae-cn/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.trae/skills/critique/SKILL.md b/.trae-cn/skills/impeccable/reference/critique.md similarity index 84% rename from .trae/skills/critique/SKILL.md rename to .trae-cn/skills/impeccable/reference/critique.md index e89e7b281..8866153fc 100644 --- a/.trae/skills/critique/SKILL.md +++ b/.trae-cn/skills/impeccable/reference/critique.md @@ -1,18 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -30,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -44,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -94,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -140,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `RULES.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -176,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -196,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -209,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.trae-cn/skills/impeccable/reference/delight.md b/.trae-cn/skills/impeccable/reference/delight.md new file mode 100644 index 000000000..8a781e70e --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/delight.md @@ -0,0 +1,295 @@ +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + + +--- + +## 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. diff --git a/.trae-cn/skills/impeccable/reference/distill.md b/.trae-cn/skills/impeccable/reference/distill.md new file mode 100644 index 000000000..4f47dc0b4 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/distill.md @@ -0,0 +1,111 @@ +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.trae-cn/skills/impeccable/reference/harden.md b/.trae-cn/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.trae-cn/skills/critique/reference/heuristics-scoring.md b/.trae-cn/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .trae-cn/skills/critique/reference/heuristics-scoring.md rename to .trae-cn/skills/impeccable/reference/heuristics-scoring.md diff --git a/.trae-cn/skills/impeccable/reference/layout.md b/.trae-cn/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.trae-cn/skills/impeccable/reference/optimize.md b/.trae-cn/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.trae-cn/skills/impeccable/reference/overdrive.md b/.trae-cn/skills/impeccable/reference/overdrive.md new file mode 100644 index 000000000..d84a147dc --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/overdrive.md @@ -0,0 +1,130 @@ +Start your response with: + +``` +──────────── ⚡ OVERDRIVE ───────────── +》》》 Entering overdrive mode... +``` + +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. + +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. + +### Propose Before Building + +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: + +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). +3. Only proceed with the direction the user confirms. + +Skipping this step risks building something embarrassing that needs to be thrown away. + +### Iterate with Browser Automation + +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. + +--- + +## Assess What "Extraordinary" Means Here + +The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** + +### For visual/marketing surfaces +Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. + +### For functional UI +Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. + +### For performance-critical UI +The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. + +### For data-heavy interfaces +Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. + +**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. + +## The Toolkit + +Organized by what you're trying to achieve, not by technology name. + +### Make transitions feel cinematic +- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. +- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes +- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. + +### Tie animation to scroll position +- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) + +### Render beyond CSS +- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. +- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. +- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. +- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. + +### Make data feel alive +- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. +- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. +- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. + +### Animate complex properties +- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. +- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. + +### Push performance boundaries +- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. +- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. +- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. + +### Interact with the device +- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. +- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. + +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. + +## Implement with Discipline + +### Progressive enhancement is non-negotiable + +Every technique must degrade gracefully. The experience without the enhancement must still be good. + +```css +@supports (animation-timeline: scroll()) { + .hero { animation-timeline: scroll(); } +} +``` + +```javascript +if ('gpu' in navigator) { /* WebGPU */ } +else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } +/* CSS-only fallback must still look good */ +``` + +### Performance rules + +- Target 60fps. If dropping below 50, simplify. +- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. +- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. +- Pause off-screen rendering. Kill what you can't see. +- Test on real mid-range devices, not just your development machine. + +### Polish is the difference + +The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. + +**NEVER**: +- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion +- Ship effects that cause jank on mid-range devices +- Use bleeding-edge APIs without a functional fallback +- Add sound without explicit user opt-in +- Use technical ambition to mask weak design fundamentals; fix those first with other commands +- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise + +## Verify the Result + +- **The wow test**: Show it to someone who hasn't seen it. Do they react? +- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? +- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? +- **The accessibility test**: Enable reduced motion. Still beautiful? +- **The context test**: Does this make sense for THIS brand and audience? + +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.trae-cn/skills/critique/reference/personas.md b/.trae-cn/skills/impeccable/reference/personas.md similarity index 100% rename from .trae-cn/skills/critique/reference/personas.md rename to .trae-cn/skills/impeccable/reference/personas.md diff --git a/.trae-cn/skills/impeccable/reference/polish.md b/.trae-cn/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.trae-cn/skills/impeccable/reference/quieter.md b/.trae-cn/skills/impeccable/reference/quieter.md new file mode 100644 index 000000000..a8ad41809 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/quieter.md @@ -0,0 +1,92 @@ +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.trae-cn/skills/impeccable/reference/shape.md b/.trae-cn/skills/impeccable/reference/shape.md new file mode 100644 index 000000000..0ae281943 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/shape.md @@ -0,0 +1,82 @@ +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. + +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. + +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. + +## Philosophy + +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. + +## Phase 1: Discovery Interview + +**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. + +Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. + +### Purpose & Context +- What is this feature for? What problem does it solve? +- Who specifically will use it? (Not "users"; be specific: role, context, frequency) +- What does success look like? How will you know this feature is working? +- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) + +### Content & Data +- What content or data does this feature display or collect? +- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) +- What are the edge cases? (Empty state, error state, first-time use, power user) +- Is any content dynamic? What changes and how often? + +### Design Goals +- What's the single most important thing a user should do or understand here? +- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) +- Are there existing patterns in the product this should be consistent with? +- Are there specific examples (inside or outside the product) that capture what you're going for? + +### Constraints +- Are there technical constraints? (Framework, performance budget, browser support) +- Are there content constraints? (Localization, dynamic text length, user-generated content) +- Mobile/responsive requirements? +- Accessibility requirements beyond WCAG AA? + +### Anti-Goals +- What should this NOT be? What would be a wrong direction? +- What's the biggest risk of getting this wrong? + +## Phase 2: Design Brief + +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. + +### Brief Structure + +**1. Feature Summary** (2-3 sentences) +What this is, who it's for, what it needs to accomplish. + +**2. Primary User Action** +The single most important thing a user should do or understand here. + +**3. Design Direction** +How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. + +**4. Layout Strategy** +High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. + +**5. Key States** +List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. + +**6. Interaction Model** +How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? + +**7. Content Requirements** +What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. + +**8. Recommended References** +Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). + +**9. Open Questions** +Anything unresolved that the implementer should resolve during build. + +--- + +ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. + +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.trae-cn/skills/impeccable/reference/teach.md b/.trae-cn/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..972ca25be --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to RULES.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.trae-cn/skills/impeccable/reference/typeset.md b/.trae-cn/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.trae-cn/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.trae-cn/skills/impeccable/scripts/cleanup-deprecated.mjs b/.trae-cn/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.trae-cn/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.trae-cn/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.trae-cn/skills/impeccable/scripts/command-metadata.json b/.trae-cn/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.trae-cn/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.trae-cn/skills/impeccable/scripts/pin.mjs b/.trae-cn/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.trae-cn/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.trae-cn/skills/layout/SKILL.md b/.trae-cn/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.trae-cn/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.trae-cn/skills/optimize/SKILL.md b/.trae-cn/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.trae-cn/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.trae-cn/skills/overdrive/SKILL.md b/.trae-cn/skills/overdrive/SKILL.md deleted file mode 100644 index 862a4c9c4..000000000 --- a/.trae-cn/skills/overdrive/SKILL.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Start your response with: - -``` -──────────── ⚡ OVERDRIVE ───────────── -》》》 Entering overdrive mode... -``` - -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. - -### Propose Before Building - -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: - -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. -2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). -3. Only proceed with the direction the user confirms. - -Skipping this step risks building something embarrassing that needs to be thrown away. - -### Iterate with Browser Automation - -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. - ---- - -## Assess What "Extraordinary" Means Here - -The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** - -### For visual/marketing surfaces -Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. - -### For functional UI -Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. - -### For performance-critical UI -The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. - -### For data-heavy interfaces -Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. - -**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. - -## The Toolkit - -Organized by what you're trying to achieve, not by technology name. - -### Make transitions feel cinematic -- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. -- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes -- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. - -### Tie animation to scroll position -- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) - -### Render beyond CSS -- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. -- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. -- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. -- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. - -### Make data feel alive -- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. -- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. -- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. - -### Animate complex properties -- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. -- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. - -### Push performance boundaries -- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. -- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. -- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. - -### Interact with the device -- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. -- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. - -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. - -## Implement with Discipline - -### Progressive enhancement is non-negotiable - -Every technique must degrade gracefully. The experience without the enhancement must still be good. - -```css -@supports (animation-timeline: scroll()) { - .hero { animation-timeline: scroll(); } -} -``` - -```javascript -if ('gpu' in navigator) { /* WebGPU */ } -else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } -/* CSS-only fallback must still look good */ -``` - -### Performance rules - -- Target 60fps. If dropping below 50, simplify. -- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. -- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. -- Pause off-screen rendering. Kill what you can't see. -- Test on real mid-range devices, not just your development machine. - -### Polish is the difference - -The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. - -**NEVER**: -- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion -- Ship effects that cause jank on mid-range devices -- Use bleeding-edge APIs without a functional fallback -- Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills -- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise - -## Verify the Result - -- **The wow test**: Show it to someone who hasn't seen it. Do they react? -- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? -- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? -- **The accessibility test**: Enable reduced motion. Still beautiful? -- **The context test**: Does this make sense for THIS brand and audience? - -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file diff --git a/.trae-cn/skills/polish/SKILL.md b/.trae-cn/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.trae-cn/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.trae-cn/skills/quieter/SKILL.md b/.trae-cn/skills/quieter/SKILL.md deleted file mode 100644 index 373ae6869..000000000 --- a/.trae-cn/skills/quieter/SKILL.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too intense: - -1. **Identify intensity sources**: - - **Color saturation**: Overly bright or saturated colors - - **Contrast extremes**: Too much high-contrast juxtaposition - - **Visual weight**: Too many bold, heavy elements competing - - **Animation excess**: Too much motion or overly dramatic effects - - **Complexity**: Too many visual elements, patterns, or decorations - - **Scale**: Everything is large and loud with no hierarchy - -2. **Understand the context**: - - What's the purpose? (Marketing vs tool vs reading experience) - - Who's the audience? (Some contexts need energy) - - What's working? (Don't throw away good ideas) - - What's the core message? (Preserve what matters) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. - -## Plan Refinement - -Create a strategy to reduce intensity while maintaining impact: - -- **Color approach**: Desaturate or shift to more sophisticated tones? -- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? -- **Simplification approach**: What can be removed entirely? -- **Sophistication approach**: How can we signal quality through restraint? - -**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. - -## Refine the Design - -Systematically reduce intensity across these dimensions: - -### Color Refinement -- **Reduce saturation**: Shift from fully saturated to 70-85% saturation -- **Soften palette**: Replace bright colors with muted, sophisticated tones -- **Reduce color variety**: Use fewer colors more thoughtfully -- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) -- **Gentler contrasts**: High contrast only where it matters most -- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness -- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead - -### Visual Weight Reduction -- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate -- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness -- **White space**: Increase breathing room, reduce density -- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely - -### Simplification -- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose -- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes -- **Reduce layering**: Flatten visual hierarchy where possible -- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows - -### Motion Reduction -- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing -- **Remove decorative animations**: Keep functional motion, remove flourishes -- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback -- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic -- **Remove animations entirely** if they're not serving a clear purpose - -### Composition Refinement -- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling -- **Align to grid**: Bring rogue elements back into systematic alignment -- **Even out spacing**: Replace extreme spacing variations with consistent rhythm - -**NEVER**: -- Make everything the same size/weight (hierarchy still matters) -- Remove all color (quiet ≠ grayscale) -- Eliminate all personality (maintain character through refinement) -- Sacrifice usability for aesthetics (functional elements still need clear affordances) -- Make everything small and light (some anchors needed) - -## Verify Quality - -Ensure refinement maintains quality: - -- **Still functional**: Can users still accomplish tasks easily? -- **Still distinctive**: Does it have character, or is it generic now? -- **Better reading**: Is text easier to read for extended periods? -- **Sophistication**: Does it feel more refined and premium? - -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/.trae-cn/skills/shape/SKILL.md b/.trae-cn/skills/shape/SKILL.md deleted file mode 100644 index 7e83008b5..000000000 --- a/.trae-cn/skills/shape/SKILL.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. - -## Philosophy - -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. - -## Phase 1: Discovery Interview - -**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. - -Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. - -### Purpose & Context -- What is this feature for? What problem does it solve? -- Who specifically will use it? (Not "users"; be specific: role, context, frequency) -- What does success look like? How will you know this feature is working? -- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) - -### Content & Data -- What content or data does this feature display or collect? -- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) -- What are the edge cases? (Empty state, error state, first-time use, power user) -- Is any content dynamic? What changes and how often? - -### Design Goals -- What's the single most important thing a user should do or understand here? -- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) -- Are there existing patterns in the product this should be consistent with? -- Are there specific examples (inside or outside the product) that capture what you're going for? - -### Constraints -- Are there technical constraints? (Framework, performance budget, browser support) -- Are there content constraints? (Localization, dynamic text length, user-generated content) -- Mobile/responsive requirements? -- Accessibility requirements beyond WCAG AA? - -### Anti-Goals -- What should this NOT be? What would be a wrong direction? -- What's the biggest risk of getting this wrong? - -## Phase 2: Design Brief - -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. - -### Brief Structure - -**1. Feature Summary** (2-3 sentences) -What this is, who it's for, what it needs to accomplish. - -**2. Primary User Action** -The single most important thing a user should do or understand here. - -**3. Design Direction** -How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. - -**4. Layout Strategy** -High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. - -**5. Key States** -List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. - -**6. Interaction Model** -How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? - -**7. Content Requirements** -What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. - -**8. Recommended References** -Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). - -**9. Open Questions** -Anything unresolved that the implementer should resolve during build. - ---- - -ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. - -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file diff --git a/.trae-cn/skills/typeset/SKILL.md b/.trae-cn/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.trae-cn/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/.trae/skills/adapt/SKILL.md b/.trae/skills/adapt/SKILL.md deleted file mode 100644 index 21a424162..000000000 --- a/.trae/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility. -version: 2.1.1 -user-invocable: true -argument-hint: "[target] [context (mobile, tablet, print...)]" ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/.trae/skills/animate/SKILL.md b/.trae/skills/animate/SKILL.md deleted file mode 100644 index 89933bfb5..000000000 --- a/.trae/skills/animate/SKILL.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.trae/skills/audit/SKILL.md b/.trae/skills/audit/SKILL.md deleted file mode 100644 index ea30301c1..000000000 --- a/.trae/skills/audit/SKILL.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -name: audit -description: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. - -This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. - -## Diagnostic Scan - -Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. - -### 1. Accessibility (A11y) - -**Check for**: -- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) -- **Missing ARIA**: Interactive elements without proper roles, labels, or states -- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps -- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons -- **Alt text**: Missing or poor image descriptions -- **Form issues**: Inputs without labels, poor error messaging, missing required indicators - -**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) - -### 2. Performance - -**Check for**: -- **Layout thrashing**: Reading/writing layout properties in loops -- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity -- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change -- **Bundle size**: Unnecessary imports, unused dependencies -- **Render performance**: Unnecessary re-renders, missing memoization - -**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) - -### 3. Theming - -**Check for**: -- **Hard-coded colors**: Colors not using design tokens -- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme -- **Inconsistent tokens**: Using wrong tokens, mixing token types -- **Theme switching issues**: Values that don't update on theme change - -**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) - -### 4. Responsive Design - -**Check for**: -- **Fixed widths**: Hard-coded widths that break on mobile -- **Touch targets**: Interactive elements < 44x44px -- **Horizontal scroll**: Content overflow on narrow viewports -- **Text scaling**: Layouts that break when text size increases -- **Missing breakpoints**: No mobile/tablet variants - -**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) - -### 5. Anti-Patterns (CRITICAL) - -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). - -**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) - -## Generate Report - -### Audit Health Score - -| # | Dimension | Score | Key Finding | -|---|-----------|-------|-------------| -| 1 | Accessibility | ? | [most critical a11y issue or "--"] | -| 2 | Performance | ? | | -| 3 | Responsive Design | ? | | -| 4 | Theming | ? | | -| 5 | Anti-Patterns | ? | | -| **Total** | | **??/20** | **[Rating band]** | - -**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) - -### Anti-Patterns Verdict -**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. - -### Executive Summary -- Audit Health Score: **??/20** ([rating band]) -- Total issues found (count by severity: P0/P1/P2/P3) -- Top 3-5 critical issues -- Recommended next steps - -### Detailed Findings by Severity - -Tag every issue with **P0-P3 severity**: -- **P0 Blocking**: Prevents task completion — fix immediately -- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release -- **P2 Minor**: Annoyance, workaround exists — fix in next pass -- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits - -For each issue, document: -- **[P?] Issue name** -- **Location**: Component, file, line -- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern -- **Impact**: How it affects users -- **WCAG/Standard**: Which standard it violates (if applicable) -- **Recommendation**: How to fix it -- **Suggested command**: Which command to use (prefer: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) - -### Patterns & Systemic Issues - -Identify recurring problems that indicate systemic gaps rather than one-off mistakes: -- "Hard-coded colors appear in 15+ components, should use design tokens" -- "Touch targets consistently too small (<44px) throughout mobile experience" - -### Positive Findings - -Note what's working well — good practices to maintain and replicate. - -## Recommended Actions - -List recommended commands in priority order (P0 first, then P1, then P2): - -1. **[P?] `/command-name`** — Brief description (specific context from audit findings) -2. **[P?] `/command-name`** — Brief description (specific context) - -**Rules**: Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive. Map findings to the most appropriate command. End with `/polish` as the final step if any fixes were recommended. - -After presenting the summary, tell the user: - -> You can ask me to run these one at a time, all at once, or in any order you prefer. -> -> Re-run `/audit` after fixes to see your score improve. - -**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. - -**NEVER**: -- Report issues without explaining impact (why does this matter?) -- Provide generic recommendations (be specific and actionable) -- Skip positive findings (celebrate what works) -- Forget to prioritize (everything can't be P0) -- Report false positives without verification - -Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. \ No newline at end of file diff --git a/.trae/skills/bolder/SKILL.md b/.trae/skills/bolder/SKILL.md deleted file mode 100644 index e80f55ed1..000000000 --- a/.trae/skills/bolder/SKILL.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -name: bolder -description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too safe or boring: - -1. **Identify weakness sources**: - - **Generic choices**: System fonts, basic colors, standard layouts - - **Timid scale**: Everything is medium-sized with no drama - - **Low contrast**: Everything has similar visual weight - - **Static**: No motion, no energy, no life - - **Predictable**: Standard patterns with no surprises - - **Flat hierarchy**: Nothing stands out or commands attention - -2. **Understand the context**: - - What's the brand personality? (How far can we push?) - - What's the purpose? (Marketing can be bolder than financial dashboards) - - Who's the audience? (What will resonate?) - - What are the constraints? (Brand guidelines, accessibility, performance) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. - -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." - -## Plan Amplification - -Create a strategy to increase impact while maintaining coherence: - -- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) -- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. -- **Risk budget**: How experimental can we be? Push boundaries within constraints. -- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) - -**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. - -## Amplify the Design - -Systematically increase impact across these dimensions: - -### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) -- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) -- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 -- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) - -### Color Intensification -- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) -- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop -- **Dominant color strategy**: Let one bold color own 60% of the design -- **Sharp accents**: High-contrast accent colors that pop -- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette -- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) - -### Spatial Drama -- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings -- **Break the grid**: Let hero elements escape containers and cross boundaries -- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry -- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) -- **Overlap**: Layer elements intentionally for depth - -### Visual Effects -- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) -- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) -- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) -- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) -- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand - -### Motion & Animation -- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays -- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences -- **Micro-interactions**: Satisfying hover effects, click feedback, state changes -- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) - -### Composition Boldness -- **Hero moments**: Create clear focal points with dramatic treatment -- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements -- **Full-bleed elements**: Use full viewport width/height for impact -- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits - -**NEVER**: -- Add effects randomly without purpose (chaos ≠ bold) -- Sacrifice readability for aesthetics (body text must be readable) -- Make everything bold (then nothing is bold - need contrast) -- Ignore accessibility (bold design must still meet WCAG standards) -- Overwhelm with motion (animation fatigue is real) -- Copy trendy aesthetics blindly (bold means distinctive, not derivative) - -## Verify Quality - -Ensure amplification maintains usability and coherence: - -- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. -- **Still functional**: Can users accomplish tasks without distraction? -- **Coherent**: Does everything feel intentional and unified? -- **Memorable**: Will users remember this experience? -- **Performant**: Do all these effects run smoothly? -- **Accessible**: Does it still meet accessibility standards? - -**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." - -Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/.trae/skills/clarify/SKILL.md b/.trae/skills/clarify/SKILL.md deleted file mode 100644 index f0013b2cf..000000000 --- a/.trae/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/.trae/skills/colorize/SKILL.md b/.trae/skills/colorize/SKILL.md deleted file mode 100644 index 76075804f..000000000 --- a/.trae/skills/colorize/SKILL.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -name: colorize -description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. Additionally gather: existing brand colors. - ---- - -## Assess Color Opportunity - -Analyze the current state and identify opportunities: - -1. **Understand current state**: - - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? - - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? - - **Context**: What's appropriate for this domain and audience? - - **Brand**: Are there existing brand colors we should use? - -2. **Identify where color adds value**: - - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) - - **Hierarchy**: Drawing attention to important elements - - **Categorization**: Different sections, types, or states - - **Emotional tone**: Warmth, energy, trust, creativity - - **Wayfinding**: Helping users navigate and understand structure - - **Delight**: Moments of visual interest and personality - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. - -## Plan Color Strategy - -Create a purposeful color introduction plan: - -- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) -- **Dominant color**: Which color owns 60% of colored elements? -- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) -- **Application strategy**: Where does each color appear and why? - -**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. - -## Introduce Color Strategically - -Add color systematically across these dimensions: - -### Semantic Color -- **State indicators**: - - Success: Green tones (emerald, forest, mint) - - Error: Red/pink tones (rose, crimson, coral) - - Warning: Orange/amber tones - - Info: Blue tones (sky, ocean, indigo) - - Neutral: Gray/slate for inactive states - -- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) -- **Progress indicators**: Colored bars, rings, or charts showing completion or health - -### Accent Color Application -- **Primary actions**: Color the most important buttons/CTAs -- **Links**: Add color to clickable text (maintain accessibility) -- **Icons**: Colorize key icons for recognition and personality -- **Headers/titles**: Add color to section headers or key labels -- **Hover states**: Introduce color on interaction - -### Background & Surfaces -- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) -- **Colored sections**: Use subtle background colors to separate areas -- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) -- **Cards & surfaces**: Tint cards or surfaces slightly for warmth - -**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. - -### Data Visualization -- **Charts & graphs**: Use color to encode categories or values -- **Heatmaps**: Color intensity shows density or importance -- **Comparison**: Color coding for different datasets or timeframes - -### Borders & Accents -- **Accent borders**: Add colored left/top borders to cards or sections -- **Underlines**: Color underlines for emphasis or active states -- **Dividers**: Subtle colored dividers instead of gray lines -- **Focus rings**: Colored focus indicators matching brand - -### Typography Color -- **Colored headings**: Use brand colors for section headings (maintain contrast) -- **Highlight text**: Color for emphasis or categories -- **Labels & tags**: Small colored labels for metadata or categories - -### Decorative Elements -- **Illustrations**: Add colored illustrations or icons -- **Shapes**: Geometric shapes in brand colors as background elements -- **Gradients**: Colorful gradient overlays or mesh backgrounds -- **Blobs/organic shapes**: Soft colored shapes for visual interest - -## Balance & Refinement - -Ensure color addition improves rather than overwhelms: - -### Maintain Hierarchy -- **Dominant color** (60%): Primary brand color or most used accent -- **Secondary color** (30%): Supporting color for variety -- **Accent color** (10%): High contrast for key moments -- **Neutrals** (remaining): Gray/black/white for structure - -### Accessibility -- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) -- **Don't rely on color alone**: Use icons, labels, or patterns alongside color -- **Test for color blindness**: Verify red/green combinations work for all users - -### Cohesion -- **Consistent palette**: Use colors from defined palette, not arbitrary choices -- **Systematic application**: Same color meanings throughout (green always = success) -- **Temperature consistency**: Warm palette stays warm, cool stays cool - -**NEVER**: -- Use every color in the rainbow (choose 2-4 colors beyond neutrals) -- Apply color randomly without semantic meaning -- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead -- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication -- Use pure black (`#000`) or pure white (`#fff`) for large areas -- Violate WCAG contrast requirements -- Use color as the only indicator (accessibility issue) -- Make everything colorful (defeats the purpose) -- Default to purple-blue gradients (AI slop aesthetic) - -## Verify Color Addition - -Test that colorization improves the experience: - -- **Better hierarchy**: Does color guide attention appropriately? -- **Clearer meaning**: Does color help users understand states/categories? -- **More engaging**: Does the interface feel warmer and more inviting? -- **Still accessible**: Do all color combinations meet WCAG standards? -- **Not overwhelming**: Is color balanced and purposeful? - -Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/.trae/skills/delight/SKILL.md b/.trae/skills/delight/SKILL.md deleted file mode 100644 index fedebff9c..000000000 --- a/.trae/skills/delight/SKILL.md +++ /dev/null @@ -1,304 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. \ No newline at end of file diff --git a/.trae/skills/distill/SKILL.md b/.trae/skills/distill/SKILL.md deleted file mode 100644 index f3f721c99..000000000 --- a/.trae/skills/distill/SKILL.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -name: distill -description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel complex or cluttered: - -1. **Identify complexity sources**: - - **Too many elements**: Competing buttons, redundant information, visual clutter - - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose - - **Information overload**: Everything visible at once, no progressive disclosure - - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations - - **Confusing hierarchy**: Unclear what matters most - - **Feature creep**: Too many options, actions, or paths forward - -2. **Find the essence**: - - What's the primary user goal? (There should be ONE) - - What's actually necessary vs nice-to-have? - - What can be removed, hidden, or combined? - - What's the 20% that delivers 80% of value? - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. - -## Plan Simplification - -Create a ruthless editing strategy: - -- **Core purpose**: What's the ONE thing this should accomplish? -- **Essential elements**: What's truly necessary to achieve that purpose? -- **Progressive disclosure**: What can be hidden until needed? -- **Consolidation opportunities**: What can be combined or integrated? - -**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. - -## Simplify the Design - -Systematically remove complexity across these dimensions: - -### Information Architecture -- **Reduce scope**: Remove secondary actions, optional features, redundant information -- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) -- **Combine related actions**: Merge similar buttons, consolidate forms, group related content -- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden -- **Remove redundancy**: If it's said elsewhere, don't repeat it here - -### Visual Simplification -- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors -- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights -- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function -- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards -- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead -- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps - -### Layout Simplification -- **Linear flow**: Replace complex grids with simple vertical flow where possible -- **Remove sidebars**: Move secondary content inline or hide it -- **Full-width**: Use available space generously instead of complex multi-column layouts -- **Consistent alignment**: Pick left or center, stick with it -- **Generous white space**: Let content breathe, don't pack everything tight - -### Interaction Simplification -- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) -- **Smart defaults**: Make common choices automatic, only ask when necessary -- **Inline actions**: Replace modal flows with inline editing where possible -- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? -- **Clear CTAs**: ONE obvious next step, not five competing actions - -### Content Simplification -- **Shorter copy**: Cut every sentence in half, then do it again -- **Active voice**: "Save changes" not "Changes will be saved" -- **Remove jargon**: Plain language always wins -- **Scannable structure**: Short paragraphs, bullet points, clear headings -- **Essential information only**: Remove marketing fluff, legalese, hedging -- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once - -### Code Simplification -- **Remove unused code**: Dead CSS, unused components, orphaned files -- **Flatten component trees**: Reduce nesting depth -- **Consolidate styles**: Merge similar styles, use utilities consistently -- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? - -**NEVER**: -- Remove necessary functionality (simplicity ≠ feature-less) -- Sacrifice accessibility for simplicity (clear labels and ARIA still required) -- Make things so simple they're unclear (mystery ≠ minimalism) -- Remove information users need to make decisions -- Eliminate hierarchy completely (some things should stand out) -- Oversimplify complex domains (match complexity to actual task complexity) - -## Verify Simplification - -Ensure simplification improves usability: - -- **Faster task completion**: Can users accomplish goals more quickly? -- **Reduced cognitive load**: Is it easier to understand what to do? -- **Still complete**: Are all necessary features still accessible? -- **Clearer hierarchy**: Is it obvious what matters most? -- **Better performance**: Does simpler design load faster? - -## Document Removed Complexity - -If you removed features or options: -- Document why they were removed -- Consider if they need alternative access points -- Note any user feedback to monitor - -Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/.trae/skills/harden/SKILL.md b/.trae/skills/harden/SKILL.md deleted file mode 100644 index 31b996fa8..000000000 --- a/.trae/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

Failed to load data. {error.message}

- - -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/.trae/skills/impeccable/SKILL.md b/.trae/skills/impeccable/SKILL.md index 210b9c92f..005f325c3 100644 --- a/.trae/skills/impeccable/SKILL.md +++ b/.trae/skills/impeccable/SKILL.md @@ -1,16 +1,18 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system. +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." version: 2.1.1 user-invocable: true -argument-hint: "[craft|teach|extract]" +argument-hint: "[command] [target]" license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -23,8 +25,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -34,7 +34,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -270,7 +270,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -284,82 +284,96 @@ Remember: the model is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `/impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `/impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `/impeccable craft [feature]` - Shape, then build a feature end-to-end +> `/impeccable shape [feature]` - Plan UX/UI before writing code +> `/impeccable teach` - Set up design context for this project (one-time) +> `/impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `/impeccable critique [target]` - UX design review with heuristic scoring +> `/impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `/impeccable polish [target]` - Final quality pass before shipping +> `/impeccable bolder [target]` - Amplify safe/bland designs +> `/impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `/impeccable distill [target]` - Strip to essence, remove complexity +> `/impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `/impeccable animate [target]` - Add purposeful animations and motion +> `/impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `/impeccable typeset [target]` - Improve typography hierarchy and fonts +> `/impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `/impeccable delight [target]` - Add personality and memorable touches +> `/impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `/impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `/impeccable adapt [target]` - Adapt for different devices and screen sizes +> `/impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `/impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates /audit) +> `/impeccable unpin ` - Remove a pinned shortcut +> +> Or use `/impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke /impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `/impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `/audit` instead of `/impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node .trae/skills/impeccable/scripts/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to RULES.md. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `/impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. \ No newline at end of file +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). \ No newline at end of file diff --git a/.trae/skills/impeccable/reference/adapt.md b/.trae/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/.trae/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/.trae/skills/impeccable/reference/animate.md b/.trae/skills/impeccable/reference/animate.md new file mode 100644 index 000000000..0186ce081 --- /dev/null +++ b/.trae/skills/impeccable/reference/animate.md @@ -0,0 +1,166 @@ +> **Additional context needed**: performance constraints. + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + + +--- + +## 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. diff --git a/.trae/skills/impeccable/reference/audit.md b/.trae/skills/impeccable/reference/audit.md new file mode 100644 index 000000000..206fafb5c --- /dev/null +++ b/.trae/skills/impeccable/reference/audit.md @@ -0,0 +1,134 @@ +Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. + +This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. + +## Diagnostic Scan + +Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below. + +### 1. Accessibility (A11y) + +**Check for**: +- **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) +- **Missing ARIA**: Interactive elements without proper roles, labels, or states +- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps +- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons +- **Alt text**: Missing or poor image descriptions +- **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA) + +### 2. Performance + +**Check for**: +- **Layout thrashing**: Reading/writing layout properties in loops +- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity +- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change +- **Bundle size**: Unnecessary imports, unused dependencies +- **Render performance**: Unnecessary re-renders, missing memoization + +**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized) + +### 3. Theming + +**Check for**: +- **Hard-coded colors**: Colors not using design tokens +- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme +- **Inconsistent tokens**: Using wrong tokens, mixing token types +- **Theme switching issues**: Values that don't update on theme change + +**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly) + +### 4. Responsive Design + +**Check for**: +- **Fixed widths**: Hard-coded widths that break on mobile +- **Touch targets**: Interactive elements < 44x44px +- **Horizontal scroll**: Content overflow on narrow viewports +- **Text scaling**: Layouts that break when text size increases +- **Missing breakpoints**: No mobile/tablet variants + +**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets) + +### 5. Anti-Patterns (CRITICAL) + +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) + +## Generate Report + +### Audit Health Score + +| # | Dimension | Score | Key Finding | +|---|-----------|-------|-------------| +| 1 | Accessibility | ? | [most critical a11y issue or "--"] | +| 2 | Performance | ? | | +| 3 | Responsive Design | ? | | +| 4 | Theming | ? | | +| 5 | Anti-Patterns | ? | | +| **Total** | | **??/20** | **[Rating band]** | + +**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues) + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells. Be brutally honest. + +### Executive Summary +- Audit Health Score: **??/20** ([rating band]) +- Total issues found (count by severity: P0/P1/P2/P3) +- Top 3-5 critical issues +- Recommended next steps + +### Detailed Findings by Severity + +Tag every issue with **P0-P3 severity**: +- **P0 Blocking**: Prevents task completion — fix immediately +- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release +- **P2 Minor**: Annoyance, workaround exists — fix in next pass +- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits + +For each issue, document: +- **[P?] Issue name** +- **Location**: Component, file, line +- **Category**: Accessibility / Performance / Theming / Responsive / Anti-Pattern +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (prefer: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) + +### Patterns & Systemic Issues + +Identify recurring problems that indicate systemic gaps rather than one-off mistakes: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" + +### Positive Findings + +Note what's working well — good practices to maintain and replicate. + +## Recommended Actions + +List recommended commands in priority order (P0 first, then P1, then P2): + +1. **[P?] `/command-name`** — Brief description (specific context from audit findings) +2. **[P?] `/command-name`** — Brief description (specific context) + +**Rules**: Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset. Map findings to the most appropriate command. End with `/impeccable polish` as the final step if any fixes were recommended. + +After presenting the summary, tell the user: + +> You can ask me to run these one at a time, all at once, or in any order you prefer. +> +> Re-run `/impeccable audit` after fixes to see your score improve. + +**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Provide generic recommendations (be specific and actionable) +- Skip positive findings (celebrate what works) +- Forget to prioritize (everything can't be P0) +- Report false positives without verification + +Remember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement. diff --git a/.trae/skills/impeccable/reference/bolder.md b/.trae/skills/impeccable/reference/bolder.md new file mode 100644 index 000000000..cb3481663 --- /dev/null +++ b/.trae/skills/impeccable/reference/bolder.md @@ -0,0 +1,106 @@ +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. diff --git a/.trae/skills/impeccable/reference/clarify.md b/.trae/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/.trae/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/.trae/skills/critique/reference/cognitive-load.md b/.trae/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from .trae/skills/critique/reference/cognitive-load.md rename to .trae/skills/impeccable/reference/cognitive-load.md diff --git a/.trae/skills/impeccable/reference/colorize.md b/.trae/skills/impeccable/reference/colorize.md new file mode 100644 index 000000000..a4ce5072e --- /dev/null +++ b/.trae/skills/impeccable/reference/colorize.md @@ -0,0 +1,134 @@ +> **Additional context needed**: existing brand colors. + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. diff --git a/.trae/skills/impeccable/reference/craft.md b/.trae/skills/impeccable/reference/craft.md index 8cddbc9db..b038cf96d 100644 --- a/.trae/skills/impeccable/reference/craft.md +++ b/.trae/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run /shape, passing along whatever feature description the user provided. +Run /impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run /shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run /impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/.trae-cn/skills/critique/SKILL.md b/.trae/skills/impeccable/reference/critique.md similarity index 84% rename from .trae-cn/skills/critique/SKILL.md rename to .trae/skills/impeccable/reference/critique.md index e89e7b281..8866153fc 100644 --- a/.trae-cn/skills/critique/SKILL.md +++ b/.trae/skills/impeccable/reference/critique.md @@ -1,18 +1,6 @@ ---- -name: critique -description: Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component. -version: 2.1.1 -user-invocable: true -argument-hint: "[area (feature, page, component...)]" ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -30,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -44,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -94,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -140,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) -- **Suggested command**: Which command could address this (from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive) +- **Suggested command**: Which command could address this (from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `RULES.md` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -176,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. ask the user directly to clarify what you cannot infer. These answers will shape the action plan. @@ -196,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -209,17 +197,17 @@ List recommended commands in priority order, based on the user's answers: ... **Rules for recommendations**: -- Only recommend commands from: /animate, /quieter, /shape, /optimize, /adapt, /clarify, /layout, /distill, /delight, /audit, /harden, /polish, /bolder, /typeset, /critique, /colorize, /overdrive +- Only recommend commands from: /impeccable adapt, /impeccable animate, /impeccable audit, /impeccable bolder, /impeccable clarify, /impeccable colorize, /impeccable critique, /impeccable delight, /impeccable distill, /impeccable harden, /impeccable layout, /impeccable optimize, /impeccable overdrive, /impeccable polish, /impeccable quieter, /impeccable shape, /impeccable typeset - Order by the user's stated priorities first, then by impact - Each item's description should carry enough context that the command knows what to focus on - Map each Priority Issue to the appropriate command - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `/polish` as the final step if any fixes were recommended +- End with `/impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `/critique` after fixes to see your score improve. \ No newline at end of file +> Re-run `/impeccable critique` after fixes to see your score improve. diff --git a/.trae/skills/impeccable/reference/delight.md b/.trae/skills/impeccable/reference/delight.md new file mode 100644 index 000000000..8a781e70e --- /dev/null +++ b/.trae/skills/impeccable/reference/delight.md @@ -0,0 +1,295 @@ +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + + +--- + +## 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. diff --git a/.trae/skills/impeccable/reference/distill.md b/.trae/skills/impeccable/reference/distill.md new file mode 100644 index 000000000..4f47dc0b4 --- /dev/null +++ b/.trae/skills/impeccable/reference/distill.md @@ -0,0 +1,111 @@ +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." diff --git a/.trae/skills/impeccable/reference/harden.md b/.trae/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/.trae/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/.trae/skills/critique/reference/heuristics-scoring.md b/.trae/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from .trae/skills/critique/reference/heuristics-scoring.md rename to .trae/skills/impeccable/reference/heuristics-scoring.md diff --git a/.trae/skills/impeccable/reference/layout.md b/.trae/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/.trae/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/.trae/skills/impeccable/reference/optimize.md b/.trae/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/.trae/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/.trae/skills/impeccable/reference/overdrive.md b/.trae/skills/impeccable/reference/overdrive.md new file mode 100644 index 000000000..d84a147dc --- /dev/null +++ b/.trae/skills/impeccable/reference/overdrive.md @@ -0,0 +1,130 @@ +Start your response with: + +``` +──────────── ⚡ OVERDRIVE ───────────── +》》》 Entering overdrive mode... +``` + +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. + +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. + +### Propose Before Building + +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: + +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). +3. Only proceed with the direction the user confirms. + +Skipping this step risks building something embarrassing that needs to be thrown away. + +### Iterate with Browser Automation + +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. + +--- + +## Assess What "Extraordinary" Means Here + +The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** + +### For visual/marketing surfaces +Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. + +### For functional UI +Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. + +### For performance-critical UI +The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. + +### For data-heavy interfaces +Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. + +**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. + +## The Toolkit + +Organized by what you're trying to achieve, not by technology name. + +### Make transitions feel cinematic +- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. +- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes +- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. + +### Tie animation to scroll position +- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) + +### Render beyond CSS +- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. +- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. +- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. +- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. + +### Make data feel alive +- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. +- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. +- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. + +### Animate complex properties +- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. +- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. + +### Push performance boundaries +- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. +- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. +- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. + +### Interact with the device +- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. +- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. + +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. + +## Implement with Discipline + +### Progressive enhancement is non-negotiable + +Every technique must degrade gracefully. The experience without the enhancement must still be good. + +```css +@supports (animation-timeline: scroll()) { + .hero { animation-timeline: scroll(); } +} +``` + +```javascript +if ('gpu' in navigator) { /* WebGPU */ } +else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } +/* CSS-only fallback must still look good */ +``` + +### Performance rules + +- Target 60fps. If dropping below 50, simplify. +- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. +- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. +- Pause off-screen rendering. Kill what you can't see. +- Test on real mid-range devices, not just your development machine. + +### Polish is the difference + +The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. + +**NEVER**: +- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion +- Ship effects that cause jank on mid-range devices +- Use bleeding-edge APIs without a functional fallback +- Add sound without explicit user opt-in +- Use technical ambition to mask weak design fundamentals; fix those first with other commands +- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise + +## Verify the Result + +- **The wow test**: Show it to someone who hasn't seen it. Do they react? +- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? +- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? +- **The accessibility test**: Enable reduced motion. Still beautiful? +- **The context test**: Does this make sense for THIS brand and audience? + +Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. diff --git a/.trae/skills/critique/reference/personas.md b/.trae/skills/impeccable/reference/personas.md similarity index 100% rename from .trae/skills/critique/reference/personas.md rename to .trae/skills/impeccable/reference/personas.md diff --git a/.trae/skills/impeccable/reference/polish.md b/.trae/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/.trae/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/.trae/skills/impeccable/reference/quieter.md b/.trae/skills/impeccable/reference/quieter.md new file mode 100644 index 000000000..a8ad41809 --- /dev/null +++ b/.trae/skills/impeccable/reference/quieter.md @@ -0,0 +1,92 @@ +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. diff --git a/.trae/skills/impeccable/reference/shape.md b/.trae/skills/impeccable/reference/shape.md new file mode 100644 index 000000000..0ae281943 --- /dev/null +++ b/.trae/skills/impeccable/reference/shape.md @@ -0,0 +1,82 @@ +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. + +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. + +**Output**: A design brief that can be handed off to /impeccable craft, or directly to /impeccable for freeform implementation. + +## Philosophy + +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. + +## Phase 1: Discovery Interview + +**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. + +Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. + +### Purpose & Context +- What is this feature for? What problem does it solve? +- Who specifically will use it? (Not "users"; be specific: role, context, frequency) +- What does success look like? How will you know this feature is working? +- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) + +### Content & Data +- What content or data does this feature display or collect? +- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) +- What are the edge cases? (Empty state, error state, first-time use, power user) +- Is any content dynamic? What changes and how often? + +### Design Goals +- What's the single most important thing a user should do or understand here? +- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) +- Are there existing patterns in the product this should be consistent with? +- Are there specific examples (inside or outside the product) that capture what you're going for? + +### Constraints +- Are there technical constraints? (Framework, performance budget, browser support) +- Are there content constraints? (Localization, dynamic text length, user-generated content) +- Mobile/responsive requirements? +- Accessibility requirements beyond WCAG AA? + +### Anti-Goals +- What should this NOT be? What would be a wrong direction? +- What's the biggest risk of getting this wrong? + +## Phase 2: Design Brief + +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. + +### Brief Structure + +**1. Feature Summary** (2-3 sentences) +What this is, who it's for, what it needs to accomplish. + +**2. Primary User Action** +The single most important thing a user should do or understand here. + +**3. Design Direction** +How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. + +**4. Layout Strategy** +High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. + +**5. Key States** +List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. + +**6. Interaction Model** +How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? + +**7. Content Requirements** +What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. + +**8. Recommended References** +Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). + +**9. Open Questions** +Anything unresolved that the implementer should resolve during build. + +--- + +ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. + +Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this command internally.) diff --git a/.trae/skills/impeccable/reference/teach.md b/.trae/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..972ca25be --- /dev/null +++ b/.trae/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to RULES.md. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/.trae/skills/impeccable/reference/typeset.md b/.trae/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/.trae/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/.trae/skills/impeccable/scripts/cleanup-deprecated.mjs b/.trae/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/.trae/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/.trae/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/.trae/skills/impeccable/scripts/command-metadata.json b/.trae/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/.trae/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/.trae/skills/impeccable/scripts/pin.mjs b/.trae/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/.trae/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/.trae/skills/layout/SKILL.md b/.trae/skills/layout/SKILL.md deleted file mode 100644 index 6e532e38a..000000000 --- a/.trae/skills/layout/SKILL.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -name: layout -description: Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. \ No newline at end of file diff --git a/.trae/skills/optimize/SKILL.md b/.trae/skills/optimize/SKILL.md deleted file mode 100644 index d562cc53d..000000000 --- a/.trae/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/.trae/skills/overdrive/SKILL.md b/.trae/skills/overdrive/SKILL.md deleted file mode 100644 index 862a4c9c4..000000000 --- a/.trae/skills/overdrive/SKILL.md +++ /dev/null @@ -1,142 +0,0 @@ ---- -name: overdrive -description: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Start your response with: - -``` -──────────── ⚡ OVERDRIVE ───────────── -》》》 Entering overdrive mode... -``` - -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. - -### Propose Before Building - -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: - -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. -2. **ask the user directly to clarify what you cannot infer.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). -3. Only proceed with the direction the user confirms. - -Skipping this step risks building something embarrassing that needs to be thrown away. - -### Iterate with Browser Automation - -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. - ---- - -## Assess What "Extraordinary" Means Here - -The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?** - -### For visual/marketing surfaces -Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor. - -### For functional UI -Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics. - -### For performance-critical UI -The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates. - -### For data-heavy interfaces -Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally. - -**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around. - -## The Toolkit - -Organized by what you're trying to achieve, not by technology name. - -### Make transitions feel cinematic -- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations. -- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes -- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver. - -### Tie animation to scroll position -- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback) - -### Render beyond CSS -- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express. -- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2. -- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas. -- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable. - -### Make data feel alive -- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones. -- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers. -- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts. - -### Animate complex properties -- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate. -- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography. - -### Push performance boundaries -- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank. -- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background. -- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs. - -### Interact with the device -- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. -- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. - -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. - -## Implement with Discipline - -### Progressive enhancement is non-negotiable - -Every technique must degrade gracefully. The experience without the enhancement must still be good. - -```css -@supports (animation-timeline: scroll()) { - .hero { animation-timeline: scroll(); } -} -``` - -```javascript -if ('gpu' in navigator) { /* WebGPU */ } -else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ } -/* CSS-only fallback must still look good */ -``` - -### Performance rules - -- Target 60fps. If dropping below 50, simplify. -- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative. -- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport. -- Pause off-screen rendering. Kill what you can't see. -- Test on real mid-range devices, not just your development machine. - -### Polish is the difference - -The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable. - -**NEVER**: -- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion -- Ship effects that cause jank on mid-range devices -- Use bleeding-edge APIs without a functional fallback -- Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills -- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise - -## Verify the Result - -- **The wow test**: Show it to someone who hasn't seen it. Do they react? -- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice? -- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth? -- **The accessibility test**: Enable reduced motion. Still beautiful? -- **The context test**: Does this make sense for THIS brand and audience? - -Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do. \ No newline at end of file diff --git a/.trae/skills/polish/SKILL.md b/.trae/skills/polish/SKILL.md deleted file mode 100644 index 360b367f1..000000000 --- a/.trae/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. \ No newline at end of file diff --git a/.trae/skills/quieter/SKILL.md b/.trae/skills/quieter/SKILL.md deleted file mode 100644 index 373ae6869..000000000 --- a/.trae/skills/quieter/SKILL.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -name: quieter -description: Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current State - -Analyze what makes the design feel too intense: - -1. **Identify intensity sources**: - - **Color saturation**: Overly bright or saturated colors - - **Contrast extremes**: Too much high-contrast juxtaposition - - **Visual weight**: Too many bold, heavy elements competing - - **Animation excess**: Too much motion or overly dramatic effects - - **Complexity**: Too many visual elements, patterns, or decorations - - **Scale**: Everything is large and loud with no hierarchy - -2. **Understand the context**: - - What's the purpose? (Marketing vs tool vs reading experience) - - Who's the audience? (Some contexts need energy) - - What's working? (Don't throw away good ideas) - - What's the core message? (Preserve what matters) - -If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. - -**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. - -## Plan Refinement - -Create a strategy to reduce intensity while maintaining impact: - -- **Color approach**: Desaturate or shift to more sophisticated tones? -- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? -- **Simplification approach**: What can be removed entirely? -- **Sophistication approach**: How can we signal quality through restraint? - -**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. - -## Refine the Design - -Systematically reduce intensity across these dimensions: - -### Color Refinement -- **Reduce saturation**: Shift from fully saturated to 70-85% saturation -- **Soften palette**: Replace bright colors with muted, sophisticated tones -- **Reduce color variety**: Use fewer colors more thoughtfully -- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) -- **Gentler contrasts**: High contrast only where it matters most -- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness -- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead - -### Visual Weight Reduction -- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate -- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness -- **White space**: Increase breathing room, reduce density -- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely - -### Simplification -- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose -- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes -- **Reduce layering**: Flatten visual hierarchy where possible -- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows - -### Motion Reduction -- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing -- **Remove decorative animations**: Keep functional motion, remove flourishes -- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback -- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic -- **Remove animations entirely** if they're not serving a clear purpose - -### Composition Refinement -- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling -- **Align to grid**: Bring rogue elements back into systematic alignment -- **Even out spacing**: Replace extreme spacing variations with consistent rhythm - -**NEVER**: -- Make everything the same size/weight (hierarchy still matters) -- Remove all color (quiet ≠ grayscale) -- Eliminate all personality (maintain character through refinement) -- Sacrifice usability for aesthetics (functional elements still need clear affordances) -- Make everything small and light (some anchors needed) - -## Verify Quality - -Ensure refinement maintains quality: - -- **Still functional**: Can users still accomplish tasks easily? -- **Still distinctive**: Does it have character, or is it generic now? -- **Better reading**: Is text easier to read for extended periods? -- **Sophistication**: Does it feel more refined and premium? - -Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/.trae/skills/shape/SKILL.md b/.trae/skills/shape/SKILL.md deleted file mode 100644 index 7e83008b5..000000000 --- a/.trae/skills/shape/SKILL.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -name: shape -description: Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written. -version: 2.1.1 -user-invocable: true -argument-hint: "[feature to shape]" ---- - -## MANDATORY PREPARATION - -Invoke /impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run /impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to /impeccable craft, /impeccable, or any other implementation skill. - -## Philosophy - -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. - -## Phase 1: Discovery Interview - -**Do NOT write any code or make any design decisions during this phase.** Your only job is to understand the feature deeply enough to make excellent design decisions later. - -Ask these questions in conversation, adapting based on answers. Don't dump them all at once; have a natural dialogue. ask the user directly to clarify what you cannot infer. - -### Purpose & Context -- What is this feature for? What problem does it solve? -- Who specifically will use it? (Not "users"; be specific: role, context, frequency) -- What does success look like? How will you know this feature is working? -- What's the user's state of mind when they reach this feature? (Rushed? Exploring? Anxious? Focused?) - -### Content & Data -- What content or data does this feature display or collect? -- What are the realistic ranges? (Minimum, typical, maximum, e.g., 0 items, 5 items, 500 items) -- What are the edge cases? (Empty state, error state, first-time use, power user) -- Is any content dynamic? What changes and how often? - -### Design Goals -- What's the single most important thing a user should do or understand here? -- What should this feel like? (Fast/efficient? Calm/trustworthy? Fun/playful? Premium/refined?) -- Are there existing patterns in the product this should be consistent with? -- Are there specific examples (inside or outside the product) that capture what you're going for? - -### Constraints -- Are there technical constraints? (Framework, performance budget, browser support) -- Are there content constraints? (Localization, dynamic text length, user-generated content) -- Mobile/responsive requirements? -- Accessibility requirements beyond WCAG AA? - -### Anti-Goals -- What should this NOT be? What would be a wrong direction? -- What's the biggest risk of getting this wrong? - -## Phase 2: Design Brief - -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. - -### Brief Structure - -**1. Feature Summary** (2-3 sentences) -What this is, who it's for, what it needs to accomplish. - -**2. Primary User Action** -The single most important thing a user should do or understand here. - -**3. Design Direction** -How this should feel. What aesthetic approach fits. Reference the project's design context from `.impeccable.md` and explain how this feature should express it. - -**4. Layout Strategy** -High-level spatial approach: what gets emphasis, what's secondary, how information flows. Describe the visual hierarchy and rhythm, not specific CSS. - -**5. Key States** -List every state the feature needs: default, empty, loading, error, success, edge cases. For each, note what the user needs to see and feel. - -**6. Interaction Model** -How users interact with this feature. What happens on click, hover, scroll? What feedback do they get? What's the flow from entry to completion? - -**7. Content Requirements** -What copy, labels, empty state messages, error messages, and microcopy are needed. Note any dynamic content and its realistic ranges. - -**8. Recommended References** -Based on the brief, list which impeccable reference files would be most valuable during implementation (e.g., spatial-design.md for complex layouts, motion-design.md for animated features, interaction-design.md for form-heavy features). - -**9. Open Questions** -Anything unresolved that the implementer should resolve during build. - ---- - -ask the user directly to clarify what you cannot infer. Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. - -Once confirmed, the brief is complete. The user can now hand it to /impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use /impeccable craft instead, which runs this skill internally.) \ No newline at end of file diff --git a/.trae/skills/typeset/SKILL.md b/.trae/skills/typeset/SKILL.md deleted file mode 100644 index 166d4b741..000000000 --- a/.trae/skills/typeset/SKILL.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -name: typeset -description: Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography. -version: 2.1.1 -user-invocable: true -argument-hint: "[target]" ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke /impeccable — 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 /impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. \ No newline at end of file diff --git a/AGENTS.md b/AGENTS.md index 54a0d2c35..6252f0cb8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,6 +1,6 @@ # Impeccable -The vocabulary you didn't know you needed. 1 skill, 18 commands, and curated anti-patterns for impeccable style. Works with Cursor, Claude Code, Gemini CLI, and Codex CLI. +The vocabulary you didn't know you needed. 1 skill, 20 commands, and curated anti-patterns for impeccable style. Works with Cursor, Claude Code, Gemini CLI, and Codex CLI. ## Repository Purpose diff --git a/CLAUDE.md b/CLAUDE.md index e95cff647..87349124c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -92,20 +92,26 @@ There are three independently versioned components. Only bump the one(s) that ac - Update for user-facing changes only, not internal build/tooling details - Use the most prominent version that changed (e.g. skills version for skill consolidation) -## Adding New Skills +## Adding New Sub-commands -When adding a new user-invocable skill, update the command count in **all** of these locations: +All commands are accessed through `/impeccable`. To add a new one: -- `public/index.html` → meta descriptions, hero box, section lead -- `public/cheatsheet.html` → meta description, subtitle, `commandCategories`, `commandRelationships` -- `public/js/data.js` → `commandProcessSteps`, `commandCategories`, `commandRelationships` -- `public/js/components/framework-viz.js` → `commandSymbols`, `commandNumbers` -- `public/js/demos/commands/` → new demo file + import in `index.js` -- `README.md` → intro, command count, commands table -- `NOTICE.md` → steering commands count -- `AGENTS.md` → intro command count -- `.claude-plugin/plugin.json` → description -- `.claude-plugin/marketplace.json` → metadata description + plugin description +1. Create `source/skills/impeccable/reference/.md` with the command's instructions +2. Add a row to the **Sub-command reference table** in `source/skills/impeccable/SKILL.md` +3. Add an entry to the **Command menu** section in the same file +4. Add the command name to `IMPECCABLE_SUB_COMMANDS` in `scripts/lib/utils.js` +5. Add it to `VALID_COMMANDS` in `source/skills/impeccable/scripts/pin.mjs` +6. Add its metadata to `source/skills/impeccable/scripts/command-metadata.json` + +The build system counts commands from the router table automatically. Update the command count in **all** of these locations: + +- `public/index.html` -- meta descriptions, hero box, section lead +- `public/cheatsheet.html` -- meta description, subtitle +- `README.md` -- intro, command count, commands table +- `NOTICE.md` -- command count +- `AGENTS.md` -- intro command count +- `.claude-plugin/plugin.json` -- description +- `.claude-plugin/marketplace.json` -- metadata description + plugin description ## Evals Framework (private, gitignored) diff --git a/NOTICE.md b/NOTICE.md index 04be4620b..2843ee71b 100644 --- a/NOTICE.md +++ b/NOTICE.md @@ -13,5 +13,5 @@ The `impeccable` skill in this project builds on Anthropic's original frontend-d This project extends the original with: - 7 domain-specific reference files (typography, color-and-contrast, spatial-design, motion-design, interaction-design, responsive-design, ux-writing) -- 18 steering commands +- 20 commands - Expanded patterns and anti-patterns diff --git a/README.md b/README.md index fdbe50d19..629065501 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Impeccable -The vocabulary you didn't know you needed. 1 skill, 18 commands, and curated anti-patterns for impeccable frontend design. +The vocabulary you didn't know you needed. 1 skill, 20 commands, and curated anti-patterns for impeccable frontend design. > **Quick start:** Visit [impeccable.style](https://impeccable.style) to download ready-to-use bundles. @@ -12,7 +12,7 @@ Every LLM learned from the same generic templates. Without guidance, you get the Impeccable fights that bias with: - **An expanded skill** with 7 domain-specific reference files ([view source](source/skills/impeccable/)) -- **18 steering commands** to audit, review, polish, distill, animate, and more +- **20 commands** to audit, review, polish, distill, animate, and more - **Curated anti-patterns** that explicitly tell the AI what NOT to do ## What's Included @@ -31,65 +31,47 @@ A comprehensive design skill with 7 domain-specific references ([view skill](sou | [responsive-design](source/skills/impeccable/reference/responsive-design.md) | Mobile-first, fluid design, container queries | | [ux-writing](source/skills/impeccable/reference/ux-writing.md) | Button labels, error messages, empty states | -### 18 Commands +### 20 Commands + +All commands are accessed through `/impeccable`: | Command | What it does | |---------|--------------| -| `/impeccable teach` | One-time setup: gather design context, save to config | | `/impeccable craft` | Full shape-then-build flow with visual iteration | +| `/impeccable teach` | One-time setup: gather design context, save to config | | `/impeccable extract` | Pull reusable components and tokens into the design system | -| `/audit` | Run technical quality checks (a11y, performance, responsive) | -| `/critique` | UX design review: hierarchy, clarity, emotional resonance | -| `/polish` | Final pass, design system alignment, and shipping readiness | -| `/distill` | Strip to essence | -| `/clarify` | Improve unclear UX copy | -| `/optimize` | Performance improvements | -| `/harden` | Error handling, onboarding, i18n, edge cases | -| `/animate` | Add purposeful motion | -| `/colorize` | Introduce strategic color | -| `/bolder` | Amplify boring designs | -| `/quieter` | Tone down overly bold designs | -| `/delight` | Add moments of joy | -| `/adapt` | Adapt for different devices | -| `/typeset` | Fix font choices, hierarchy, sizing | -| `/layout` | Fix layout, spacing, visual rhythm | -| `/overdrive` | Add technically extraordinary effects | +| `/impeccable shape` | Plan UX/UI before writing code | +| `/impeccable critique` | UX design review: hierarchy, clarity, emotional resonance | +| `/impeccable audit` | Run technical quality checks (a11y, performance, responsive) | +| `/impeccable polish` | Final pass, design system alignment, and shipping readiness | +| `/impeccable bolder` | Amplify boring designs | +| `/impeccable quieter` | Tone down overly bold designs | +| `/impeccable distill` | Strip to essence | +| `/impeccable harden` | Error handling, onboarding, i18n, edge cases | +| `/impeccable animate` | Add purposeful motion | +| `/impeccable colorize` | Introduce strategic color | +| `/impeccable typeset` | Fix font choices, hierarchy, sizing | +| `/impeccable layout` | Fix layout, spacing, visual rhythm | +| `/impeccable delight` | Add moments of joy | +| `/impeccable overdrive` | Add technically extraordinary effects | +| `/impeccable clarify` | Improve unclear UX copy | +| `/impeccable adapt` | Adapt for different devices | +| `/impeccable optimize` | Performance improvements | + +Use `/impeccable pin ` to create standalone shortcuts (e.g., `pin audit` creates `/audit`). #### Usage Examples -**`/audit`** - Run quality checks, get a report (no edits) ``` -/audit blog # Audit blog hub + post pages -/audit dashboard # Check dashboard components -/audit checkout flow # Focus on checkout UX +/impeccable audit blog # Audit blog hub + post pages +/impeccable critique landing # UX design review +/impeccable polish settings # Final pass before shipping +/impeccable harden checkout # Add error handling + edge cases ``` -*When to use:* Before making changes, to understand what needs fixing. -**`/normalize`** - Align with design system +Or use `/impeccable` directly with a description: ``` -/normalize blog # Apply design tokens, fix spacing -/normalize buttons # Standardize button styles -``` -*When to use:* After audit, to fix inconsistencies. - -**`/critique`** - UX design review -``` -/critique landing page # Review landing page UX -/critique onboarding # Check onboarding flow -``` -*When to use:* When you want design feedback, not technical fixes. - -**`/polish`** - Final pass before shipping -``` -/polish feature modal # Clean up modal before release -/polish settings page # Final review of settings UI -``` -*When to use:* Last step before deploying to production. - -**Combining commands:** -``` -/audit /normalize /polish blog # Full workflow: audit → fix → polish -/critique /harden checkout # UX review + add error handling +/impeccable redo this hero section ``` ### Anti-Patterns diff --git a/content/site/anti-patterns-catalog.js b/content/site/anti-patterns-catalog.js index cae6dd9c7..b16fecf28 100644 --- a/content/site/anti-patterns-catalog.js +++ b/content/site/anti-patterns-catalog.js @@ -75,7 +75,7 @@ export const LAYER_LABELS = { export const LAYER_DESCRIPTIONS = { cli: 'Deterministic. Runs from `npx impeccable detect` on files, no browser required.', browser: 'Deterministic, but needs real browser layout. Runs via the browser extension or Puppeteer, not the plain CLI.', - llm: 'Not caught by any deterministic detector. Flagged by /critique during its LLM design review.', + llm: 'Not caught by any deterministic detector. Flagged by /impeccable critique during its LLM design review.', }; // ─── Visual examples ───────────────────────────────────────────────── diff --git a/content/site/partials/header.html b/content/site/partials/header.html index f52c00a8d..87fdc4193 100644 --- a/content/site/partials/header.html +++ b/content/site/partials/header.html @@ -7,7 +7,7 @@
diff --git a/content/site/skills/adapt.md b/content/site/skills/adapt.md index 71786e04e..a6b4996bf 100644 --- a/content/site/skills/adapt.md +++ b/content/site/skills/adapt.md @@ -4,7 +4,7 @@ tagline: "Make designs work across screens, devices, and contexts without amputa ## When to use it -`/adapt` is for taking a design built for one context and making it work in another. Mobile from desktop, tablet from mobile, print from web, embedded from standalone, email from dashboard. Reach for it when the source design is solid but falls apart at other breakpoints, on touch, or in a different container. +`/impeccable adapt` is for taking a design built for one context and making it work in another. Mobile from desktop, tablet from mobile, print from web, embedded from standalone, email from dashboard. Reach for it when the source design is solid but falls apart at other breakpoints, on touch, or in a different container. Not for building responsive from scratch. For that, start with `/impeccable` and shape the layout responsive-first. Adapt is for the "we never thought about mobile" backfill. @@ -22,7 +22,7 @@ The non-negotiable rule: adapt, do not amputate. Critical functionality cannot d ## Try it ``` -/adapt the settings page for mobile +/impeccable adapt the settings page for mobile ``` Expected changes: @@ -37,4 +37,4 @@ Expected changes: - **Amputating features.** If the mobile version hides things the desktop version can do, that is a regression, not an adaptation. Fight for the feature. - **Treating mobile as "smaller desktop".** Mobile is a different context: thumbs, interruption, short sessions. Adapt to the context, not to the viewport width. -- **Skipping `/harden` afterward.** Responsive layouts reveal edge cases. Run hardening after adapt to catch the ones that only show up at 320px. +- **Skipping `/impeccable harden` afterward.** Responsive layouts reveal edge cases. Run hardening after adapt to catch the ones that only show up at 320px. diff --git a/content/site/skills/animate.md b/content/site/skills/animate.md index 6781a8675..0cea287b8 100644 --- a/content/site/skills/animate.md +++ b/content/site/skills/animate.md @@ -4,7 +4,7 @@ tagline: "Purposeful motion that conveys state, not decoration." ## When to use it -`/animate` is for interfaces that feel lifeless, where state changes are instant and jarring, where loading just pops in, where the user never quite trusts that their click registered. Use it to add the small motions that communicate what is happening: entrances, exits, feedback, transitions between states. +`/impeccable animate` is for interfaces that feel lifeless, where state changes are instant and jarring, where loading just pops in, where the user never quite trusts that their click registered. Use it to add the small motions that communicate what is happening: entrances, exits, feedback, transitions between states. Do not use it to add bounces or elastic springs for the sake of energy. That is decoration, and this skill will not give it to you. @@ -25,7 +25,7 @@ The skill animates `transform` and `opacity` only. If you find yourself animatin ## Try it ``` -/animate the sign-up flow +/impeccable animate the sign-up flow ``` Typical additions: diff --git a/content/site/skills/audit.md b/content/site/skills/audit.md index b1e340636..9d7b68ba9 100644 --- a/content/site/skills/audit.md +++ b/content/site/skills/audit.md @@ -4,7 +4,7 @@ tagline: "Five-dimension technical quality check with P0 to P3 severity." ## When to use it -`/audit` is the technical counterpart to `/critique`. Where `/critique` asks "does this feel right", `/audit` asks "does this hold up". It runs accessibility, performance, theming, responsive design, and anti-pattern checks against the implementation, scores each dimension 0 to 4, and produces a plan with P0 to P3 severity ratings. +`/impeccable audit` is the technical counterpart to `/impeccable critique`. Where `/impeccable critique` asks "does this feel right", `/impeccable audit` asks "does this hold up". It runs accessibility, performance, theming, responsive design, and anti-pattern checks against the implementation, scores each dimension 0 to 4, and produces a plan with P0 to P3 severity ratings. Use it before shipping, during a quality sprint, or whenever a tech lead says "we should really look at accessibility". @@ -20,12 +20,12 @@ The skill scans your code across five dimensions: Each dimension gets a 0 to 4 score. Each finding gets a severity: P0 blocks the release, P1 should fix this sprint, P2 is next cycle, P3 is polish. You get back a single document you can paste into a ticket tracker. -Audit does not fix anything. It documents. Route the findings to `/polish`, `/harden`, or `/optimize` depending on the category. +Audit does not fix anything. It documents. Route the findings to `/impeccable polish`, `/impeccable harden`, or `/impeccable optimize` depending on the category. ## Try it ``` -/audit the checkout flow +/impeccable audit the checkout flow ``` Expected output: @@ -41,10 +41,10 @@ Performance: 3/4 (good) ... ``` -Hand the P0s to `/harden`, the theming and typography P1s to `/typeset` and `/polish`, the rest to `/polish`. +Hand the P0s to `/impeccable harden`, the theming and typography P1s to `/impeccable typeset` and `/impeccable polish`, the rest to `/impeccable polish`. ## Pitfalls -- **Confusing it with `/critique`.** Audit is implementation quality. Critique is design quality. Run both for a full picture. +- **Confusing it with `/impeccable critique`.** Audit is implementation quality. Critique is design quality. Run both for a full picture. - **Fixing P3s before P0s.** The severity scale exists for a reason. Start at the top. - **Skipping the dimensions you think are fine.** Theming and responsive are the ones most people assume are fine until they are not. diff --git a/content/site/skills/bolder.md b/content/site/skills/bolder.md index f636e03d8..cfaf5dd4f 100644 --- a/content/site/skills/bolder.md +++ b/content/site/skills/bolder.md @@ -4,7 +4,7 @@ tagline: "Push safe designs toward impact without sliding into chaos." ## When to use it -Reach for `/bolder` when the interface looks like every other interface. Generic sans, medium weights, soft shadows, modest accent color, reasonable spacing, forgettable. The design is not wrong, it is just safe. Use bolder when a project can handle presence and the current state is not bringing any. +Reach for `/impeccable bolder` when the interface looks like every other interface. Generic sans, medium weights, soft shadows, modest accent color, reasonable spacing, forgettable. The design is not wrong, it is just safe. Use bolder when a project can handle presence and the current state is not bringing any. Do not use it on dashboards people stare at for hours. Boldness earns its place on marketing pages, hero moments, and content features. Not in operator tools. @@ -22,7 +22,7 @@ The skill does not add more. It amplifies what is already there. If the design h ## Try it ``` -/bolder the landing page hero +/impeccable bolder the landing page hero ``` Expected changes: @@ -35,6 +35,6 @@ Expected changes: ## Pitfalls -- **Running it on the wrong page.** Product dashboards, settings, and forms should not be bold. They should be legible. Use `/layout` or `/polish` instead. -- **Confusing bold with loud.** Bold means committed and confident. Loud means shouting. Bolder is the former. If the result feels aggressive, follow up with `/quieter`. -- **Pairing it with `/delight` in the same pass.** Delight works best against a stable visual baseline. Bold first, stabilize, then delight. +- **Running it on the wrong page.** Product dashboards, settings, and forms should not be bold. They should be legible. Use `/impeccable layout` or `/impeccable polish` instead. +- **Confusing bold with loud.** Bold means committed and confident. Loud means shouting. Bolder is the former. If the result feels aggressive, follow up with `/impeccable quieter`. +- **Pairing it with `/impeccable delight` in the same pass.** Delight works best against a stable visual baseline. Bold first, stabilize, then delight. diff --git a/content/site/skills/clarify.md b/content/site/skills/clarify.md index 78593f650..47d7f3298 100644 --- a/content/site/skills/clarify.md +++ b/content/site/skills/clarify.md @@ -4,7 +4,7 @@ tagline: "Rewrite confusing UX copy so interfaces explain themselves." ## When to use it -`/clarify` is for interface text that makes people stop and think. Confusing labels, ambiguous button copy, error messages that blame the user, tooltips that repeat the label, empty states that say nothing useful. Use it when the problem is not the layout or the color, it is the words. +`/impeccable clarify` is for interface text that makes people stop and think. Confusing labels, ambiguous button copy, error messages that blame the user, tooltips that repeat the label, empty states that say nothing useful. Use it when the problem is not the layout or the color, it is the words. Good triggers: "users do not understand this field", "the error message is not helpful", "I cannot write good button copy", "this tooltip is a waste". @@ -24,7 +24,7 @@ The skill uses the audience and mental state from `.impeccable.md` to tune voice ## Try it ``` -/clarify the billing form +/impeccable clarify the billing form ``` Before and after, typical: @@ -37,6 +37,6 @@ Before and after, typical: ## Pitfalls -- **Writing cleverer, not clearer.** Clarify is not for voice upgrades. If the copy is already clear, do not reach for this skill. Use `/delight` instead when you want personality. +- **Writing cleverer, not clearer.** Clarify is not for voice upgrades. If the copy is already clear, do not reach for this skill. Use `/impeccable delight` instead when you want personality. - **Skipping the audience question.** Clarify needs to know who is reading. If `.impeccable.md` does not specify audience technical level, the rewrites will be generic. - **Running clarify on marketing copy.** Clarify is for functional UX text: labels, errors, instructions. Marketing copy needs a different set of moves and a human writer. diff --git a/content/site/skills/colorize.md b/content/site/skills/colorize.md index 9617abbd4..9dbb52598 100644 --- a/content/site/skills/colorize.md +++ b/content/site/skills/colorize.md @@ -4,7 +4,7 @@ tagline: "Add strategic color to monochrome interfaces without going garish." ## When to use it -`/colorize` is the counterweight to "everything is gray". Dashboards that read as a beige wall, forms with no accent, content pages that could be any SaaS product. Reach for it when the interface is functional but emotionally flat, and you want warmth without tipping into the AI color palette (purple-to-pink, cyan neon, dark mode glow). +`/impeccable colorize` is the counterweight to "everything is gray". Dashboards that read as a beige wall, forms with no accent, content pages that could be any SaaS product. Reach for it when the interface is functional but emotionally flat, and you want warmth without tipping into the AI color palette (purple-to-pink, cyan neon, dark mode glow). ## How it works @@ -20,7 +20,7 @@ Importantly, it uses OKLCH rather than HSL so that equal lightness steps look eq ## Try it ``` -/colorize the dashboard +/impeccable colorize the dashboard ``` Expected diff: @@ -34,5 +34,5 @@ Expected diff: ## Pitfalls - **Running it without a brand hue.** Colorize needs a starting point. If `.impeccable.md` does not specify one, it will ask. Do not let it pick from the AI color palette defaults. -- **Expecting it to fix the AI color palette problem.** If your design already has purple gradients and cyan neon, you need `/quieter` first, then colorize can rebuild. -- **Using it on already-colorful interfaces.** That is a `/quieter` job. Colorize adds, it does not subtract. +- **Expecting it to fix the AI color palette problem.** If your design already has purple gradients and cyan neon, you need `/impeccable quieter` first, then colorize can rebuild. +- **Using it on already-colorful interfaces.** That is a `/impeccable quieter` job. Colorize adds, it does not subtract. diff --git a/content/site/skills/craft.md b/content/site/skills/craft.md new file mode 100644 index 000000000..cec545ca6 --- /dev/null +++ b/content/site/skills/craft.md @@ -0,0 +1,42 @@ +--- +tagline: "Shape the design, then build it, all in one flow." +--- + +## When to use it + +`/impeccable craft` is the end-to-end build command. Give it a feature description and it runs the whole pipeline: structured discovery, reference loading, implementation, visual iteration. Use it when you are starting a new feature from zero and want the whole workflow in one invocation. + +Reach for it when: + +- **You are building a new feature and want the full flow.** You do not want to manage the steps yourself. +- **You know what you are building but not how it should look.** The discovery phase forces the design thinking before implementation locks it in. +- **You want visual iteration by default.** `craft` checks the result in a browser and refines until the polish is high, instead of shipping the first working version. + +If you only want the thinking without the code, use `/impeccable shape` standalone. If you already have a clear vision and just want to build, call `/impeccable` directly with your feature description. `craft` sits in between: structured, complete, opinionated. + +## How it works + +`craft` runs four phases in order: + +1. **Shape the design.** Runs `/impeccable shape` internally: a short discovery conversation about purpose, users, content, constraints, and goals. The output is a design brief you can read and push back on. +2. **Load references.** Based on the brief, pulls in the right reference files (spatial, typography, motion, color, interaction, responsive, UX writing) so the model has the relevant principles loaded before it starts coding. +3. **Build.** Implements the feature in a deliberate order: structure first, then spacing and hierarchy, then type and color, then states, then motion, then responsive. Every decision traces back to the brief. +4. **Visual iteration.** Opens the result in a browser, checks it against the brief and the anti-pattern catalog, and refines until it matches the intent. This step is critical. The first working version is never the shipped version. + +The discovery phase is non-skippable and that is the point. Most AI-generated UIs fail because nobody asked what the user was trying to accomplish before the model started writing JSX. `craft` inverts that. + +## Try it + +``` +/impeccable craft a pricing page for a developer tool +``` + +Expect a 5 to 10 question discovery interview first. Questions about your audience, the product's personality, the emotional tone you want, anti-references, and constraints. Then a design brief. Then implementation, with the browser checked at each stage. Expect multiple iteration rounds in the visual polish phase. + +The whole run is longer than a typical command because it includes the thinking, the building, and the refining. That is the trade: more upfront structure, less cleanup afterwards. + +## Pitfalls + +- **Using it for small changes.** `craft` is for new features, not touch-ups. For existing code, reach for `/impeccable polish`, `/impeccable critique`, or a specific refinement command instead. +- **Rushing the discovery phase.** The interview feels slow compared to "just start coding". It is not. Answering the questions carefully produces a sharper brief, which produces a sharper build, which produces fewer rewrites. +- **Skipping the visual iteration.** The phase exists for a reason. The gap between "technically works" and "feels right" is closed with visual polish, not code review. Let it run. diff --git a/content/site/skills/critique.md b/content/site/skills/critique.md index 49a0a395e..4381803b5 100644 --- a/content/site/skills/critique.md +++ b/content/site/skills/critique.md @@ -4,13 +4,13 @@ tagline: "A design review with scoring, persona tests, and automated detection." ## When to use it -Reach for `/critique` when you want an honest second opinion on something you already built. Not "does it work" but "is it any good". The skill scores your interface against Nielsen's 10 heuristics, runs cognitive load checks, tests through persona lenses, and cross-references an automated detector for 25 concrete anti-patterns. +Reach for `/impeccable critique` when you want an honest second opinion on something you already built. Not "does it work" but "is it any good". The skill scores your interface against Nielsen's 10 heuristics, runs cognitive load checks, tests through persona lenses, and cross-references an automated detector for 25 concrete anti-patterns. Use it when a page is functionally done and you want to know if it reads as intentional or as AI slop. ## How it works -`/critique` runs two independent assessments in parallel so they do not bias each other. +`/impeccable critique` runs two independent assessments in parallel so they do not bias each other. The first is an **LLM design review**: the model reads your source, visually inspects the live page if browser automation is available, and walks the impeccable skill's full DO/DON'T catalog. It scores Nielsen's heuristics, counts cognitive load failures, traces the emotional journey through the flow, and flags AI slop. @@ -23,7 +23,7 @@ The two reports merge into one prioritized list: what is working, the three to f Point it at a page: ``` -/critique the homepage hero +/impeccable critique the homepage hero ``` You get back a scored report. Typical shape: @@ -34,7 +34,7 @@ You get back a scored report. Typical shape: - **Priority issues**: three to five items, each with what, why, and fix - **Questions to answer**: the ones the interface itself cannot decide for you -From there, pair with `/polish` or `/distill` to act on the fixes. +From there, pair with `/impeccable polish` or `/impeccable distill` to act on the fixes. ## Pitfalls diff --git a/content/site/skills/delight.md b/content/site/skills/delight.md index fbd9e805a..8d7d913c4 100644 --- a/content/site/skills/delight.md +++ b/content/site/skills/delight.md @@ -4,7 +4,7 @@ tagline: "Small moments of personality that turn functional into memorable." ## When to use it -`/delight` is for interfaces that work but do not feel like anything. Use it when the core experience is solid and you want to add the small human touches that make people remember it: a considered empty state, a loading message with a point of view, a success animation that feels earned, a microcopy moment that makes someone smile. +`/impeccable delight` is for interfaces that work but do not feel like anything. Use it when the core experience is solid and you want to add the small human touches that make people remember it: a considered empty state, a loading message with a point of view, a success animation that feels earned, a microcopy moment that makes someone smile. It is a finishing skill. Never the first thing you run on a new build. @@ -25,7 +25,7 @@ The rule is: every delight moment must still work perfectly if you delete the de ## Try it ``` -/delight the first-run experience +/impeccable delight the first-run experience ``` Expected additions: diff --git a/content/site/skills/distill.md b/content/site/skills/distill.md index d8a112f15..d6d53096e 100644 --- a/content/site/skills/distill.md +++ b/content/site/skills/distill.md @@ -4,9 +4,9 @@ tagline: "Ruthless subtraction. Strip designs to their essence." ## When to use it -`/distill` removes what should not be there. Competing buttons, redundant information, decorative borders, three fonts where one works, six navigation items where three belong. Use it when an interface feels cluttered, busy, or like it is trying to do too much at once. +`/impeccable distill` removes what should not be there. Competing buttons, redundant information, decorative borders, three fonts where one works, six navigation items where three belong. Use it when an interface feels cluttered, busy, or like it is trying to do too much at once. -Reach for it after `/critique` flags "cognitive load" or "visual noise", or any time a page has grown by accretion and no one has done the editing. +Reach for it after `/impeccable critique` flags "cognitive load" or "visual noise", or any time a page has grown by accretion and no one has done the editing. ## How it works @@ -22,7 +22,7 @@ The principle: simplicity is not about fewer features. It is about fewer obstacl ## Try it ``` -/distill this dashboard +/impeccable distill this dashboard ``` Before: four card styles, three button variants, two header treatments, a sidebar with 14 items grouped into 5 sections. @@ -41,4 +41,4 @@ Fewer things. Each one clearer. - **Confusing distill with delete.** Distill removes obstacles. It does not remove features users need. If a user relies on something daily, find a way to keep it quietly, not a way to cut it. - **Running it too early.** If the feature is still growing, distilling it now means distilling the same thing again next week. Wait until the shape is stable. -- **Expecting it to replace hierarchy work.** Sometimes the right fix is not removing things, it is arranging them. Reach for `/layout` when the problem is layout, not quantity. +- **Expecting it to replace hierarchy work.** Sometimes the right fix is not removing things, it is arranging them. Reach for `/impeccable layout` when the problem is layout, not quantity. diff --git a/content/site/skills/extract.md b/content/site/skills/extract.md index 963ad985f..e8325a3a8 100644 --- a/content/site/skills/extract.md +++ b/content/site/skills/extract.md @@ -4,7 +4,7 @@ tagline: "Pull reusable components, tokens, and patterns into the design system. ## When to use it -`/extract` is for the moment your codebase has accidentally become a design system. Repeated button styles in 12 places. Three variants of the same card. Hex colors scattered throughout. Hand-rolled spacing that accidentally matches a scale. Reach for it when you want to consolidate this drift into reusable primitives. +`/impeccable extract` is for the moment your codebase has accidentally become a design system. Repeated button styles in 12 places. Three variants of the same card. Hex colors scattered throughout. Hand-rolled spacing that accidentally matches a scale. Reach for it when you want to consolidate this drift into reusable primitives. Use it after a product has shipped enough features to reveal the patterns. Premature extraction creates abstractions that do not match reality. @@ -23,7 +23,7 @@ The skill is cautious. It only extracts things used three or more times, with th ## Try it ``` -/extract the button styles +/impeccable extract the button styles ``` Expected output: diff --git a/content/site/skills/harden.md b/content/site/skills/harden.md index d2c498a0d..8b80e2bd0 100644 --- a/content/site/skills/harden.md +++ b/content/site/skills/harden.md @@ -4,7 +4,7 @@ tagline: "Make interfaces production-ready. Edge cases, onboarding, i18n, error ## When to use it -`/harden` is for the day your interface meets reality. Real user data is messy: names that are 60 characters long, product titles in German, prices in the billions, empty lists, 500 errors, offline modes, right-to-left text. Designs that only work with perfect data are not production-ready. +`/impeccable harden` is for the day your interface meets reality. Real user data is messy: names that are 60 characters long, product titles in German, prices in the billions, empty lists, 500 errors, offline modes, right-to-left text. Designs that only work with perfect data are not production-ready. Reach for it before launch, before opening to a new market, or any time a bug report starts with "our user had a really long name and". @@ -25,7 +25,7 @@ For each dimension it identifies the failure mode, then applies the concrete fix Start with one page and one dimension: ``` -/harden the user profile page for long names +/impeccable harden the user profile page for long names ``` Expected output: @@ -40,6 +40,6 @@ Run it per-page, not all at once. The first run is the biggest; subsequent runs ## Pitfalls -- **Waiting for a bug report.** Harden is preventative. If you find yourself fixing the same class of bug twice, run `/harden` across the feature. +- **Waiting for a bug report.** Harden is preventative. If you find yourself fixing the same class of bug twice, run `/impeccable harden` across the feature. - **Treating error and empty states as an afterthought.** Most hardening work is error and empty state UI. Budget time for it, not just a `catch` block. - **Skipping i18n because "we are English-only for now".** i18n-safe layouts are still better layouts. Flexible containers, proper text wrapping, generous line-height. None of that hurts English. diff --git a/content/site/skills/impeccable.md b/content/site/skills/impeccable.md index c151883e2..94e97cbae 100644 --- a/content/site/skills/impeccable.md +++ b/content/site/skills/impeccable.md @@ -1,51 +1,39 @@ --- -tagline: "The design intelligence behind every other skill." +tagline: "The design intelligence behind every command." --- ## When to use it -`/impeccable` is the foundation. It teaches your AI harness how to design, period. Every other command in this pack leans on it for design principles, anti-patterns, typography, color, and layout guidance. +`/impeccable` is the home command. Call it directly when you want freeform design work with the full guidebook loaded, without having to pick a specialized command. It is the fallback you reach for when none of the 20 specialists (`audit`, `polish`, `critique`, and the rest) map cleanly onto what you're trying to do. -Call `/impeccable` directly when you want freeform design with the full guidebook loaded. Or use one of the two sub-modes: +Reach for `/impeccable` directly when: -### /impeccable craft {#craft} +- **You're not sure which command fits.** Describe what you want in plain English and let the skill pick the right approach. +- **The work spans multiple disciplines.** "Redo this hero section" touches layout, type, color, and motion. One command can't own that. +- **You want the full design intelligence without constraints.** Every reference file loaded, every anti-pattern checked, no pre-set workflow. -The full shape-then-build flow. It starts by running `/shape` internally (a structured discovery interview about purpose, audience, and goals), then moves into implementation with visual iteration, checking the result in the browser until the polish is high. Best for brand-new features where you want to think before you build, without managing the steps yourself. - -### /impeccable teach {#teach} - -One-time project setup. Runs a short discovery interview about your brand, audience, and aesthetic direction, then writes a `.impeccable.md` file that every future skill call reads automatically. Run this once per project before doing any design work. - -### /impeccable extract {#extract} - -Pull reusable components, design tokens, and patterns out of your code and into the design system. Finds repeated UI patterns (buttons in 12 places, three card variants, scattered hex colors), extracts them into shared primitives, and migrates all callers. Best used after a product has shipped enough features to reveal the patterns -- premature extraction creates abstractions that do not match reality. +For more structured flows, reach for the specialized commands in the sidebar. `/impeccable craft` runs the full shape-then-build pipeline, `/impeccable shape` produces a design brief before any code is written, and the evaluation and refinement commands (`audit`, `critique`, `polish`, `typeset`, etc.) each own a specific slice of the work. ## How it works Most AI-generated UIs fail the same way: generic fonts, purple gradients, card grids on card grids, glassmorphism everywhere. `/impeccable` gives your AI a strong point of view. It loads an opinionated design handbook plus a long list of anti-patterns, then pushes the model to commit to a specific aesthetic direction before writing a single line of code. -The skill has a **Context Gathering Protocol** built in. It will not design anything until it knows who uses the product, what they're trying to do, and how the interface should feel. If no context exists yet, it asks you to run `/impeccable teach` first. This is deliberate: design without context produces slop, and slop is the whole problem this pack exists to solve. +The skill has a **Context Gathering Protocol** built in. It will not design anything until it knows who uses the product, what they're trying to do, and how the interface should feel. On first use in a project, it runs the `teach` flow automatically: a short interview about your brand, audience, and aesthetic direction, saved to `.impeccable.md` so every future command reads it without asking again. ## Try it -From a clean project, run once: - ``` -/impeccable teach +/impeccable redo this hero section ``` -Answer the discovery questions. The skill writes a `.impeccable.md` file with your brand, audience, and aesthetic direction. Every future skill call reads it automatically. - -Then build something: - ``` /impeccable build me a pricing page for a developer tool ``` -You should get a page that commits to one clear aesthetic direction, uses non-default fonts, avoids the AI color palette, and has a real point of view. +Both prompts are vague on purpose. `/impeccable` will pick a strong aesthetic direction, commit to non-default fonts, avoid the AI color palette, and make the kind of specific choices that a designer would make. No command name to pick first, no step-by-step workflow to follow. ## Pitfalls -- **Skipping `/impeccable teach`.** Without a `.impeccable.md` file, the skill has to ask you context questions mid-flight. Faster to set it up once. - **Treating it like a style guide.** It is an opinionated design partner, not a linter. The defaults exist to raise the floor, not to overrule your judgment. If you have a real reason to push back (brand guideline, accessibility constraint, user research that says otherwise), push back and explain why. The skill will work with you. What produces worse output is ignoring the opinion without a reason. -- **Expecting it to fix existing code.** For that, reach for `/polish`, `/distill`, or `/critique` instead. `/impeccable` is for creation. +- **Expecting it to fix existing code.** `/impeccable` is for creation. For refinement, reach for `/impeccable polish`, `/impeccable distill`, or `/impeccable critique` instead. +- **Running it before `teach` has had a chance to save context.** On a fresh project it will interview you mid-flight, which is fine but slower. Running `/impeccable teach` explicitly as your very first command is a tiny bit smoother. diff --git a/content/site/skills/layout.md b/content/site/skills/layout.md index 8af09fa28..317f5ea39 100644 --- a/content/site/skills/layout.md +++ b/content/site/skills/layout.md @@ -4,7 +4,7 @@ tagline: "Fix layout, spacing, and visual rhythm." ## When to use it -`/layout` is for pages where nothing is technically wrong but nothing is breathing either. Equal padding everywhere, monotonous card grids, content that runs edge to edge, hierarchy that relies on size alone. Reach for it when a layout "feels off" and you cannot articulate why. +`/impeccable layout` is for pages where nothing is technically wrong but nothing is breathing either. Equal padding everywhere, monotonous card grids, content that runs edge to edge, hierarchy that relies on size alone. Reach for it when a layout "feels off" and you cannot articulate why. Good triggers: "everything feels crowded", "it reads like a wall", "I do not know where to look first". @@ -23,7 +23,7 @@ Fixes usually involve rebuilding the spacing scale, introducing asymmetry, colla ## Try it ``` -/layout the settings page +/impeccable layout the settings page ``` Typical changes: @@ -36,6 +36,6 @@ Typical changes: ## Pitfalls -- **Confusing arrange with distill.** If the problem is too many things, run `/distill` first. Layout is for arranging what is already the right set. +- **Confusing arrange with distill.** If the problem is too many things, run `/impeccable distill` first. Layout is for arranging what is already the right set. - **Expecting it to rescue a broken grid.** If the page has no grid at all, arrange will build one. Just know that the diff is going to be larger than you expect. - **Ignoring the hierarchy verdict.** If arrange says "nothing is primary", no amount of spacing work fixes that. You need a content decision, not a layout tweak. diff --git a/content/site/skills/optimize.md b/content/site/skills/optimize.md index 15b49905e..545d596c1 100644 --- a/content/site/skills/optimize.md +++ b/content/site/skills/optimize.md @@ -4,7 +4,7 @@ tagline: "Diagnose and fix UI performance from LCP to bundle size." ## When to use it -`/optimize` is for interfaces that feel slow. First paint takes forever, scrolling janks, images pop in late, interactions feel laggy, the bundle ships 800KB of JavaScript. Use it when the Web Vitals are bad or when users are complaining that things are sluggish. +`/impeccable optimize` is for interfaces that feel slow. First paint takes forever, scrolling janks, images pop in late, interactions feel laggy, the bundle ships 800KB of JavaScript. Use it when the Web Vitals are bad or when users are complaining that things are sluggish. Do not use it as premature optimization. If LCP is 1.1s and INP is 80ms, stop. The design work matters more. @@ -23,7 +23,7 @@ The skill measures before and after. Every fix gets quantified. If a change does ## Try it ``` -/optimize the homepage +/impeccable optimize the homepage ``` Expected shape: @@ -51,6 +51,6 @@ Bundle: 340KB → 180KB ## Pitfalls -- **Optimizing before measuring.** Without baseline metrics, you cannot tell what helped. Run `/optimize` with specific Web Vitals numbers, not vibes. +- **Optimizing before measuring.** Without baseline metrics, you cannot tell what helped. Run `/impeccable optimize` with specific Web Vitals numbers, not vibes. - **Chasing tiny wins.** A 20ms improvement in INP that takes a week is rarely worth it. Optimize has diminishing returns; know when to stop. - **Forgetting to re-measure after every change.** The build could have made things worse in a way the skill did not predict. Verify. diff --git a/content/site/skills/overdrive.md b/content/site/skills/overdrive.md index b01135358..61a2a26e8 100644 --- a/content/site/skills/overdrive.md +++ b/content/site/skills/overdrive.md @@ -4,7 +4,7 @@ tagline: "Push an interface past conventional limits. Shaders, physics, 60fps, c ## When to use it -`/overdrive` is for the moments where you want to impress. A hero that uses WebGL. A table that handles a million rows. A dialog that morphs out of its trigger element. A form that validates in real-time with streaming feedback. A page transition that feels cinematic. Use it when the project budget allows for technical ambition and the outcome needs to feel extraordinary. +`/impeccable overdrive` is for the moments where you want to impress. A hero that uses WebGL. A table that handles a million rows. A dialog that morphs out of its trigger element. A form that validates in real-time with streaming feedback. A page transition that feels cinematic. Use it when the project budget allows for technical ambition and the outcome needs to feel extraordinary. Do not use it on operator tools, dashboards, or anything where reliability beats spectacle. Overdrive burns complexity for effect, and that trade-off is only worth it on moments that matter. @@ -17,7 +17,7 @@ Overdrive output is announced with `──── ⚡ OVERDRIVE ────` so ## Try it ``` -/overdrive the landing hero +/impeccable overdrive the landing hero ``` One concrete run might replace a static hero with a WebGL shader background driven by mouse position, a display headline that reveals with a mask on scroll using the Scroll Timeline API, and a View Transition on the CTA that morphs into the next page. Plus a reduced-motion fallback that swaps all of it for a clean static composition. diff --git a/content/site/skills/polish.md b/content/site/skills/polish.md index 048957757..9c7a5f0e4 100644 --- a/content/site/skills/polish.md +++ b/content/site/skills/polish.md @@ -4,7 +4,7 @@ tagline: "The meticulous final pass between good and great." ## When to use it -`/polish` is the last thing you run before shipping. It hunts down the small details that separate a shipped feature from a polished one: half-pixel misalignments, inconsistent spacing, forgotten focus states, loading transitions that flash, copy that drifts in tone. It also aligns the feature with your design system -- replacing hard-coded values with tokens, swapping custom components for shared ones, and fixing any drift from established patterns. +`/impeccable polish` is the last thing you run before shipping. It hunts down the small details that separate a shipped feature from a polished one: half-pixel misalignments, inconsistent spacing, forgotten focus states, loading transitions that flash, copy that drifts in tone. It also aligns the feature with your design system, replacing hard-coded values with tokens, swapping custom components for shared ones, and fixing any drift from established patterns. Reach for it when the feature is functionally complete, nothing is broken, and something still feels off. Also reach for it when a feature has drifted from the design system and needs to be pulled back in line. @@ -24,7 +24,7 @@ The skill is explicit about one thing: polish is the last step, not the first. I ## Try it ``` -/polish the pricing page +/impeccable polish the pricing page ``` A healthy run looks like: @@ -41,6 +41,6 @@ Five small fixes, no rewrites. That is the shape of a good polish pass. ## Pitfalls -- **Polishing work that is not done.** If there are TODOs in the code, you are not ready. Run `/polish` on finished features only. -- **Treating polish as redesign.** Polish refines what exists. If you find yourself rearchitecting a layout, you needed `/critique` or `/layout` instead. -- **Running `/polish` without `/audit` first.** Polish catches feel-based issues. Audit catches measurable ones. Use both. +- **Polishing work that is not done.** If there are TODOs in the code, you are not ready. Run `/impeccable polish` on finished features only. +- **Treating polish as redesign.** Polish refines what exists. If you find yourself rearchitecting a layout, you needed `/impeccable critique` or `/impeccable layout` instead. +- **Running `/impeccable polish` without `/impeccable audit` first.** Polish catches feel-based issues. Audit catches measurable ones. Use both. diff --git a/content/site/skills/quieter.md b/content/site/skills/quieter.md index fedaa4d7c..e589df5c6 100644 --- a/content/site/skills/quieter.md +++ b/content/site/skills/quieter.md @@ -4,9 +4,9 @@ tagline: "Tone down designs that are shouting without losing their intent." ## When to use it -`/quieter` is the counterweight to `/bolder`. Reach for it when an interface is visually aggressive, overstimulating, or trying to do too many things at full volume. Neon on dark, gradient text everywhere, 6 accent colors, everything animated, 20px shadows. Use quieter when the design needs to breathe and you want refinement without losing the point of view. +`/impeccable quieter` is the counterweight to `/impeccable bolder`. Reach for it when an interface is visually aggressive, overstimulating, or trying to do too many things at full volume. Neon on dark, gradient text everywhere, 6 accent colors, everything animated, 20px shadows. Use quieter when the design needs to breathe and you want refinement without losing the point of view. -Also useful after `/bolder` goes a little too far. +Also useful after `/impeccable bolder` goes a little too far. ## How it works @@ -22,7 +22,7 @@ The skill preserves the design's intent. If the original had a point of view, th ## Try it ``` -/quieter the pricing page +/impeccable quieter the pricing page ``` Typical diff: @@ -37,4 +37,4 @@ Typical diff: - **Over-applying.** Quieter can strip personality if you run it on something that was already measured. Use it when the design is too loud, not when it is correctly assertive. - **Confusing quieter with distill.** Quieter reduces intensity. Distill removes elements. They are different moves. -- **Running it in response to a critique that says "too busy".** Busy usually means too many things, not too loud. Try `/distill` first. +- **Running it in response to a critique that says "too busy".** Busy usually means too many things, not too loud. Try `/impeccable distill` first. diff --git a/content/site/skills/shape.md b/content/site/skills/shape.md index e4a687d76..b593e30f5 100644 --- a/content/site/skills/shape.md +++ b/content/site/skills/shape.md @@ -4,13 +4,13 @@ tagline: "Think before you build. Produce a design brief through discovery, not ## When to use it -`/shape` is where a feature starts. Before anyone writes code, before anyone argues about the hero treatment, before anyone picks a font. Use it to force a discovery conversation about purpose, users, content, and constraints, then capture the answers as a design brief the implementation skills can lean on. +`/impeccable shape` is where a feature starts. Before anyone writes code, before anyone argues about the hero treatment, before anyone picks a font. Use it to force a discovery conversation about purpose, users, content, and constraints, then capture the answers as a design brief the implementation skills can lean on. Reach for it whenever a feature is about to start, a ticket is vague, or you catch yourself writing JSX to figure out what the product should be. ## How it works -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. The model jumps to "here is a card grid" without asking "what is the user trying to accomplish". `/shape` inverts that order. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. The model jumps to "here is a card grid" without asking "what is the user trying to accomplish". `/impeccable shape` inverts that order. The skill runs a structured discovery interview in conversation. It will not write code during this phase. The questions cover: @@ -21,17 +21,17 @@ The skill runs a structured discovery interview in conversation. It will not wri You answer naturally. The skill asks follow-ups, not a form. At the end it produces a design brief: a structured artifact you can hand to `/impeccable` or any other implementation skill. -Note: if you want the full flow -- discovery interview, then straight into building -- use `/impeccable craft` instead. It runs `/shape` internally, then continues into implementation with visual iteration. `/shape` standalone is for when you want just the brief, so you can take it to whatever implementation approach you prefer. +Note: if you want the full flow (discovery interview, then straight into building), use `/impeccable craft` instead. It runs `/impeccable shape` internally, then continues into implementation with visual iteration. `/impeccable shape` standalone is for when you want just the brief, so you can take it to whatever implementation approach you prefer. ## Try it ``` -/shape a daily digest email preferences page +/impeccable shape a daily digest email preferences page ``` Expect a 5 to 10 question conversation. The skill asks things like "who is the person opening this, and are they already committed or still curious" and "what happens when the user has unsubscribed from everything, do we hide the feature or show something". You answer, and a brief materializes. -From there you can hand the brief to `/impeccable`, `/polish`, or any other skill. Or just use it as a reference while you build by hand. +From there you can hand the brief to `/impeccable`, `/impeccable polish`, or any other skill. Or just use it as a reference while you build by hand. ## Pitfalls diff --git a/content/site/skills/teach.md b/content/site/skills/teach.md new file mode 100644 index 000000000..698fd7894 --- /dev/null +++ b/content/site/skills/teach.md @@ -0,0 +1,3 @@ +--- +tagline: "Teach Impeccable who your product is for, once per project." +--- diff --git a/content/site/skills/typeset.md b/content/site/skills/typeset.md index feb656821..0bfc1aad8 100644 --- a/content/site/skills/typeset.md +++ b/content/site/skills/typeset.md @@ -4,7 +4,7 @@ tagline: "Fix typography that feels generic, inconsistent, or accidental." ## When to use it -Reach for `/typeset` when the text on a page looks like default typography instead of designed typography. Muddy hierarchy, three sizes that look the same, body copy at 14px, a display font that is actually just Inter bold, headlines with no kerning attention. +Reach for `/impeccable typeset` when the text on a page looks like default typography instead of designed typography. Muddy hierarchy, three sizes that look the same, body copy at 14px, a display font that is actually just Inter bold, headlines with no kerning attention. Common triggers: "hierarchy feels flat", "readability is off", "fonts look generic". @@ -23,7 +23,7 @@ It then fixes what it finds: picks distinctive typefaces, builds a modular scale ## Try it ``` -/typeset the article layout +/impeccable typeset the article layout ``` Expected diff: @@ -38,5 +38,5 @@ Expected diff: ## Pitfalls - **Asking for a new font without context.** Typeset will pick based on the `.impeccable.md` brand voice. If you have not run `/impeccable teach`, the suggestion will be generic. -- **Reaching for typeset when the issue is layout.** If paragraphs are fine but the page feels cramped, you want `/layout`. +- **Reaching for typeset when the issue is layout.** If paragraphs are fine but the page feels cramped, you want `/impeccable layout`. - **Expecting fluid clamp scales on app UIs.** Typeset uses fixed rem scales for app interfaces. Fluid typography is for marketing and content pages where line length varies dramatically. diff --git a/content/site/tutorials/critique-with-overlay.md b/content/site/tutorials/critique-with-overlay.md index 5ba0a1b98..e370d14ca 100644 --- a/content/site/tutorials/critique-with-overlay.md +++ b/content/site/tutorials/critique-with-overlay.md @@ -1,6 +1,6 @@ --- title: Critique with the visual overlay -tagline: "Use /critique plus the browser overlay to review a live page with ground truth." +tagline: "Use /impeccable critique plus the browser overlay to review a live page with ground truth." order: 2 description: "Run a full design critique that combines LLM assessment, the automated detector, and a live browser overlay so you can see exactly which elements trigger which anti-patterns on the page you're looking at." --- @@ -17,12 +17,12 @@ Total time: about ten minutes. - A harness with browser automation available (Claude Code with the Chrome extension, or similar). - A page you want to critique, either local (`localhost:3000/pricing`) or deployed. -## Step 1. Run /critique +## Step 1. Run /impeccable critique From your harness, run: ``` -/critique the pricing page at localhost:3000/pricing +/impeccable critique the pricing page at localhost:3000/pricing ``` The skill kicks off two independent assessments in parallel. They run in separate sub-agents so one does not bias the other. @@ -58,14 +58,14 @@ Every outlined element has a floating label naming the rule that fired. Hover an You have three ways to open it: 1. **[Chrome extension](https://chromewebstore.google.com/detail/impeccable/bdkgmiklpdmaojlpflclinlofgjfpabf)**: one-click activation on any page. Click the Impeccable icon in the toolbar and every anti-pattern gets highlighted instantly. -2. **Inside `/critique`**: the skill opens a browser tab labeled `[Human]` with the detector active during the browser portion of the assessment. You do not need to do anything extra. +2. **Inside `/impeccable critique`**: the skill opens a browser tab labeled `[Human]` with the detector active during the browser portion of the assessment. You do not need to do anything extra. 3. **Standalone CLI**: `npx impeccable live` starts a local server that serves the detector script. You inject it into any page by adding a ` - - - - - Impeccable Command Cheatsheet - - - - - - - - - - -
- - - Impeccable - -
- - - - 18k - - -
-
- -
-

Impeccable Commands

-

Quick reference for all 18 design commands

-
- -
-

Loading commands...

-
- - - - - - diff --git a/public/css/main.css b/public/css/main.css index 0cacbeca6..d2c15a660 100644 --- a/public/css/main.css +++ b/public/css/main.css @@ -1666,6 +1666,11 @@ code { margin: 0 0 var(--spacing-xs) 0; } +.mobile-cmd-namespace { + color: var(--color-ash); + font-weight: 400; +} + .mobile-cmd-desc { font-size: 0.875rem; color: var(--color-charcoal); @@ -2741,7 +2746,7 @@ code { /* Row 1: full-width primary install card with internal 2-column split */ .install-row-primary { display: grid; - grid-template-columns: 1.1fr 0.9fr; + grid-template-columns: 1fr 1fr; gap: var(--spacing-xl); align-items: start; margin: 0 0 var(--spacing-xl); @@ -2751,19 +2756,221 @@ code { min-width: 0; } -.install-primary-main { +.install-primary-main, +.install-primary-howto { display: flex; flex-direction: column; min-width: 0; } +.install-primary-howto { + padding-left: var(--spacing-xl); + border-left: 1px solid var(--color-mist); +} + +/* The "Use it" side uses the hero body copy size so both columns feel balanced + in typographic weight, not just pixel width. */ +.install-primary-howto .install-path-desc { + font-size: 0.9375rem; + line-height: 1.6; + color: var(--color-ink); + max-width: 48ch; +} + +.install-primary-howto .install-path-desc em { + font-family: var(--font-display); + font-style: italic; + font-weight: 500; + color: var(--color-accent); +} + .install-primary-alts { display: flex; flex-direction: column; gap: var(--spacing-lg); min-width: 0; - padding-left: var(--spacing-xl); - border-left: 1px solid var(--color-mist); +} + +/* Collapsible "other install methods" under the main install card. */ +.install-alts-collapse { + margin-top: var(--spacing-md); + border-top: 1px solid var(--color-mist); + padding-top: var(--spacing-md); +} + +.install-alts-collapse[open] { + padding-bottom: var(--spacing-sm); +} + +.install-alts-summary { + display: flex; + align-items: center; + justify-content: space-between; + gap: var(--spacing-sm); + cursor: pointer; + list-style: none; + padding: 0.25rem 0; + user-select: none; +} + +.install-alts-summary::-webkit-details-marker { + display: none; +} + +.install-alts-summary-label { + font-family: var(--font-body); + font-size: 0.6875rem; + font-weight: 600; + text-transform: uppercase; + letter-spacing: 0.08em; + color: var(--color-ash); +} + +.install-alts-chevron { + color: var(--color-ash); + transition: transform 0.2s ease; + flex-shrink: 0; +} + +.install-alts-collapse[open] .install-alts-chevron { + transform: rotate(180deg); +} + +.install-alts-collapse[open] .install-primary-alts { + margin-top: var(--spacing-md); +} + +/* Editorial "How to use" step list on the right side of the install row. + Uses display-font numerals as prominent visual anchors, generous vertical + rhythm, and body text at the same scale as the hero copy for hierarchy + parity with the rest of the page. */ +.install-howto-steps { + list-style: none; + counter-reset: howto-step; + padding: 0; + margin: var(--spacing-lg) 0 0; + display: flex; + flex-direction: column; + gap: var(--spacing-lg); +} + +.install-howto-steps > li { + counter-increment: howto-step; + position: relative; + padding-left: 3rem; + min-height: 2.5rem; +} + +.install-howto-steps > li::before { + content: counter(howto-step, decimal-leading-zero); + position: absolute; + left: 0; + top: -0.1em; + font-family: var(--font-display); + font-size: 1.75rem; + font-weight: 400; + font-style: italic; + color: var(--color-accent); + line-height: 1; + letter-spacing: -0.02em; +} + +.install-howto-step-label { + font-family: var(--font-body); + font-size: 1rem; + font-weight: 600; + color: var(--color-ink); + margin-bottom: 0.35rem; + line-height: 1.3; + letter-spacing: -0.005em; +} + +.install-howto-steps > li p { + margin: 0; + font-size: 0.9375rem; + color: var(--color-ink); + line-height: 1.6; +} + +.install-howto-steps code { + font-family: var(--font-mono); + font-size: 0.8125rem; + font-weight: 500; + color: var(--color-ink); + background: var(--color-accent-dim); + padding: 1px 6px; + border-radius: 3px; + white-space: nowrap; +} + +.install-howto-steps .install-path-slash { + color: var(--color-accent); +} + +.install-howto-footer { + display: flex; + flex-wrap: wrap; + gap: var(--spacing-lg); + margin-top: var(--spacing-xl); + padding-top: var(--spacing-lg); + border-top: 1px solid var(--color-mist); +} + +.install-howto-link { + font-family: var(--font-body); + font-size: 0.875rem; + font-weight: 500; + color: var(--color-accent); + text-decoration: none; + display: inline-flex; + align-items: baseline; + gap: 0.35em; + transition: gap 0.2s var(--ease-out-quart, ease); +} + +.install-howto-link:hover { + gap: 0.6em; +} + +.install-howto-link span { + display: inline-block; + transition: transform 0.2s var(--ease-out-quart, ease); +} + +.install-howto-link:hover span { + transform: translateX(2px); +} + +/* Two-tool grid inside the "Anti-pattern tools" step. */ +.install-tool-grid { + display: grid; + grid-template-columns: 1fr 1fr; + gap: var(--spacing-lg); + margin-top: var(--spacing-md); +} + +.install-tool { + display: flex; + flex-direction: column; + gap: var(--spacing-sm); + min-width: 0; +} + +.install-tool-label { + font-family: var(--font-body); + font-size: 0.9375rem; + font-weight: 600; + color: var(--color-ink); + display: flex; + align-items: center; + gap: 0.4rem; +} + +.install-tool-desc { + margin: 0; + font-size: 0.8125rem; + color: var(--color-charcoal); + line-height: 1.55; } .install-alts-label { @@ -3025,6 +3232,7 @@ code { color: var(--color-accent); } + .install-path-subcommands { display: flex; flex-direction: column; @@ -3311,13 +3519,17 @@ a.install-updated-ref:hover { max-width: calc(100vw - var(--spacing-md) * 2); } - .install-primary-alts { + .install-primary-howto { padding-left: 0; padding-top: var(--spacing-lg); border-left: none; border-top: 1px solid var(--color-mist); } + .install-tool-grid { + grid-template-columns: 1fr; + } + .install-path-primary { margin-bottom: var(--spacing-sm); padding: var(--spacing-md); diff --git a/public/css/sub-pages.css b/public/css/sub-pages.css index 716b13307..c4be084bd 100644 --- a/public/css/sub-pages.css +++ b/public/css/sub-pages.css @@ -486,138 +486,283 @@ main#main { padding: clamp(2rem, 4vw, 3.5rem) 0 clamp(4rem, 8vw, 6rem); } -.skills-overview-content { - max-width: 720px; +/* ============================================ + DOCS OVERVIEW — /skills page + ============================================ */ + +.docs-overview { + max-width: 920px; } -.skills-overview-header { - margin-bottom: clamp(2.5rem, 5vw, 4rem); +.docs-overview-header { + margin-bottom: clamp(2rem, 4vw, 3rem); } -.skills-overview-header .sub-page-lede a { - color: var(--color-ink); - text-decoration: underline; - text-decoration-thickness: 1px; - text-decoration-color: var(--color-accent); - text-underline-offset: 4px; - font-family: var(--font-mono); - font-weight: 500; -} - -.skills-overview-howto { - padding: var(--spacing-lg) var(--spacing-lg); - background: var(--color-cream); - border: 1px solid var(--color-mist); - border-radius: 10px; - margin-bottom: clamp(2.5rem, 5vw, 4rem); -} - -.skills-overview-howto-title { - font-family: var(--font-display); - font-size: 1.25rem; - font-style: italic; - font-weight: 500; - color: var(--color-ink); - margin-bottom: var(--spacing-sm); -} - -.skills-overview-howto p { - font-size: 0.9375rem; - line-height: 1.7; - color: var(--color-charcoal); +.docs-overview-header .sub-page-lede { max-width: 60ch; } -.skills-overview-howto a { - color: var(--color-ink); - font-family: var(--font-mono); - font-size: 0.875em; - font-weight: 500; - text-decoration: none; - border-bottom: 1px solid var(--color-accent); - transition: color var(--duration-fast) var(--ease-out); +/* Home command hero — the /impeccable root card that sits above the + category sections. It gets special treatment because it's the entry + point, not just another command in a category. */ +.docs-home-card { + display: grid; + grid-template-columns: 1.1fr 1fr; + gap: clamp(1.5rem, 3vw, 2.5rem); + padding: clamp(1.5rem, 3vw, 2rem); + background: #ffffff; + border: 1px solid var(--color-mist); + border-radius: 12px; + margin-bottom: clamp(2.5rem, 5vw, 3.5rem); } -.skills-overview-howto a:hover { +.docs-home-card-identity { + min-width: 0; +} + +.docs-home-card-eyebrow { + display: inline-block; + font-family: var(--font-body); + font-size: 0.6875rem; + font-weight: 600; + text-transform: uppercase; + letter-spacing: 0.12em; color: var(--color-accent); + margin-bottom: var(--spacing-sm); } -.skills-overview-categories { +.docs-home-card-title { + font-family: var(--font-display); + font-size: clamp(2rem, 4vw, 2.75rem); + font-weight: 500; + font-style: italic; + color: var(--color-ink); + letter-spacing: -0.02em; + line-height: 1; + margin: 0 0 var(--spacing-sm) 0; +} + +.docs-home-card-tagline { + font-family: var(--font-body); + font-size: 1rem; + font-weight: 500; + color: var(--color-ink); + line-height: 1.5; + margin: 0 0 var(--spacing-md) 0; + max-width: 32ch; +} + +.docs-home-card-desc { + font-size: 0.9375rem; + line-height: 1.6; + color: var(--color-ink); + max-width: 36ch; + margin: 0; +} + +.docs-home-card-desc code { + font-family: var(--font-mono); + font-size: 0.8125rem; + font-weight: 500; + color: var(--color-ink); + background: var(--color-accent-dim); + padding: 1px 6px; + border-radius: 3px; +} + +.docs-home-card-modes { + list-style: none; + padding: 0; + margin: 0; display: flex; flex-direction: column; - gap: clamp(2rem, 4vw, 3rem); + gap: var(--spacing-md); } -.skills-overview-category { - padding-bottom: clamp(2rem, 4vw, 2.5rem); - border-bottom: 1px solid var(--color-mist); +.docs-home-card-modes a { + display: block; + text-decoration: none; + transition: padding var(--duration-fast) var(--ease-out, ease); } -.skills-overview-category:last-child { - border-bottom: none; +.docs-home-card-modes a:hover { + padding-left: 6px; } -.skills-overview-category-meta { +.docs-home-mode-label { + display: block; + font-family: var(--font-mono); + font-size: 0.875rem; + font-weight: 600; + color: var(--color-ink); + margin-bottom: 2px; +} + +.docs-home-mode-slash { + color: var(--color-accent); + font-weight: 400; +} + +.docs-home-mode-hint { + display: block; + font-family: var(--font-body); + font-size: 0.8125rem; + color: var(--color-charcoal); + line-height: 1.4; +} + +/* Category sections with rich command cards */ +.docs-categories { + display: flex; + flex-direction: column; + gap: clamp(2.5rem, 5vw, 3.5rem); +} + +.docs-category-header { display: flex; align-items: baseline; justify-content: space-between; gap: var(--spacing-md); - margin-bottom: 6px; + margin-bottom: var(--spacing-md); + padding-bottom: var(--spacing-sm); + border-bottom: 1px solid var(--color-mist); } -.skills-overview-category-title { +.docs-category-title { font-family: var(--font-display); font-size: clamp(1.5rem, 3vw, 2rem); font-weight: 500; font-style: italic; color: var(--color-ink); letter-spacing: -0.01em; + line-height: 1.1; + margin: 0 0 4px 0; } -.skills-overview-category-count { +.docs-category-desc { + font-size: 0.875rem; + line-height: 1.5; + color: var(--color-charcoal); + max-width: 58ch; + margin: 0; +} + +.docs-category-count { font-family: var(--font-mono); font-size: 0.6875rem; font-weight: 600; text-transform: uppercase; letter-spacing: 0.12em; color: var(--color-ash); + white-space: nowrap; + flex-shrink: 0; } -.skills-overview-category-desc { - font-size: 0.9375rem; - line-height: 1.7; - color: var(--color-charcoal); - max-width: 58ch; - margin-bottom: var(--spacing-md); -} - -.skills-overview-chips { +/* Dense two-column rows for each command: name on the left, description + + relationship on the right. Mirrors the original cheatsheet density. */ +.docs-category-rows { display: flex; - flex-wrap: wrap; - gap: 8px; + flex-direction: column; } -.skills-overview-chip { - display: inline-flex; - align-items: center; - padding: 6px 12px; +.command-row { + display: grid; + grid-template-columns: minmax(11rem, 13rem) 1fr; + gap: var(--spacing-lg); + padding: var(--spacing-md) 0; + border-bottom: 1px solid var(--color-mist); + align-items: baseline; +} + +.command-row:last-child { + border-bottom: none; +} + +.command-row-name { font-family: var(--font-mono); - font-size: 0.8125rem; - font-weight: 500; + font-size: 0.875rem; + font-weight: 600; color: var(--color-ink); - background: var(--color-paper); - border: 1px solid var(--color-mist); - border-radius: 99px; - text-decoration: none; - transition: border-color var(--duration-fast) var(--ease-out), - color var(--duration-fast) var(--ease-out), - background var(--duration-fast) var(--ease-out); + line-height: 1.4; + min-width: 0; } -.skills-overview-chip:hover { +.command-row-name a { + color: inherit; + text-decoration: none; + border-bottom: 1px solid transparent; + transition: border-color var(--duration-fast) var(--ease-out, ease); +} + +.command-row-name a:hover { + border-bottom-color: var(--color-accent); +} + +.command-row-namespace { + color: var(--color-ash); + font-weight: 400; +} + +.command-row-beta { + display: inline-block; + font-family: var(--font-mono); + font-size: 0.5625rem; + font-weight: 600; + letter-spacing: 0.08em; + text-transform: uppercase; + color: var(--color-accent); + border: 1px solid var(--color-accent); + border-radius: 3px; + padding: 1px 5px; + vertical-align: 1px; + margin-left: 4px; +} + +.command-row-info { + min-width: 0; +} + +.command-row-desc { + font-family: var(--font-body); + font-size: 0.875rem; + line-height: 1.55; + color: var(--color-ink); + margin: 0; +} + +.command-row-rel { + font-family: var(--font-body); + font-size: 0.75rem; + line-height: 1.5; + color: var(--color-ash); + margin-top: 4px; +} + +.command-row-rel a { + font-family: var(--font-mono); + font-size: 0.75rem; + color: var(--color-charcoal); + text-decoration: none; + border-bottom: 1px solid var(--color-mist); + transition: color var(--duration-fast) var(--ease-out, ease), + border-color var(--duration-fast) var(--ease-out, ease); +} + +.command-row-rel a:hover { color: var(--color-accent); border-color: var(--color-accent); - background: var(--color-cream); +} + +/* Narrow viewport: stack name above info */ +@media (max-width: 820px) { + .docs-home-card { + grid-template-columns: 1fr; + } + + .command-row { + grid-template-columns: 1fr; + gap: 4px; + } } /* ============================================ @@ -1686,6 +1831,24 @@ main#main { font-weight: 300; } +/* Sub-commands: show "/impeccable" as a smaller label above the command name + so it stacks and the command name stays at full display size. */ +.skill-detail-title-namespace { + display: block; + font-family: var(--font-body); + font-size: 0.9375rem; + font-weight: 500; + color: var(--color-ash); + letter-spacing: 0.04em; + margin-bottom: 0.4em; + line-height: 1; +} + +.skill-detail-title-namespace .skill-detail-title-slash { + color: var(--color-accent); + font-weight: 400; +} + .skill-detail-tagline { font-family: var(--font-body); font-size: clamp(1rem, 1.4vw, 1.125rem); diff --git a/public/css/workflow.css b/public/css/workflow.css index 8dfa984dd..e0321b625 100644 --- a/public/css/workflow.css +++ b/public/css/workflow.css @@ -181,6 +181,24 @@ font-weight: 300; } +/* Sub-commands: stack the /impeccable namespace as a smaller label above the + command name so the command name stays at full display size and never + clips (e.g., "overdrive" is long). */ +.spread-command-name .spread-namespace { + display: block; + font-family: var(--font-body); + font-size: 0.875rem; + font-weight: 500; + color: var(--color-ash); + letter-spacing: 0.04em; + margin-bottom: 0.4em; +} + +.spread-command-name .spread-namespace .spread-slash { + color: var(--spread-accent); + font-weight: 400; +} + .spread-command-name .beta-badge { font-family: var(--font-body); font-size: 0.55rem; diff --git a/public/index.html b/public/index.html index bc9012563..387083c39 100644 --- a/public/index.html +++ b/public/index.html @@ -13,7 +13,7 @@ Impeccable: The missing upgrade to Anthropic's impeccable skill - + @@ -21,7 +21,7 @@ - + @@ -29,7 +29,7 @@ - + @@ -57,7 +57,7 @@
@@ -88,15 +88,15 @@

Impeccable

Design fluency for AI harnesses

-

Great design prompts require design vocabulary. Most people don't have it. Impeccable teaches your AI deep design knowledge and gives you 18 commands to steer the result.

-

Impeccable teaches your AI real design and gives you 18 commands to steer the result.

+

Great design prompts require design vocabulary. Most people don't have it. Impeccable teaches your AI deep design knowledge and gives you 20 commands to steer the result.

+

Impeccable teaches your AI real design and gives you 20 commands to steer the result.

What's included
- Enhanced impeccable skill + anti-patterns + Impeccable agent skill with 20 design commands · - 18 design commands: /polish, /audit, /typeset, /overdrive... + Optional CLI + Chrome extension
@@ -117,7 +117,7 @@
-

v2.1: Streamlined from 21 to 18 commands

+

v2.2: 1 skill, 20 commands

@@ -203,7 +203,7 @@

The Language

-

18 commands form a shared vocabulary between you and your AI. Each one encodes a specific design discipline, so you can steer with precision.

+

20 commands form a shared vocabulary between you and your AI. Each one encodes a specific design discipline, so you can steer with precision.

@@ -213,7 +213,7 @@
-

Pick any command to see it in action. View cheatsheet →

+

Pick any command to see it in action. Full command reference →

@@ -305,7 +305,7 @@
Three ways to use it -

The Chrome extension on any site, embedded in /critique during an AI design review, or standalone via npx impeccable live.

+

The Chrome extension on any site, embedded in /impeccable critique during an AI design review, or standalone via npx impeccable live.

Impeccable Chrome extension panel listing detected anti-patterns @@ -327,11 +327,12 @@

Get Started

- +
+
-

1Install the skills Recommended

-

18 commands that steer your AI toward better design, in real time. The full Impeccable experience.

+

1Install the skill Recommended

+

One agent skill that teaches your AI to design, with 20 commands bundled inside.

@@ -358,90 +359,115 @@
-
- Then run /impeccable teach to set up your project's design context. -
+ +
+ + Other install methods + + +
+
+ Claude Code plugin +
+ $ + /plugin marketplace add pbakaus/impeccable + +
+ Then open /plugin in Claude Code +
+ +
+ Manual download all 11 providers +
+ + +
+
+
+
- -
- Other install methods + +
+

2Use it

+

Impeccable gives you a shared design vocabulary with your AI. 20 commands (polish, audit, critique, typeset, and more) that each encode a specific design discipline, so you can steer with precision.

-
- Claude Code plugin -
- $ - /plugin marketplace add pbakaus/impeccable - -
- Then open /plugin in Claude Code -
+
    +
  1. +
    Let it think for you
    +

    Say /impeccable redo this hero section and let the skill pick the right approach. No command names to memorize.

    +
    2. +
  2. +
    Or steer directly
    +

    Type /impeccable alone to see the full vocabulary, or reach for a command by name: /impeccable audit checkout, /impeccable polish pricing, /impeccable critique onboarding.

    +
    3. +
  3. +
    Pin your favorites
    +

    Use one all the time? /impeccable pin audit gives you /audit as a standalone shortcut.

    +
    4. +
-
- Manual download all 11 providers -
- - -
+
+ Full walkthrough + Browse the vocabulary
- +
- +
-

2Add the CLI Beta

+

3Add the anti-pattern tools Optional
-

Scan any file, directory, or live URL for anti-patterns from the terminal. Catches gradient text, AI color palettes, nested cards, low contrast, and 20+ more rules across HTML, CSS, JSX/TSX, Vue, and Svelte. Use it in CI pipelines, pre-commit hooks, or one-off audits to keep AI slop out of production.

+

Two ways to catch AI slop outside the skill: a CLI for the terminal and a Chrome extension for any webpage. Both catch gradient text, AI color palettes, nested cards, low contrast, and 20+ more rules.

-
-
- $ - npm i -g impeccable - +
+
+
CLI Beta
+

Scan files, directories, or live URLs from the terminal. Drop into CI pipelines, pre-commit hooks, or one-off audits.

+
+
+ $ + npm i -g impeccable + +
+ Or use npx impeccable detect src/ without installing. +
+

Full command reference on npm →

+
+ +
+
Chrome extension
+

Click the toolbar icon on any page and every anti-pattern lights up right where it lives. Works on localhost, staging, production, or anyone else's site.

+

Install from Chrome Web Store →

- Or use npx impeccable detect src/ directly without installing.
- -

Full command reference on npm →

-
-
- - -
- -

3Browser extension

- - -
-

Click the toolbar icon on any page and every anti-pattern lights up right where it lives: gradient text, purple palettes, nested cards, tiny body text, and the rest. Works on your localhost, staging, production, or anyone else's site. Great for spot-checking competitors, reviewing PRs visually, or just browsing the web with a sharper eye.

-

Install from Chrome Web Store →

@@ -515,7 +541,7 @@
  • Chrome DevTools extension. One-click detection on any page: yours, staging, production, or someone else's. Reads live computed styles, surfaces findings in an interactive panel, and highlights elements on the page. In Chrome Web Store review.
  • /critique got teeth. Persona sub-agents review in parallel, score against Nielsen's heuristics, run the detector automatically, and open a live browser overlay so you can walk each finding in place.
  • New ways to create with Impeccable. /shape runs a structured discovery interview about purpose, audience, and goals, then produces a design brief before any code is written. /impeccable craft chains that brief straight into the full implementation flow so you ship a designed feature instead of a reflex card grid.
    • -
  • New docs site. Top-level Docs, Anti-Patterns, and Visual Mode sections. 18 per-skill pages with before/after demos and the canonical SKILL.md inline, two tutorials, and 38 rule cards with inline visual examples.
    • +
  • New docs site. Top-level Docs, Anti-Patterns, and Visual Mode sections. 18 per-skill pages with before/after demos and the canonical SKILL.md inline, two tutorials, and 38 rule cards with inline visual examples.
  • New harness: Rovo Dev. 11 supported AI tools total.
    • @@ -649,7 +675,7 @@
    Commands or skills aren't appearing. What do I do?
    -

    For commands: Type / in your AI harness and look for commands like /audit, /polish, etc. If they don't appear, double-check the files are in the correct location.

    +

    For commands: Type /impeccable in your AI harness and look for commands like /impeccable audit, /impeccable polish, etc. If they don't appear, double-check the files are in the correct location.

    For skills: Skills are applied automatically when relevant. To verify, explicitly mention "use the impeccable skill" in your prompt. This forces the AI to acknowledge and apply it.

    Tool-specific setup:

      @@ -706,10 +732,10 @@
      diff --git a/public/js/components/framework-viz.js b/public/js/components/framework-viz.js index 133eec4dd..d74881b96 100644 --- a/public/js/components/framework-viz.js +++ b/public/js/components/framework-viz.js @@ -25,10 +25,9 @@ const categoryLabels = { }; const commandSymbols = { - 'shape': 'Sh', - 'impeccable craft': 'Ic', 'impeccable': 'Im', - 'overdrive': 'Od', + 'craft': 'Cf', + 'shape': 'Sh', 'critique': 'Cr', 'audit': 'Au', 'typeset': 'Ty', @@ -38,33 +37,32 @@ const commandSymbols = { 'delight': 'De', 'bolder': 'Bo', 'quieter': 'Qu', + 'overdrive': 'Od', 'distill': 'Di', 'clarify': 'Cl', 'adapt': 'Ad', 'polish': 'Po', 'optimize': 'Op', 'harden': 'Ha', - 'impeccable teach': 'It', - 'impeccable extract': 'Ie' + 'teach': 'Te', + 'extract': 'Ex' }; const commandNumbers = { - 'shape': 0, - 'impeccable craft': 1, 'impeccable': 2, 'overdrive': 3, + 'impeccable': 1, 'craft': 2, 'shape': 3, 'critique': 4, 'audit': 5, 'typeset': 6, 'layout': 7, 'colorize': 8, 'animate': 9, - 'delight': 10, 'bolder': 11, 'quieter': 12, - 'distill': 13, 'clarify': 14, 'adapt': 15, - 'polish': 16, 'optimize': 17, 'harden': 18, - 'impeccable teach': 19, 'impeccable extract': 20 + 'delight': 10, 'bolder': 11, 'quieter': 12, 'overdrive': 13, + 'distill': 14, 'clarify': 15, 'adapt': 16, + 'polish': 17, 'optimize': 18, 'harden': 19, + 'teach': 20, 'extract': 21 }; -// Map sub-commands to their display label and scroll target -const commandDisplay = { - 'impeccable craft': { label: '/impeccable craft', scrollTo: 'impeccable' }, - 'impeccable teach': { label: '/impeccable teach', scrollTo: 'impeccable' }, - 'impeccable extract': { label: '/impeccable extract', scrollTo: 'impeccable' }, -}; +// After the v3.0 consolidation, all commands except the root "impeccable" are +// sub-commands of /impeccable. The renderer handles the display label directly +// (bare name for sub-commands, "/impeccable" for the root). This map is kept +// as an extension point for any future per-command display overrides. +const commandDisplay = {}; export class PeriodicTable { constructor(container) { @@ -130,11 +128,12 @@ export class PeriodicTable { const leadsTo = toArray(rel.leadsTo); const combinesWith = toArray(rel.combinesWith); - // Build relationships line + // Build relationships line. Command names are shown bare (no slash) + // because they're names, not invocations — the invocation is /impeccable . let relParts = []; - if (pairs.length > 0) relParts.push(`pairs with ${pairs.map(p => '/' + p).join(', ')}`); - if (combinesWith.length > 0) relParts.push(`+ ${combinesWith.map(p => '/' + p).join(', ')}`); - if (leadsTo.length > 0) relParts.push(`then ${leadsTo.map(p => '/' + p).join(', ')}`); + if (pairs.length > 0) relParts.push(`pairs with ${pairs.join(', ')}`); + if (combinesWith.length > 0) relParts.push(`+ ${combinesWith.join(', ')}`); + if (leadsTo.length > 0) relParts.push(`then ${leadsTo.join(', ')}`); // Strip category prefix from flow for cleaner display const flow = (rel.flow || '').replace(/^[^:]+:\s*/, ''); @@ -222,7 +221,13 @@ export class PeriodicTable { const el = document.createElement('button'); el.type = 'button'; - el.setAttribute('aria-label', `/${cmd} command - ${categoryLabels[category]}`); + // Build accessible label with the full invocation + const invocation = cmd === 'impeccable' + ? '/impeccable' + : cmd.startsWith('impeccable ') + ? `/${cmd}` + : `/impeccable ${cmd}`; + el.setAttribute('aria-label', `${invocation} command - ${categoryLabels[category]}`); el.style.cssText = ` width: 56px; height: 64px; @@ -266,20 +271,28 @@ export class PeriodicTable { symbol.textContent = commandSymbols[cmd]; el.appendChild(symbol); - // Command name + // Command name. The root "impeccable" is shown with its slash as the + // entry point. All other commands are sub-commands and show their + // bare name (the invocation is /impeccable ). const name = document.createElement('div'); name.style.cssText = ` font-family: var(--font-mono); - font-size: ${display ? '6.5px' : '8px'}; + font-size: 8px; color: ${colors.text}; opacity: 0.7; margin-top: 3px; text-align: center; max-width: 52px; line-height: 1.3; - ${display ? '' : 'white-space: nowrap;'} + white-space: nowrap; `; - name.textContent = display ? display.label : `/${cmd}`; + if (cmd === 'impeccable') { + name.textContent = '/impeccable'; + } else if (display) { + name.textContent = display.label; + } else { + name.textContent = cmd; + } el.appendChild(name); // Beta badge diff --git a/public/js/components/glass-terminal.js b/public/js/components/glass-terminal.js index 543ca1a16..cd1673482 100644 --- a/public/js/components/glass-terminal.js +++ b/public/js/components/glass-terminal.js @@ -71,8 +71,10 @@ function renderDesktopLayout(container, commands) { let startIndex = -1; - // Filter out deprecated shims and sub-commands (no standalone demos) - const deprecated = new Set(['teach-impeccable', 'frontend-design', 'arrange', 'normalize', 'onboard', 'extract', 'impeccable craft', 'impeccable teach', 'impeccable extract']); + // Filter out deprecated shims. craft, teach, extract used to be filtered + // too (when they were rendered as 'impeccable craft' etc.) but are now + // first-class sub-commands that should appear in the gallery. + const deprecated = new Set(['teach-impeccable', 'frontend-design', 'arrange', 'normalize', 'onboard', 'impeccable craft', 'impeccable teach', 'impeccable extract']); const filteredCommands = commands.filter(c => !deprecated.has(c.id)); const categoryOrder = ['create', 'evaluate', 'refine', 'simplify', 'harden', 'system']; @@ -82,12 +84,12 @@ function renderDesktopLayout(container, commands) { }; // Preferred order within each category (unlisted commands append at end) const categoryCommandOrder = { - 'create': ['impeccable', 'shape'], + 'create': ['impeccable', 'craft', 'shape'], 'evaluate': ['critique', 'audit'], - 'refine': ['typeset', 'arrange', 'colorize', 'animate', 'delight', 'bolder', 'quieter', 'onboard', 'overdrive'], + 'refine': ['typeset', 'layout', 'colorize', 'animate', 'delight', 'bolder', 'quieter', 'overdrive'], 'simplify': ['distill', 'clarify', 'adapt'], - 'harden': ['normalize', 'polish', 'optimize', 'harden'], - 'system': ['extract'] + 'harden': ['polish', 'optimize', 'harden'], + 'system': ['teach', 'extract'] }; const grouped = {}; filteredCommands.forEach(cmd => { @@ -133,7 +135,13 @@ function renderDesktopLayout(container, commands) { const fisheyeHTML = filteredCommands.map((cmd, i) => { const cat = commandCategories[cmd.id] || 'other'; const isBeta = betaCommands.includes(cmd.id); - return ``; + // The root skill is shown as "/impeccable", everything else is a sub-command + // displayed without a slash (invocation is /impeccable ) + const isRoot = cmd.id === 'impeccable'; + const label = isRoot + ? `/impeccable` + : cmd.id; + return ``; }).join(''); container.innerHTML = ` @@ -193,12 +201,20 @@ function renderSpread(cmd, index, isActive) { } } + // The root skill is rendered as /impeccable; sub-commands are rendered as + // /impeccable on a smaller line above the command name, so the command name + // stays the visual anchor at full display size. + const isRoot = cmd.id === 'impeccable'; + const nameHTML = isRoot + ? `/impeccable` + : `/impeccable${cmd.id}`; + return `
      ${categoryLabels[cat] || cat} -

      /${cmd.id}${isBeta ? 'BETA' : ''}

      -

      ${cmd.description}

      +

      ${nameHTML}${isBeta ? 'BETA' : ''}

      +

      ${cmd.tagline || cmd.description}

      ${flowHTML}
      @@ -466,9 +482,11 @@ function truncateDescription(text, maxLen = 120) { function renderMobileLayout(container, commands) { // Build carousel pills + // Carousel pills show bare command names for sub-commands, and /impeccable + // for the root entry. const carouselHTML = commands.map((cmd, i) => ` `).join(''); @@ -477,18 +495,24 @@ function renderMobileLayout(container, commands) { const relationship = commandRelationships[cmd.id]; let relationshipHTML = ''; + // Relationships show bare command names (e.g., "pairs with quieter") + // because the invocation is /impeccable , not /. if (relationship) { if (relationship.pairs) { - relationshipHTML = `
      ↔ pairs with /${relationship.pairs}
      `; + relationshipHTML = `
      ↔ pairs with ${relationship.pairs}
      `; } else if (relationship.leadsTo && relationship.leadsTo.length > 0) { - relationshipHTML = `
      → leads to ${relationship.leadsTo.map(c => `/${c}`).join(', ')}
      `; + relationshipHTML = `
      → leads to ${relationship.leadsTo.map(c => `${c}`).join(', ')}
      `; } } + const cardName = cmd.id === 'impeccable' + ? '/impeccable' + : `/impeccable ${cmd.id}`; + return `
      -

      /${cmd.id}

      -

      ${cmd.description}

      +

      ${cardName}

      +

      ${cmd.tagline || cmd.description}

      ${relationshipHTML}
      `; diff --git a/public/js/data.js b/public/js/data.js index d3858a50b..4861eb896 100644 --- a/public/js/data.js +++ b/public/js/data.js @@ -53,9 +53,9 @@ export const skillReferenceDomains = [ ]; export const commandProcessSteps = { - 'shape': ['Interview', 'Synthesize', 'Brief', 'Confirm'], - 'impeccable craft': ['Shape', 'Reference', 'Build', 'Iterate'], 'impeccable': ['Direct', 'Design', 'Build', 'Refine'], + 'craft': ['Shape', 'Reference', 'Build', 'Iterate'], + 'shape': ['Interview', 'Synthesize', 'Brief', 'Confirm'], 'overdrive': ['Assess', 'Choose', 'Build', 'Polish'], 'critique': ['Evaluate', 'Critique', 'Prioritize', 'Suggest'], 'audit': ['Scan', 'Document', 'Prioritize', 'Recommend'], @@ -72,15 +72,15 @@ export const commandProcessSteps = { 'polish': ['Discover', 'Review', 'Refine', 'Verify'], 'optimize': ['Profile', 'Identify', 'Improve', 'Measure'], 'harden': ['Test', 'Handle', 'Onboard', 'Validate'], - 'impeccable teach': ['Explore', 'Interview', 'Synthesize', 'Save'], - 'impeccable extract': ['Identify', 'Abstract', 'Migrate', 'Document'] + 'teach': ['Explore', 'Interview', 'Synthesize', 'Save'], + 'extract': ['Identify', 'Abstract', 'Migrate', 'Document'] }; export const commandCategories = { // CREATE - build something new - 'shape': 'create', - 'impeccable craft': 'create', 'impeccable': 'create', + 'craft': 'create', + 'shape': 'create', // EVALUATE - review and assess 'critique': 'evaluate', 'audit': 'evaluate', @@ -102,8 +102,8 @@ export const commandCategories = { 'optimize': 'harden', 'harden': 'harden', // SYSTEM - setup and tooling - 'impeccable teach': 'system', - 'impeccable extract': 'system' + 'teach': 'system', + 'extract': 'system' }; // Skill relationships - now consolidated into impeccable skill @@ -116,10 +116,9 @@ export const skillRelationships = { }; export const commandRelationships = { - 'shape': { flow: 'Create: Plan UX and UI through structured discovery' }, - 'impeccable craft': { flow: 'Create: Full shape-then-build flow with visual iteration' }, 'impeccable': { flow: 'Create: Freeform design with full design intelligence' }, - 'overdrive': { combinesWith: ['animate', 'delight'], flow: 'Refine: Technically extraordinary effects' }, + 'craft': { flow: 'Create: Full shape-then-build flow with visual iteration' }, + 'shape': { flow: 'Create: Plan UX and UI through structured discovery' }, 'critique': { leadsTo: ['polish', 'distill', 'bolder', 'quieter', 'typeset', 'layout'], flow: 'Evaluate: UX and design review with scoring' }, 'audit': { leadsTo: ['harden', 'optimize', 'adapt', 'clarify'], flow: 'Evaluate: Technical quality audit' }, 'typeset': { combinesWith: ['bolder', 'polish'], flow: 'Refine: Fix typography and type hierarchy' }, @@ -129,12 +128,13 @@ export const commandRelationships = { 'delight': { combinesWith: ['bolder', 'animate'], flow: 'Refine: Add personality and joy' }, 'bolder': { pairs: 'quieter', flow: 'Refine: Amplify timid designs' }, 'quieter': { pairs: 'bolder', flow: 'Refine: Tone down aggressive designs' }, + 'overdrive': { combinesWith: ['animate', 'delight'], flow: 'Refine: Technically extraordinary effects' }, 'distill': { combinesWith: ['quieter', 'polish'], flow: 'Simplify: Strip to essence' }, 'clarify': { combinesWith: ['polish', 'adapt'], flow: 'Simplify: Improve UX copy' }, 'adapt': { combinesWith: ['polish', 'clarify'], flow: 'Simplify: Adapt for different contexts' }, 'polish': { flow: 'Harden: Final pass and design system alignment' }, 'optimize': { flow: 'Harden: Performance improvements' }, 'harden': { combinesWith: ['optimize'], flow: 'Harden: Edge cases, onboarding, and error handling' }, - 'impeccable teach': { flow: 'System: One-time project design context setup' }, - 'impeccable extract': { flow: 'System: Extract design system components and tokens' } + 'teach': { flow: 'System: One-time project design context setup' }, + 'extract': { flow: 'System: Extract design system components and tokens' } }; diff --git a/public/js/demo-renderer.js b/public/js/demo-renderer.js index 7247e3a97..8d6121489 100644 --- a/public/js/demo-renderer.js +++ b/public/js/demo-renderer.js @@ -61,6 +61,78 @@ export function renderCommandDemo(commandId) {
      `; } + // craft is the full end-to-end flow, show the four stages + if (commandId === 'craft') { + return ` +
      +
      +
      +
      Shape, reference, build, iterate
      +
      +
      +
      + 1. Shape +
      + Runs /impeccable shape internally to build a design brief from discovery questions. No code yet. +
      +
      +
      + 2. Reference +
      + Loads the right reference files for the feature (spatial design, typography, motion, color) based on what the brief calls for. +
      +
      +
      + 3. Build +
      + Implements structure, spacing, type, color, states, motion, responsive. Every decision traces back to the brief. +
      +
      +
      + 4. Visual iteration +
      + Opens the result in a browser, checks against the brief and anti-pattern list, refines until the polish bar is high. +
      +
      +
      The full shape-then-build flow in one command. Best for brand-new features.
      +
      +
      +
      + `; + } + // teach sets up the project's design context, show the flow + if (commandId === 'teach') { + return ` +
      +
      +
      +
      One-time project setup
      +
      +
      +
      + 1. Explore +
      + Scans the codebase for brand assets, existing design tokens, typography, components, and documentation. +
      +
      +
      + 2. Interview +
      + Asks about audience, brand personality, aesthetic direction, and accessibility needs. Skips anything it can infer from the code. +
      +
      +
      + 3. Save +
      + Writes a .impeccable.md file with users, brand, aesthetic direction, and design principles. Every future command reads it automatically. +
      +
      +
      Run once per project. Then forget it exists.
      +
      +
      +
      + `; + } // shape is a planning skill — show the process if (commandId === 'shape') { return ` diff --git a/public/js/generated/counts.js b/public/js/generated/counts.js index 397efb84c..6a9333419 100644 --- a/public/js/generated/counts.js +++ b/public/js/generated/counts.js @@ -1,3 +1,3 @@ // GENERATED by build.js — do not edit -export const COMMAND_COUNT = 18; +export const COMMAND_COUNT = 20; export const DETECTION_COUNT = 25; diff --git a/public/privacy.html b/public/privacy.html index 6944106c6..3a41097f0 100644 --- a/public/privacy.html +++ b/public/privacy.html @@ -32,7 +32,7 @@
      diff --git a/public/sitemap.xml b/public/sitemap.xml index 8cc157893..b78f423ef 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -3,67 +3,67 @@ https://impeccable.style/ - 2026-04-08 + 2026-04-10 weekly 1.0 - https://impeccable.style/cheatsheet - 2026-04-08 - monthly - 0.7 - - - https://impeccable.style/gallery - 2026-04-08 - monthly - 0.7 + https://impeccable.style/privacy + 2026-04-10 + yearly + 0.3 - https://impeccable.style/skills - 2026-04-08 + https://impeccable.style/docs + 2026-04-10 weekly 0.9 https://impeccable.style/anti-patterns - 2026-04-08 + 2026-04-10 weekly 0.9 + + https://impeccable.style/visual-mode + 2026-04-10 + weekly + 0.8 + https://impeccable.style/tutorials - 2026-04-08 + 2026-04-10 weekly 0.9 - - https://impeccable.style/skills/adapt2026-04-080.8 - https://impeccable.style/skills/animate2026-04-080.8 - https://impeccable.style/skills/arrange2026-04-080.8 - https://impeccable.style/skills/audit2026-04-080.8 - https://impeccable.style/skills/bolder2026-04-080.8 - https://impeccable.style/skills/clarify2026-04-080.8 - https://impeccable.style/skills/colorize2026-04-080.8 - https://impeccable.style/skills/critique2026-04-080.8 - https://impeccable.style/skills/delight2026-04-080.8 - https://impeccable.style/skills/distill2026-04-080.8 - https://impeccable.style/skills/extract2026-04-080.8 - https://impeccable.style/skills/harden2026-04-080.8 - https://impeccable.style/skills/impeccable2026-04-080.8 - https://impeccable.style/skills/normalize2026-04-080.8 - https://impeccable.style/skills/onboard2026-04-080.8 - https://impeccable.style/skills/optimize2026-04-080.8 - https://impeccable.style/skills/overdrive2026-04-080.8 - https://impeccable.style/skills/polish2026-04-080.8 - https://impeccable.style/skills/quieter2026-04-080.8 - https://impeccable.style/skills/shape2026-04-080.8 - https://impeccable.style/skills/typeset2026-04-080.8 + + https://impeccable.style/docs/impeccable2026-04-100.9 + https://impeccable.style/docs/craft2026-04-100.8 + https://impeccable.style/docs/teach2026-04-100.8 + https://impeccable.style/docs/extract2026-04-100.8 + https://impeccable.style/docs/shape2026-04-100.8 + https://impeccable.style/docs/critique2026-04-100.8 + https://impeccable.style/docs/audit2026-04-100.8 + https://impeccable.style/docs/polish2026-04-100.8 + https://impeccable.style/docs/bolder2026-04-100.8 + https://impeccable.style/docs/quieter2026-04-100.8 + https://impeccable.style/docs/distill2026-04-100.8 + https://impeccable.style/docs/harden2026-04-100.8 + https://impeccable.style/docs/animate2026-04-100.8 + https://impeccable.style/docs/colorize2026-04-100.8 + https://impeccable.style/docs/typeset2026-04-100.8 + https://impeccable.style/docs/layout2026-04-100.8 + https://impeccable.style/docs/delight2026-04-100.8 + https://impeccable.style/docs/overdrive2026-04-100.8 + https://impeccable.style/docs/clarify2026-04-100.8 + https://impeccable.style/docs/adapt2026-04-100.8 + https://impeccable.style/docs/optimize2026-04-100.8 - https://impeccable.style/tutorials/getting-started2026-04-080.8 - https://impeccable.style/tutorials/critique-with-overlay2026-04-080.8 + https://impeccable.style/tutorials/getting-started2026-04-100.8 + https://impeccable.style/tutorials/critique-with-overlay2026-04-100.8 diff --git a/scripts/build-sub-pages.js b/scripts/build-sub-pages.js index a8f8b7eae..621509328 100644 --- a/scripts/build-sub-pages.js +++ b/scripts/build-sub-pages.js @@ -5,7 +5,7 @@ * server/index.js (at module load), so dev and prod share the same * code path and output shape. * - * Output lives under public/skills/, public/anti-patterns/, + * Output lives under public/docs/, public/anti-patterns/, * public/tutorials/, all gitignored. Bun's HTML loader picks them up * the same way it picks up the hand-authored pages. */ @@ -17,6 +17,7 @@ import { CATEGORY_ORDER, CATEGORY_LABELS, CATEGORY_DESCRIPTIONS, + COMMAND_RELATIONSHIPS, LAYER_LABELS, LAYER_DESCRIPTIONS, GALLERY_ITEMS, @@ -119,12 +120,19 @@ ${refBody} const hasDemo = demoHtml.trim().length > 0; + // Sub-commands are accessed via /impeccable . Show "/impeccable" as + // a smaller namespace label above the command name, matching the magazine + // spread treatment so the command name stays at full display size. + const titleHtml = skill.isSubCommand + ? `/impeccable${escapeHtml(skill.id)}` + : `/${escapeHtml(skill.id)}`; + return `
      -

      Skills / ${escapeHtml(categoryLabel)}

      -

      /${escapeHtml(skill.id)}

      +

      Docs / ${escapeHtml(categoryLabel)}

      +

      ${titleHtml}

      ${escapeHtml(tagline)}

      ${metaStrip}
      @@ -135,8 +143,8 @@ ${refBody}
      - SKILL.md - The canonical skill definition your AI harness loads. + ${skill.isSubCommand ? 'reference/' + escapeHtml(skill.id) + '.md' : 'SKILL.md'} + ${skill.isSubCommand ? 'Loaded when the impeccable skill routes to this command.' : 'The canonical skill definition your AI harness loads.'}
      ${bodyHtml} @@ -197,35 +205,28 @@ ${tutorials `; } - // Sub-command links that appear as indented entries after their parent skill. - const SUB_COMMANDS = { - impeccable: [ - { id: 'impeccable-craft', label: '/impeccable craft', href: '/skills/impeccable#craft' }, - { id: 'impeccable-teach', label: '/impeccable teach', href: '/skills/impeccable#teach' }, - { id: 'impeccable-extract', label: '/impeccable extract', href: '/skills/impeccable#extract' }, - ], - }; - - // Then the skills, grouped by category. + // Then the skills, grouped by category. The root "/impeccable" entry is + // shown with its slash; sub-commands are shown as bare names (since the + // invocation is /impeccable ). Within a category the list is + // alphabetical, except /impeccable always pins to the top of Create. for (const category of CATEGORY_ORDER) { - const list = skillsByCategory[category] || []; - if (list.length === 0) continue; + const raw = skillsByCategory[category] || []; + if (raw.length === 0) continue; + const list = [...raw].sort((a, b) => { + if (a.id === 'impeccable') return -1; + if (b.id === 'impeccable') return 1; + return a.id.localeCompare(b.id); + }); html += `

      ${escapeHtml(CATEGORY_LABELS[category])}

        ${list - .flatMap((s) => { + .map((s) => { const isCurrent = current?.kind === 'skill' && current.id === s.id; const attr = isCurrent ? ' aria-current="page"' : ''; - const items = [`
      • /${escapeHtml(s.id)}
        • `]; - const subs = SUB_COMMANDS[s.id]; - if (subs) { - for (const sub of subs) { - items.push(`
      • ${escapeHtml(sub.label)}
        • `); - } - } - return items; + const label = s.id === 'impeccable' ? '/impeccable' : escapeHtml(s.id); + return `
      • ${label}
        • `; }) .join('\n')}
      @@ -244,52 +245,113 @@ ${list * This is the orientation piece: what skills are, how to pick one, * the six categories explained with inline cross-links to detail pages. */ -function renderSkillsOverviewMain(skillsByCategory) { - const totalSkills = Object.values(skillsByCategory).reduce( - (sum, list) => sum + list.length, - 0, - ); +function renderSkillsOverviewMain(skillsByCategory, allSkills) { + // Build a lookup by id so we can pull taglines/descriptions for the cards. + const skillsById = Object.fromEntries(allSkills.map((s) => [s.id, s])); + const commandCount = allSkills.filter((s) => s.id !== 'impeccable').length; + // Short, clean tagline for the home command card. Fall back to the editorial + // tagline if set, otherwise use a default. + const impeccable = skillsById['impeccable']; + const homeTagline = impeccable?.editorial?.frontmatter?.tagline + || 'The design intelligence behind every command.'; + + // Render a single command as a compact row: name on the left, description + // and relationship on the right. Matches the original cheatsheet density. + const renderCommandRow = (skill) => { + const tagline = skill.editorial?.frontmatter?.tagline || skill.description; + const shortTagline = tagline.length > 140 ? tagline.slice(0, 137) + '...' : tagline; + const rel = COMMAND_RELATIONSHIPS[skill.id] || {}; + const isBeta = skill.id === 'overdrive'; + + let metaHtml = ''; + if (rel.pairs) { + metaHtml = `
      Pairs with ${rel.pairs}
      `; + } else if (rel.leadsTo?.length) { + const links = rel.leadsTo.map((c) => `${c}`).join(', '); + metaHtml = `
      Leads to ${links}
      `; + } else if (rel.combinesWith?.length) { + const links = rel.combinesWith.map((c) => `${c}`).join(', '); + metaHtml = `
      Combines with ${links}
      `; + } + + // Row is a
      (not an ) so the inner relationship links are valid. + // The name on the left is the primary link target. + return ` +
      +
      + /impeccable ${escapeHtml(skill.id)}${isBeta ? ' BETA' : ''} +
      +
      +

      ${escapeHtml(shortTagline)}

      + ${metaHtml} +
      +
      `; + }; + + // Render category sections, skipping the Create category's /impeccable root + // (shown as a hero card above) but keeping everything else in place. let categoriesHtml = ''; for (const category of CATEGORY_ORDER) { - const list = skillsByCategory[category] || []; + const list = (skillsByCategory[category] || []).filter((s) => s.id !== 'impeccable'); if (list.length === 0) continue; - const skillChips = list - .map( - (s) => - `/${escapeHtml(s.id)}`, - ) - .join(''); + const rowsHtml = list.map(renderCommandRow).join(''); categoriesHtml += ` -
      -
      -

      ${escapeHtml(CATEGORY_LABELS[category])}

      -

      ${list.length} ${list.length === 1 ? 'skill' : 'skills'}

      -
      -

      ${escapeHtml(CATEGORY_DESCRIPTIONS[category])}

      -
      -${skillChips} +
      +
      +
      +

      ${escapeHtml(CATEGORY_LABELS[category])}

      +

      ${escapeHtml(CATEGORY_DESCRIPTIONS[category])}

      +
      + ${list.length} ${list.length === 1 ? 'command' : 'commands'} +
      +
      +${rowsHtml}
      `; } return ` -
      -
      -

      ${totalSkills} commands

      -

      Skills

      -

      One skill, /impeccable, teaches your AI design. Eighteen commands steer the result. Each command does one job with an opinion about what good looks like.

      +
      +
      +

      1 skill · ${commandCount} commands

      +

      Commands

      +

      Impeccable gives you a shared design vocabulary with your AI. ${commandCount} commands that each encode a specific design discipline, so you can steer with precision. Pick one for the job or let the skill route you automatically.

      -
      -

      How to pick one

      -

      Skills are named after the intent you bring to them. Reviewing something? /critique or /audit. Fixing type? /typeset. Last-mile pass before shipping? /polish. The categories below group skills by the job.

      +
      +
      + The home command +

      /impeccable

      +

      ${escapeHtml(homeTagline)}

      +

      Call /impeccable directly for freeform design work with the full guidebook loaded. Or reach for one of its specialized modes:

      +
      +
      -
      +
      ${categoriesHtml}
      `; @@ -397,7 +459,7 @@ function renderRuleCard(rule) { const layerLabel = LAYER_LABELS[layer] || layer; const layerTitle = LAYER_DESCRIPTIONS[layer] || ''; const skillLink = rule.skillSection - ? `See in /impeccable` + ? `See in /impeccable` : ''; const visual = rule.visual ? `` @@ -500,9 +562,9 @@ function renderVisualModeMain() {

      Three ways to run it

      -

      Inside /critique

      -

      /critique

      -

      The design review skill opens the overlay automatically during its browser assessment pass. You get the deterministic findings highlighted in place while the LLM runs its separate heuristic review.

      +

      Inside /impeccable critique

      +

      /impeccable critique

      +

      The design review command opens the overlay automatically during its browser assessment pass. You get the deterministic findings highlighted in place while the LLM runs its separate heuristic review.

      Standalone CLI

      @@ -579,7 +641,7 @@ ${rules.map(renderRuleCard).join('\n')}

      ${totalRules} rules

      Anti-patterns

      -

      The full catalog of patterns /impeccable teaches against. ${detectedCount} are caught by a deterministic detector (npx impeccable detect or the browser extension). ${llmCount} can only be flagged by /critique's LLM review pass. Want to see them live on real pages? Try Visual Mode.

      +

      The full catalog of patterns /impeccable teaches against. ${detectedCount} are caught by a deterministic detector (npx impeccable detect or the browser extension). ${llmCount} can only be flagged by /impeccable critique's LLM review pass. Want to see them live on real pages? Try Visual Mode.

      @@ -592,7 +654,7 @@ ${rules.map(renderRuleCard).join('\n')}
      CLI
      Deterministic. Runs from npx impeccable detect on files, no browser required.
      Browser
      Deterministic, but needs real browser layout. Runs via the browser extension or Puppeteer, not the plain CLI.
      -
      LLM only
      No deterministic detector. Caught by /critique during its LLM design review.
      +
      LLM only
      No deterministic detector. Caught by /impeccable critique during its LLM design review.
    @@ -612,7 +674,7 @@ ${sectionsHtml} export async function generateSubPages(rootDir) { const data = await buildSubPageData(rootDir); const outDirs = { - skills: path.join(rootDir, 'public/skills'), + docs: path.join(rootDir, 'public/docs'), antiPatterns: path.join(rootDir, 'public/anti-patterns'), tutorials: path.join(rootDir, 'public/tutorials'), visualMode: path.join(rootDir, 'public/visual-mode'), @@ -626,39 +688,41 @@ export async function generateSubPages(rootDir) { const generated = []; - // Skills index: docs-browser layout with unified sidebar. + // Docs index: the full command reference with rich cards. { const sidebar = renderDocsSidebar(data.skillsByCategory, data.tutorials, null); - const main = renderSkillsOverviewMain(data.skillsByCategory); + const main = renderSkillsOverviewMain(data.skillsByCategory, data.skills); const html = renderPage({ - title: 'Skills | Impeccable', + title: 'Docs | Impeccable', description: - '18 commands that teach your AI harness how to design. Browse by category: create, evaluate, refine, simplify, harden.', + '20 commands that teach your AI harness how to design. Browse by category: create, evaluate, refine, simplify, harden.', bodyHtml: wrapInDocsLayout(sidebar, main), activeNav: 'docs', - canonicalPath: '/skills', + canonicalPath: '/docs', bodyClass: 'sub-page skills-layout-page', }); - const out = path.join(outDirs.skills, 'index.html'); + const out = path.join(outDirs.docs, 'index.html'); fs.writeFileSync(out, html, 'utf-8'); generated.push(out); } - // Skills detail pages: same docs-browser shell as the overview. + // Per-command detail pages: same docs-browser shell as the overview. for (const skill of data.skills) { const sidebar = renderDocsSidebar(data.skillsByCategory, data.tutorials, { kind: 'skill', id: skill.id }); const main = renderSkillDetail(skill, data.knownSkillIds); - const title = `/${skill.id} | Impeccable`; + const title = skill.isSubCommand + ? `/impeccable ${skill.id} | Impeccable` + : `/${skill.id} | Impeccable`; const description = skill.editorial?.frontmatter?.tagline || skill.description; const html = renderPage({ title, description, bodyHtml: wrapInDocsLayout(sidebar, main), activeNav: 'docs', - canonicalPath: `/skills/${skill.id}`, + canonicalPath: `/docs/${skill.id}`, bodyClass: 'sub-page skills-layout-page', }); - const out = path.join(outDirs.skills, `${skill.id}.html`); + const out = path.join(outDirs.docs, `${skill.id}.html`); fs.writeFileSync(out, html, 'utf-8'); generated.push(out); } @@ -703,7 +767,7 @@ export async function generateSubPages(rootDir) { const html = renderPage({ title: 'Visual Mode | Impeccable', description: - 'See every anti-pattern flagged directly on the page. Live detection overlay from Impeccable, available via /critique, npx impeccable live, or the upcoming Chrome extension.', + 'See every anti-pattern flagged directly on the page. Live detection overlay from Impeccable, available via /impeccable critique, npx impeccable live, or the upcoming Chrome extension.', bodyHtml: renderVisualModeMain(), activeNav: 'visual-mode', canonicalPath: '/visual-mode', diff --git a/scripts/build.js b/scripts/build.js index 4668d3cd4..6636eec54 100644 --- a/scripts/build.js +++ b/scripts/build.js @@ -27,13 +27,23 @@ import { generateSubPages } from './build-sub-pages.js'; * Also validates that key HTML files reference the correct numbers. */ function generateCounts(rootDir, skills, buildDir) { - // Count active (non-deprecated) user-invocable commands - const activeCommands = skills.filter(s => { - if (!s.userInvocable) return false; - const content = fs.readFileSync(s.filePath, 'utf-8'); - return !content.includes('DEPRECATED'); - }); - const commandCount = activeCommands.length; + // Count active commands. After the v3.0 consolidation, commands are sub-commands + // of /impeccable. Count them from the command router table in SKILL.md. + const impeccableSkill = skills.find(s => s.name === 'impeccable'); + let commandCount; + if (impeccableSkill) { + // Count lines in the router table that have a | `command` | pattern + const routerMatches = impeccableSkill.body.match(/^\| `\w+` \|/gm); + commandCount = routerMatches ? routerMatches.length : 0; + } else { + // Fallback: count user-invocable skills + const activeCommands = skills.filter(s => { + if (!s.userInvocable) return false; + const content = fs.readFileSync(s.filePath, 'utf-8'); + return !content.includes('DEPRECATED'); + }); + commandCount = activeCommands.length; + } // Count detection rules from impeccable package const detectPkgPath = path.join(rootDir, 'src/detect-antipatterns.mjs'); @@ -56,7 +66,6 @@ function generateCounts(rootDir, skills, buildDir) { // Validate counts in key files const filesToCheck = [ 'public/index.html', - 'public/cheatsheet.html', 'README.md', 'NOTICE.md', 'AGENTS.md', @@ -73,7 +82,7 @@ function generateCounts(rootDir, skills, buildDir) { // Check for stale command counts (look for "N commands" or "N skills" patterns) // Strip changelog list content to avoid flagging historical counts const strippedContent = content.replace(/
      [\s\S]*?<\/ul>/g, ''); - const countPattern = /\b(\d+)\s+(design\s+)?(commands|skills|steering commands)/gi; + const countPattern = /\b(\d+)\s+(design\s+)?(commands|sub-commands|skills|steering commands)/gi; for (const match of strippedContent.matchAll(countPattern)) { const num = parseInt(match[1]); // Allow 1 (for "1 skill") and the correct count @@ -174,7 +183,6 @@ function validateNoEmDashes(rootDir) { const targets = [ 'content/site', 'public/index.html', - 'public/cheatsheet.html', 'public/privacy.html', 'scripts/build-sub-pages.js', 'scripts/lib/sub-pages-data.js', @@ -228,7 +236,6 @@ function validateNoEmDashes(rootDir) { function validateSiteHeader(rootDir) { const pages = [ 'public/index.html', - 'public/cheatsheet.html', 'public/privacy.html', ]; const marker = ''; @@ -281,7 +288,6 @@ const DIST_DIR = path.join(ROOT_DIR, 'dist'); async function buildStaticSite(extraEntrypoints = []) { const entrypoints = [ path.join(ROOT_DIR, 'public', 'index.html'), - path.join(ROOT_DIR, 'public', 'cheatsheet.html'), path.join(ROOT_DIR, 'public', 'privacy.html'), ...extraEntrypoints, ]; @@ -328,7 +334,7 @@ async function buildStaticSite(extraEntrypoints = []) { const cssFiles = result.outputs.filter(o => o.path.endsWith('.css')); // When entrypoints span multiple depths under public/ (e.g. public/index.html - // + public/skills/polish.html), Bun's HTML loader preserves the full public/ + // + public/docs/polish.html), Bun's HTML loader preserves the full public/ // prefix in the output tree. Flatten build/public/* up to build/*. const nestedPublic = path.join(outdir, 'public'); if (fs.existsSync(nestedPublic)) { @@ -435,8 +441,49 @@ function generateApiData(buildDir, skills, patterns) { })); fs.writeFileSync(path.join(apiDir, 'skills.json'), JSON.stringify(skillsData)); - // commands.json (user-invocable skills only) - const commandsData = skillsData.filter(s => s.userInvocable); + // commands.json - after v3.0 consolidation, commands are sub-commands of + // /impeccable. Load them from command-metadata.json and include the root + // impeccable skill itself so UI surfaces like the cheatsheet can list them. + // Each entry also picks up a short `tagline` from its editorial file + // (content/site/skills/.md) when one exists. Taglines are used by UI + // surfaces that need a human-friendly one-liner, while `description` stays + // optimized for auto-trigger keyword matching in the AI harness. + const readTagline = (id) => { + const editorialPath = path.join(ROOT_DIR, 'content/site/skills', `${id}.md`); + if (!fs.existsSync(editorialPath)) return null; + const raw = fs.readFileSync(editorialPath, 'utf-8'); + const match = raw.match(/^---\n([\s\S]*?)\n---/); + if (!match) return null; + const taglineMatch = match[1].match(/tagline:\s*"([^"]+)"/); + return taglineMatch ? taglineMatch[1] : null; + }; + + const metadataPath = path.join(ROOT_DIR, 'source/skills/impeccable/scripts/command-metadata.json'); + if (!fs.existsSync(metadataPath)) { + throw new Error(`command-metadata.json is missing at ${metadataPath}. This file is required to generate the commands API.`); + } + const impeccable = skills.find(s => s.name === 'impeccable'); + if (!impeccable) { + throw new Error('impeccable skill not found in source/skills/. The build system expects a single impeccable skill.'); + } + + const metadata = JSON.parse(fs.readFileSync(metadataPath, 'utf-8')); + const commandsData = [ + { + id: 'impeccable', + name: 'impeccable', + description: impeccable.description, + tagline: readTagline('impeccable'), + userInvocable: true, + }, + ...Object.entries(metadata).map(([id, meta]) => ({ + id, + name: id, + description: meta.description, + tagline: readTagline(id), + userInvocable: true, + })), + ]; fs.writeFileSync(path.join(apiDir, 'commands.json'), JSON.stringify(commandsData)); // patterns.json @@ -454,7 +501,8 @@ function generateApiData(buildDir, skills, patterns) { ); } - console.log(`✓ Generated static API data (${skillsData.length} skills, ${commandsData.length} commands)`); + const skillWord = skillsData.length === 1 ? 'skill' : 'skills'; + console.log(`✓ Generated static API data (${skillsData.length} ${skillWord}, ${commandsData.length} commands)`); } /** @@ -523,12 +571,16 @@ function generateCFConfig(buildDir) { `; fs.writeFileSync(path.join(buildDir, '_headers'), headers); - // _redirects: rewrite JSON API routes to static files (200 = rewrite, not redirect) + // _redirects: rewrite JSON API routes to static files (200 = rewrite, not redirect). + // Also permanent redirects for legacy URLs: /skills -> /docs, /cheatsheet -> /docs. const redirects = `/api/skills /_data/api/skills.json 200 /api/commands /_data/api/commands.json 200 /api/patterns /_data/api/patterns.json 200 /api/command-source/:id /_data/api/command-source/:id.json 200 /gallery /visual-mode#try-it-live 301 +/cheatsheet /docs 301 +/skills /docs 301 +/skills/:id /docs/:id 301 `; fs.writeFileSync(path.join(buildDir, '_redirects'), redirects); @@ -630,6 +682,10 @@ async function build() { const deprecatedLocalSkills = [ 'frontend-design', 'teach-impeccable', 'arrange', 'normalize', 'onboard', 'extract', + // v3.0 consolidation: standalone skills -> /impeccable sub-commands + 'adapt', 'animate', 'audit', 'bolder', 'clarify', 'colorize', + 'critique', 'delight', 'distill', 'harden', 'layout', 'optimize', + 'overdrive', 'polish', 'quieter', 'shape', 'typeset', ]; for (const { configDir } of syncConfigs) { for (const name of deprecatedLocalSkills) { diff --git a/scripts/lib/render-markdown.js b/scripts/lib/render-markdown.js index 41a4116ad..068b9f286 100644 --- a/scripts/lib/render-markdown.js +++ b/scripts/lib/render-markdown.js @@ -82,7 +82,7 @@ export function createRenderer({ knownSkillIds = new Set(), currentSkillId = nul * * - `http(s)://…` → unchanged, external * - `reference/foo.md` → `#reference-foo` on current skill page - * - `/skill-id` (known) → `/skills/skill-id` + * - `/skill-id` (known) → `/docs/skill-id` * - `#anchor` → unchanged (in-page anchor) * - anything else → unchanged (will be caught by build warnings later) * @@ -112,12 +112,12 @@ function resolveHref(href, { knownSkillIds, currentSkillId }) { // /skill-id mentioned in prose (e.g. "run /polish") const slashMatch = href.match(/^\/([a-z0-9-]+)$/i); if (slashMatch && knownSkillIds.has(slashMatch[1])) { - return { href: `/skills/${slashMatch[1]}`, external: false }; + return { href: `/docs/${slashMatch[1]}`, external: false }; } - // [text](other-skill) → /skills/other-skill + // [text](other-skill) → /docs/other-skill if (/^[a-z0-9-]+$/i.test(href) && knownSkillIds.has(href)) { - return { href: `/skills/${href}`, external: false }; + return { href: `/docs/${href}`, external: false }; } // Unknown — pass through. Generator can warn separately. diff --git a/scripts/lib/sub-pages-data.js b/scripts/lib/sub-pages-data.js index 61246f932..7523de8dd 100644 --- a/scripts/lib/sub-pages-data.js +++ b/scripts/lib/sub-pages-data.js @@ -13,7 +13,7 @@ import fs from 'node:fs'; import path from 'node:path'; import { pathToFileURL } from 'node:url'; -import { readSourceFiles, parseFrontmatter } from './utils.js'; +import { readSourceFiles, parseFrontmatter, replacePlaceholders } from './utils.js'; import { DETECTION_LAYERS, VISUAL_EXAMPLES, @@ -37,7 +37,6 @@ const EXCLUDED_SKILLS = new Set([ 'arrange', // renamed to layout 'normalize', // merged into /polish 'onboard', // merged into /harden - 'extract', // merged into /impeccable extract ]); /** @@ -48,6 +47,7 @@ const EXCLUDED_SKILLS = new Set([ const SKILL_CATEGORIES = { // CREATE - build something new impeccable: 'create', + craft: 'create', shape: 'create', // EVALUATE - review and assess critique: 'evaluate', @@ -69,9 +69,12 @@ const SKILL_CATEGORIES = { polish: 'harden', optimize: 'harden', harden: 'harden', + // SYSTEM - setup and tooling + teach: 'system', + extract: 'system', }; -export const CATEGORY_ORDER = ['create', 'evaluate', 'refine', 'simplify', 'harden']; +export const CATEGORY_ORDER = ['create', 'evaluate', 'refine', 'simplify', 'harden', 'system']; export const CATEGORY_LABELS = { create: 'Create', @@ -91,6 +94,43 @@ export const CATEGORY_DESCRIPTIONS = { system: 'Setup and tooling. Design system work, extraction, organization.', }; +/** + * How commands relate to each other. Mirrors public/js/data.js so the server + * can render the docs overview without loading the client bundle. + * + * - leadsTo: commands that typically follow this one (used for evaluators) + * - pairs: the inverse counterpart (bolder <-> quieter) + * - combinesWith: commands that work well alongside this one + */ +export const COMMAND_RELATIONSHIPS = { + // Create + craft: { combinesWith: ['shape'] }, + shape: { combinesWith: ['craft'] }, + // Evaluate (these are the "diagnostics" that lead to fixes) + audit: { leadsTo: ['harden', 'optimize', 'adapt', 'clarify'] }, + critique: { leadsTo: ['polish', 'distill', 'bolder', 'quieter', 'typeset', 'layout'] }, + // Refine + typeset: { combinesWith: ['bolder', 'polish'] }, + layout: { combinesWith: ['distill', 'adapt'] }, + colorize: { combinesWith: ['bolder', 'delight'] }, + animate: { combinesWith: ['delight'] }, + delight: { combinesWith: ['bolder', 'animate'] }, + bolder: { pairs: 'quieter' }, + quieter: { pairs: 'bolder' }, + overdrive: { combinesWith: ['animate', 'delight'] }, + // Simplify + distill: { combinesWith: ['quieter', 'polish'] }, + clarify: { combinesWith: ['polish', 'adapt'] }, + adapt: { combinesWith: ['polish', 'clarify'] }, + // Harden + polish: {}, + optimize: {}, + harden: { combinesWith: ['optimize'] }, + // System + teach: {}, + extract: {}, +}; + /** * Parse the ANTIPATTERNS array out of src/detect-antipatterns.mjs. * Mirrors the trick in scripts/build.js validateAntipatternRules() so we @@ -168,28 +208,76 @@ export async function buildSubPageData(rootDir) { const contentDir = path.join(rootDir, 'content/site'); const commandDemos = await loadCommandDemos(rootDir); - // Filter to user-invocable, non-deprecated skills. - const skills = rawSkills - .filter((s) => s.userInvocable && !EXCLUDED_SKILLS.has(s.name)) - .map((s) => { - const category = SKILL_CATEGORIES[s.name]; - const editorial = readEditorialWrapper(contentDir, 'skills', s.name); - const demo = commandDemos[s.name] || null; - return { - id: s.name, - name: s.name, - description: s.description, - argumentHint: s.argumentHint, - category, - body: s.body, - references: s.references, - editorial, // may be null - demo, // may be null (e.g. /shape has no demo) - }; - }) - .sort((a, b) => a.name.localeCompare(b.name)); + // After the v3.0 consolidation there's only one source skill (impeccable). + // Its reference/ directory holds one file per command (audit.md, polish.md, ...). + // We synthesize a virtual skill entry for each sub-command so the sub-page + // generators can keep rendering per-command pages, index cards, etc. + const impeccableSkill = rawSkills.find((s) => s.name === 'impeccable'); + const metadataPath = path.join(rootDir, 'source/skills/impeccable/scripts/command-metadata.json'); + let commandMetadata = {}; + if (fs.existsSync(metadataPath)) { + commandMetadata = JSON.parse(fs.readFileSync(metadataPath, 'utf-8')); + } - // Validate the category map covers every user-invocable skill. + // Reference files and skill bodies use {{command_prefix}} placeholders that + // are normally replaced by the provider transformer at build time. For web + // rendering, resolve them here using the claude-code provider as the canonical + // form ("/" prefix). The list of all command names includes the root skill + // plus all sub-commands from metadata so cross-references render correctly. + const allCommandNames = ['impeccable', ...Object.keys(commandMetadata)]; + const resolvePlaceholders = (content) => + replacePlaceholders(content, 'claude-code', [], allCommandNames); + + const skills = []; + + // 1. The root impeccable skill itself. + if (impeccableSkill && !EXCLUDED_SKILLS.has(impeccableSkill.name)) { + const editorial = readEditorialWrapper(contentDir, 'skills', 'impeccable'); + const demo = commandDemos['impeccable'] || null; + skills.push({ + id: 'impeccable', + name: 'impeccable', + description: impeccableSkill.description, + argumentHint: impeccableSkill.argumentHint, + category: SKILL_CATEGORIES['impeccable'], + body: resolvePlaceholders(impeccableSkill.body), + references: (impeccableSkill.references || []).map((r) => ({ + ...r, + content: resolvePlaceholders(r.content), + })), + editorial, + demo, + isSubCommand: false, + }); + } + + // 2. One virtual entry per sub-command, body sourced from its reference file. + if (impeccableSkill) { + for (const [cmdId, meta] of Object.entries(commandMetadata)) { + if (EXCLUDED_SKILLS.has(cmdId)) continue; + const refFile = impeccableSkill.references?.find((r) => r.name === cmdId); + if (!refFile) continue; // no reference file = no page + + const editorial = readEditorialWrapper(contentDir, 'skills', cmdId); + const demo = commandDemos[cmdId] || null; + skills.push({ + id: cmdId, + name: cmdId, + description: meta.description, + argumentHint: meta.argumentHint, + category: SKILL_CATEGORIES[cmdId], + body: resolvePlaceholders(refFile.content), + references: [], // sub-commands don't have their own references + editorial, + demo, + isSubCommand: true, + }); + } + } + + skills.sort((a, b) => a.name.localeCompare(b.name)); + + // Validate the category map covers every skill entry. const missing = skills.filter((s) => !s.category).map((s) => s.id); if (missing.length > 0) { throw new Error( diff --git a/scripts/lib/transformers/factory.js b/scripts/lib/transformers/factory.js index 3b33064c7..5e13a4a4d 100644 --- a/scripts/lib/transformers/factory.js +++ b/scripts/lib/transformers/factory.js @@ -123,10 +123,10 @@ export function createTransformer(config) { } } - const userInvocableCount = skills.filter((s) => s.userInvocable).length; + const skillWord = skills.length === 1 ? 'skill' : 'skills'; const refInfo = refCount > 0 ? ` (${refCount} reference files)` : ''; const scriptInfo = scriptCount > 0 ? ` (${scriptCount} script files)` : ''; const prefixInfo = prefix ? ` [${prefix}prefixed]` : ''; - console.log(`✓ ${displayName}${prefixInfo}: ${skills.length} skills (${userInvocableCount} user-invocable)${refInfo}${scriptInfo}`); + console.log(`✓ ${displayName}${prefixInfo}: ${skills.length} ${skillWord}${refInfo}${scriptInfo}`); }; } diff --git a/scripts/lib/transformers/index.js b/scripts/lib/transformers/index.js index 2d7ab7a16..cf3ddc5b1 100644 --- a/scripts/lib/transformers/index.js +++ b/scripts/lib/transformers/index.js @@ -1,6 +1,9 @@ import { createTransformer } from './factory.js'; import { PROVIDERS } from './providers.js'; +// Named exports exist primarily as stable spy targets for the test suite +// (build.test.js uses spyOn(transformers, 'transformCursor') etc.). build.js +// itself uses createTransformer + PROVIDERS directly, not these. export const transformCursor = createTransformer(PROVIDERS.cursor); export const transformClaudeCode = createTransformer(PROVIDERS['claude-code']); export const transformGemini = createTransformer(PROVIDERS.gemini); diff --git a/scripts/lib/transformers/shared.js b/scripts/lib/transformers/shared.js deleted file mode 100644 index 6cea40521..000000000 --- a/scripts/lib/transformers/shared.js +++ /dev/null @@ -1,81 +0,0 @@ -import path from 'path'; -import { cleanDir, ensureDir, writeFile, generateYamlFrontmatter, replacePlaceholders, prefixSkillReferences } from '../utils.js'; - -/** - * Shared transformer logic for all providers. - * - * @param {Object} config - Provider-specific configuration - * @param {string} config.provider - Provider key for placeholders (e.g., 'claude-code') - * @param {string} config.displayName - Display name for logging (e.g., 'Claude Code') - * @param {string} config.configDir - Dot-directory name (e.g., '.claude') - * @param {Function} config.buildFrontmatter - (skill, skillName) => frontmatter object - * @param {Function} [config.transformBody] - Optional (body, skill) => transformed body - * @param {Array} skills - All skills - * @param {string} distDir - Distribution output directory - * @param {Object} options - Optional settings (prefix, outputSuffix) - */ -export function transformProvider(config, skills, distDir, options = {}) { - const { provider, displayName, configDir, buildFrontmatter, transformBody } = config; - const { prefix = '', outputSuffix = '' } = options; - const providerDir = path.join(distDir, `${provider}${outputSuffix}`); - const skillsDir = path.join(providerDir, `${configDir}/skills`); - - cleanDir(providerDir); - ensureDir(skillsDir); - - const allSkillNames = skills.map(s => s.name); - const commandNames = skills.filter(s => s.userInvokable).map(s => `${prefix}${s.name}`); - let refCount = 0; - let scriptCount = 0; - - for (const skill of skills) { - const skillName = `${prefix}${skill.name}`; - const skillDir = path.join(skillsDir, skillName); - - const frontmatterObj = buildFrontmatter(skill, skillName); - const frontmatter = generateYamlFrontmatter(frontmatterObj); - - let skillBody = replacePlaceholders(skill.body, provider, commandNames); - - // Replace {{scripts_path}} with provider-aware path to skill's scripts directory - const scriptsPath = provider === 'claude-code' - ? '${CLAUDE_PLUGIN_ROOT}/scripts' - : `${configDir}/skills/${skillName}/scripts`; - skillBody = skillBody.replace(/\{\{scripts_path\}\}/g, scriptsPath); - - if (prefix) skillBody = prefixSkillReferences(skillBody, prefix, allSkillNames); - if (transformBody) skillBody = transformBody(skillBody, skill); - - const content = `${frontmatter}\n\n${skillBody}`; - writeFile(path.join(skillDir, 'SKILL.md'), content); - - // Copy reference files if they exist - if (skill.references && skill.references.length > 0) { - const refDir = path.join(skillDir, 'reference'); - ensureDir(refDir); - for (const ref of skill.references) { - writeFile( - path.join(refDir, `${ref.name}.md`), - replacePlaceholders(ref.content, provider) - ); - refCount++; - } - } - - // Copy script files if they exist - if (skill.scripts && skill.scripts.length > 0) { - const scriptsOutDir = path.join(skillDir, 'scripts'); - ensureDir(scriptsOutDir); - for (const script of skill.scripts) { - writeFile(path.join(scriptsOutDir, script.name), script.content); - scriptCount++; - } - } - } - - const userInvokableCount = skills.filter(s => s.userInvokable).length; - const refInfo = refCount > 0 ? ` (${refCount} reference files)` : ''; - const scriptInfo = scriptCount > 0 ? ` (${scriptCount} script files)` : ''; - const prefixInfo = prefix ? ` [${prefix}prefixed]` : ''; - console.log(`✓ ${displayName}${prefixInfo}: ${skills.length} skills (${userInvokableCount} user-invokable)${refInfo}${scriptInfo}`); -} diff --git a/scripts/lib/utils.js b/scripts/lib/utils.js index 3f672e826..9ed835a30 100644 --- a/scripts/lib/utils.js +++ b/scripts/lib/utils.js @@ -426,13 +426,33 @@ const EXCLUDED_FROM_SUGGESTIONS = new Set([ 'frontend-design', 'i-frontend-design', // deprecated shim ]); +// Sub-commands of /impeccable that should appear in {{available_commands}}. +// These are the commands that audit/critique/etc. reference when suggesting next steps. +const IMPECCABLE_SUB_COMMANDS = [ + 'adapt', 'animate', 'audit', 'bolder', 'clarify', 'colorize', + 'critique', 'delight', 'distill', 'harden', 'layout', 'optimize', + 'overdrive', 'polish', 'quieter', 'shape', 'typeset', +]; + export function replacePlaceholders(content, provider, commandNames = [], allSkillNames = []) { const placeholders = PROVIDER_PLACEHOLDERS[provider] || PROVIDER_PLACEHOLDERS['cursor']; const cmdPrefix = placeholders.command_prefix || '/'; - const commandList = commandNames - .filter(n => !EXCLUDED_FROM_SUGGESTIONS.has(n)) - .map(n => `${cmdPrefix}${n}`) - .join(', '); + + // Build the available_commands list. + // After the v3.0 consolidation, commands are sub-commands of /impeccable. + // If there's only one user-invocable skill (impeccable), generate sub-command references. + // Otherwise fall back to listing skill names (backwards compat for forks). + const nonExcluded = commandNames.filter(n => !EXCLUDED_FROM_SUGGESTIONS.has(n)); + let commandList; + if (nonExcluded.length === 0) { + // Single-skill architecture: list sub-commands as /impeccable + commandList = IMPECCABLE_SUB_COMMANDS + .map(n => `${cmdPrefix}impeccable ${n}`) + .join(', '); + } else { + // Multi-skill architecture (backwards compat) + commandList = nonExcluded.map(n => `${cmdPrefix}${n}`).join(', '); + } let result = content .replace(/\{\{model\}\}/g, placeholders.model) diff --git a/server/index.js b/server/index.js index c9acdcdbb..0e0327167 100644 --- a/server/index.js +++ b/server/index.js @@ -2,8 +2,6 @@ import { serve, file } from "bun"; import path from "node:path"; import { fileURLToPath } from "node:url"; import homepage from "../public/index.html"; -import cheatsheet from "../public/cheatsheet.html"; -import gallery from "../public/gallery.html"; import privacy from "../public/privacy.html"; import { getSkills, @@ -42,15 +40,19 @@ const server = serve({ routes: { "/": homepage, - "/cheatsheet": cheatsheet, - "/gallery": gallery, "/privacy": privacy, + // Legacy URL redirects (kept stable for external links and existing users). + "/cheatsheet": Response.redirect("/docs", 301), + "/gallery": Response.redirect("/visual-mode#try-it-live", 301), + "/skills": Response.redirect("/docs", 301), + "/skills/:id": (req) => Response.redirect(`/docs/${req.params.id}`, 301), + // Generated sub-pages — served directly from the pre-generated files - "/skills": () => serveGenerated(path.join(ROOT_DIR, "public/skills/index.html")), - "/skills/:id": (req) => { + "/docs": () => serveGenerated(path.join(ROOT_DIR, "public/docs/index.html")), + "/docs/:id": (req) => { const id = req.params.id.replace(/[^a-z0-9-]/gi, ""); - return serveGenerated(path.join(ROOT_DIR, `public/skills/${id}.html`)); + return serveGenerated(path.join(ROOT_DIR, `public/docs/${id}.html`)); }, "/anti-patterns": () => serveGenerated(path.join(ROOT_DIR, "public/anti-patterns/index.html")), "/visual-mode": () => serveGenerated(path.join(ROOT_DIR, "public/visual-mode/index.html")), diff --git a/server/lib/api-handlers.js b/server/lib/api-handlers.js index c27ab428d..1714c25a1 100644 --- a/server/lib/api-handlers.js +++ b/server/lib/api-handlers.js @@ -47,10 +47,68 @@ export async function getSkills() { return skills; } -// Read commands (user-invocable skills) +// Read a short tagline for a command from its editorial file +// (content/site/skills/.md). Returns null if the file or tagline is +// missing. Taglines are used by UI surfaces that need a human-friendly +// one-liner; `description` stays optimized for auto-trigger matching. +async function readCommandTagline(id) { + const editorialPath = join(PROJECT_ROOT, "content/site/skills", `${id}.md`); + if (!existsSync(editorialPath)) return null; + try { + const raw = await readFileContent(editorialPath); + const match = raw.match(/^---\n([\s\S]*?)\n---/); + if (!match) return null; + const taglineMatch = match[1].match(/tagline:\s*"([^"]+)"/); + return taglineMatch ? taglineMatch[1] : null; + } catch { + return null; + } +} + +// Read commands. After the v3.0 consolidation, commands are sub-commands of +// /impeccable. Read them from command-metadata.json and include the root +// impeccable skill itself so UI surfaces (cheatsheet, magazine spread) can +// list them. export async function getCommands() { const allSkills = await getSkills(); - return allSkills.filter(s => s.userInvocable); + const metadataPath = join(PROJECT_ROOT, "source/skills/impeccable/scripts/command-metadata.json"); + + const commands = []; + const impeccable = allSkills.find(s => s.name === "impeccable"); + if (impeccable) { + commands.push({ + id: "impeccable", + name: "impeccable", + description: impeccable.description, + tagline: await readCommandTagline("impeccable"), + userInvocable: true, + }); + } + + if (existsSync(metadataPath)) { + try { + const raw = await readFileContent(metadataPath); + const metadata = JSON.parse(raw); + for (const [id, meta] of Object.entries(metadata)) { + commands.push({ + id, + name: id, + description: meta.description, + tagline: await readCommandTagline(id), + userInvocable: true, + }); + } + } catch (error) { + console.error("Error reading command metadata:", error); + } + } + + // Fallback: return just user-invocable skills if no metadata + if (commands.length === 0) { + return allSkills.filter(s => s.userInvocable); + } + + return commands; } // Get command/skill source content diff --git a/skills-lock.json b/skills-lock.json index 9eef3ff1e..f5f7b0666 100644 --- a/skills-lock.json +++ b/skills-lock.json @@ -11,11 +11,6 @@ "sourceType": "github", "computedHash": "b00cb71343fa7e987489ad330e3dd3e504ff893b9ddd2b30cacea93691b78e46" }, - "arrange": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "698fb952e9ef0d2551a5c3421ef61e084934420e0d8371a02efb4f76f21049e8" - }, "audit": { "source": "pbakaus/impeccable", "sourceType": "github", @@ -51,31 +46,11 @@ "sourceType": "github", "computedHash": "ce6fbd844488a326208c1302c73b2865fa4fb20e447b6a06c038315444d6e0c5" }, - "extract": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "1bbe30b5be73a86971f6bccb37daae84aaafceaa6d23429d6a3a0442378ac4ec" - }, - "frontend-design": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "9ebe6c652743fcde8d2ae773f34b6f548dcc8b2e75a3a30936adcd8b95dd2d16" - }, "harden": { "source": "pbakaus/impeccable", "sourceType": "github", "computedHash": "f8ce420b3c78b90707704122264da76514c793ac0e12fb9540ace68d257c231c" }, - "normalize": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "281b7f9e590e252a6aec3f5f83c5ca548c91e8bccb3fd6eee4cc7d5be0becb4d" - }, - "onboard": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "1cbedf70f906150b1b8bb70b61393eaf67e2e1311e1b5e43bde3e47411bcaa2b" - }, "optimize": { "source": "pbakaus/impeccable", "sourceType": "github", @@ -96,11 +71,6 @@ "sourceType": "github", "computedHash": "6066e73875e4770e624641355cc04662ce75d2b1d1a3673e24dcbd0ec8936297" }, - "teach-impeccable": { - "source": "pbakaus/impeccable", - "sourceType": "github", - "computedHash": "b3b5541bb9b0a260af793c7d79c2db4a436c2cd9384be34a4024c7f28af72e62" - }, "typeset": { "source": "pbakaus/impeccable", "sourceType": "github", diff --git a/source/skills/adapt/SKILL.md b/source/skills/adapt/SKILL.md deleted file mode 100644 index 1f1a0d1a9..000000000 --- a/source/skills/adapt/SKILL.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: adapt -description: "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility." -argument-hint: "[target] [context (mobile, tablet, print...)]" -user-invocable: true ---- - -Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. Additionally gather: target platforms/devices and usage contexts. - ---- - -## Assess Adaptation Challenge - -Understand what needs adaptation and why: - -1. **Identify the source context**: - - What was it designed for originally? (Desktop web? Mobile app?) - - What assumptions were made? (Large screen? Mouse input? Fast connection?) - - What works well in current context? - -2. **Understand target context**: - - **Device**: Mobile, tablet, desktop, TV, watch, print? - - **Input method**: Touch, mouse, keyboard, voice, gamepad? - - **Screen constraints**: Size, resolution, orientation? - - **Connection**: Fast wifi, slow 3G, offline? - - **Usage context**: On-the-go vs desk, quick glance vs focused reading? - - **User expectations**: What do users expect on this platform? - -3. **Identify adaptation challenges**: - - What won't fit? (Content, navigation, features) - - What won't work? (Hover states on touch, tiny touch targets) - - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) - -**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. - -## Plan Adaptation Strategy - -Create context-appropriate strategy: - -### Mobile Adaptation (Desktop → Mobile) - -**Layout Strategy**: -- Single column instead of multi-column -- Vertical stacking instead of side-by-side -- Full-width components instead of fixed widths -- Bottom navigation instead of top/side navigation - -**Interaction Strategy**: -- Touch targets 44x44px minimum (not hover-dependent) -- Swipe gestures where appropriate (lists, carousels) -- Bottom sheets instead of dropdowns -- Thumbs-first design (controls within thumb reach) -- Larger tap areas with more spacing - -**Content Strategy**: -- Progressive disclosure (don't show everything at once) -- Prioritize primary content (secondary content in tabs/accordions) -- Shorter text (more concise) -- Larger text (16px minimum) - -**Navigation Strategy**: -- Hamburger menu or bottom navigation -- Reduce navigation complexity -- Sticky headers for context -- Back button in navigation flow - -### Tablet Adaptation (Hybrid Approach) - -**Layout Strategy**: -- Two-column layouts (not single or three-column) -- Side panels for secondary content -- Master-detail views (list + detail) -- Adaptive based on orientation (portrait vs landscape) - -**Interaction Strategy**: -- Support both touch and pointer -- Touch targets 44x44px but allow denser layouts than phone -- Side navigation drawers -- Multi-column forms where appropriate - -### Desktop Adaptation (Mobile → Desktop) - -**Layout Strategy**: -- Multi-column layouts (use horizontal space) -- Side navigation always visible -- Multiple information panels simultaneously -- Fixed widths with max-width constraints (don't stretch to 4K) - -**Interaction Strategy**: -- Hover states for additional information -- Keyboard shortcuts -- Right-click context menus -- Drag and drop where helpful -- Multi-select with Shift/Cmd - -**Content Strategy**: -- Show more information upfront (less progressive disclosure) -- Data tables with many columns -- Richer visualizations -- More detailed descriptions - -### Print Adaptation (Screen → Print) - -**Layout Strategy**: -- Page breaks at logical points -- Remove navigation, footer, interactive elements -- Black and white (or limited color) -- Proper margins for binding - -**Content Strategy**: -- Expand shortened content (show full URLs, hidden sections) -- Add page numbers, headers, footers -- Include metadata (print date, page title) -- Convert charts to print-friendly versions - -### Email Adaptation (Web → Email) - -**Layout Strategy**: -- Narrow width (600px max) -- Single column only -- Inline CSS (no external stylesheets) -- Table-based layouts (for email client compatibility) - -**Interaction Strategy**: -- Large, obvious CTAs (buttons not text links) -- No hover states (not reliable) -- Deep links to web app for complex interactions - -## Implement Adaptations - -Apply changes systematically: - -### Responsive Breakpoints - -Choose appropriate breakpoints: -- Mobile: 320px-767px -- Tablet: 768px-1023px -- Desktop: 1024px+ -- Or content-driven breakpoints (where design breaks) - -### Layout Adaptation Techniques - -- **CSS Grid/Flexbox**: Reflow layouts automatically -- **Container Queries**: Adapt based on container, not viewport -- **`clamp()`**: Fluid sizing between min and max -- **Media queries**: Different styles for different contexts -- **Display properties**: Show/hide elements per context - -### Touch Adaptation - -- Increase touch target sizes (44x44px minimum) -- Add more spacing between interactive elements -- Remove hover-dependent interactions -- Add touch feedback (ripples, highlights) -- Consider thumb zones (easier to reach bottom than top) - -### Content Adaptation - -- Use `display: none` sparingly (still downloads) -- Progressive enhancement (core content first, enhancements on larger screens) -- Lazy loading for off-screen content -- Responsive images (`srcset`, `picture` element) - -### Navigation Adaptation - -- Transform complex nav to hamburger/drawer on mobile -- Bottom nav bar for mobile apps -- Persistent side navigation on desktop -- Breadcrumbs on smaller screens for context - -**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. - -**NEVER**: -- Hide core functionality on mobile (if it matters, make it work) -- Assume desktop = powerful device (consider accessibility, older machines) -- Use different information architecture across contexts (confusing) -- Break user expectations for platform (mobile users expect mobile patterns) -- Forget landscape orientation on mobile/tablet -- Use generic breakpoints blindly (use content-driven breakpoints) -- Ignore touch on desktop (many desktop devices have touch) - -## Verify Adaptations - -Test thoroughly across contexts: - -- **Real devices**: Test on actual phones, tablets, desktops -- **Different orientations**: Portrait and landscape -- **Different browsers**: Safari, Chrome, Firefox, Edge -- **Different OS**: iOS, Android, Windows, macOS -- **Different input methods**: Touch, mouse, keyboard -- **Edge cases**: Very small screens (320px), very large screens (4K) -- **Slow connections**: Test on throttled network - -Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. - diff --git a/source/skills/clarify/SKILL.md b/source/skills/clarify/SKILL.md deleted file mode 100644 index 514a6a143..000000000 --- a/source/skills/clarify/SKILL.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -name: clarify -description: "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing." -argument-hint: "[target]" -user-invocable: true ---- - -Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. Additionally gather: audience technical level and users' mental state in context. - ---- - -## Assess Current Copy - -Identify what makes the text unclear or ineffective: - -1. **Find clarity problems**: - - **Jargon**: Technical terms users won't understand - - **Ambiguity**: Multiple interpretations possible - - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" - - **Length**: Too wordy or too terse - - **Assumptions**: Assuming user knowledge they don't have - - **Missing context**: Users don't know what to do or why - - **Tone mismatch**: Too formal, too casual, or inappropriate for situation - -2. **Understand the context**: - - Who's the audience? (Technical? General? First-time users?) - - What's the user's mental state? (Stressed during error? Confident during success?) - - What's the action? (What do we want users to do?) - - What's the constraint? (Character limits? Space limitations?) - -**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. - -## Plan Copy Improvements - -Create a strategy for clearer communication: - -- **Primary message**: What's the ONE thing users need to know? -- **Action needed**: What should users do next (if anything)? -- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) -- **Constraints**: Length limits, brand voice, localization considerations - -**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. - -## Improve Copy Systematically - -Refine text across these common areas: - -### Error Messages -**Bad**: "Error 403: Forbidden" -**Good**: "You don't have permission to view this page. Contact your admin for access." - -**Bad**: "Invalid input" -**Good**: "Email addresses need an @ symbol. Try: name@example.com" - -**Principles**: -- Explain what went wrong in plain language -- Suggest how to fix it -- Don't blame the user -- Include examples when helpful -- Link to help/support if applicable - -### Form Labels & Instructions -**Bad**: "DOB (MM/DD/YYYY)" -**Good**: "Date of birth" (with placeholder showing format) - -**Bad**: "Enter value here" -**Good**: "Your email address" or "Company name" - -**Principles**: -- Use clear, specific labels (not generic placeholders) -- Show format expectations with examples -- Explain why you're asking (when not obvious) -- Put instructions before the field, not after -- Keep required field indicators clear - -### Button & CTA Text -**Bad**: "Click here" | "Submit" | "OK" -**Good**: "Create account" | "Save changes" | "Got it, thanks" - -**Principles**: -- Describe the action specifically -- Use active voice (verb + noun) -- Match user's mental model -- Be specific ("Save" is better than "OK") - -### Help Text & Tooltips -**Bad**: "This is the username field" -**Good**: "Choose a username. You can change this later in Settings." - -**Principles**: -- Add value (don't just repeat the label) -- Answer the implicit question ("What is this?" or "Why do you need this?") -- Keep it brief but complete -- Link to detailed docs if needed - -### Empty States -**Bad**: "No items" -**Good**: "No projects yet. Create your first project to get started." - -**Principles**: -- Explain why it's empty (if not obvious) -- Show next action clearly -- Make it welcoming, not dead-end - -### Success Messages -**Bad**: "Success" -**Good**: "Settings saved! Your changes will take effect immediately." - -**Principles**: -- Confirm what happened -- Explain what happens next (if relevant) -- Be brief but complete -- Match the user's emotional moment (celebrate big wins) - -### Loading States -**Bad**: "Loading..." (for 30+ seconds) -**Good**: "Analyzing your data... this usually takes 30-60 seconds" - -**Principles**: -- Set expectations (how long?) -- Explain what's happening (when it's not obvious) -- Show progress when possible -- Offer escape hatch if appropriate ("Cancel") - -### Confirmation Dialogs -**Bad**: "Are you sure?" -**Good**: "Delete 'Project Alpha'? This can't be undone." - -**Principles**: -- State the specific action -- Explain consequences (especially for destructive actions) -- Use clear button labels ("Delete project" not "Yes") -- Don't overuse confirmations (only for risky actions) - -### Navigation & Wayfinding -**Bad**: Generic labels like "Items" | "Things" | "Stuff" -**Good**: Specific labels like "Your projects" | "Team members" | "Settings" - -**Principles**: -- Be specific and descriptive -- Use language users understand (not internal jargon) -- Make hierarchy clear -- Consider information scent (breadcrumbs, current location) - -## Apply Clarity Principles - -Every piece of copy should follow these rules: - -1. **Be specific**: "Enter email" not "Enter value" -2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) -3. **Be active**: "Save changes" not "Changes will be saved" -4. **Be human**: "Oops, something went wrong" not "System error encountered" -5. **Be helpful**: Tell users what to do, not just what happened -6. **Be consistent**: Use same terms throughout (don't vary for variety) - -**NEVER**: -- Use jargon without explanation -- Blame users ("You made an error" → "This field is required") -- Be vague ("Something went wrong" without explanation) -- Use passive voice unnecessarily -- Write overly long explanations (be concise) -- Use humor for errors (be empathetic instead) -- Assume technical knowledge -- Vary terminology (pick one term and stick with it) -- Repeat information (headers restating intros, redundant explanations) -- Use placeholders as the only labels (they disappear when users type) - -## Verify Improvements - -Test that copy improvements work: - -- **Comprehension**: Can users understand without context? -- **Actionability**: Do users know what to do next? -- **Brevity**: Is it as short as possible while remaining clear? -- **Consistency**: Does it match terminology elsewhere? -- **Tone**: Is it appropriate for the situation? - -Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. - diff --git a/source/skills/harden/SKILL.md b/source/skills/harden/SKILL.md deleted file mode 100644 index 5aafb5f4e..000000000 --- a/source/skills/harden/SKILL.md +++ /dev/null @@ -1,389 +0,0 @@ ---- -name: harden -description: "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues." -argument-hint: "[target]" -user-invocable: true ---- - -Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. - -## Assess Hardening Needs - -Identify weaknesses and edge cases: - -1. **Test with extreme inputs**: - - Very long text (names, descriptions, titles) - - Very short text (empty, single character) - - Special characters (emoji, RTL text, accents) - - Large numbers (millions, billions) - - Many items (1000+ list items, 50+ options) - - No data (empty states) - -2. **Test error scenarios**: - - Network failures (offline, slow, timeout) - - API errors (400, 401, 403, 404, 500) - - Validation errors - - Permission errors - - Rate limiting - - Concurrent operations - -3. **Test internationalization**: - - Long translations (German is often 30% longer than English) - - RTL languages (Arabic, Hebrew) - - Character sets (Chinese, Japanese, Korean, emoji) - - Date/time formats - - Number formats (1,000 vs 1.000) - - Currency symbols - -**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. - -## Hardening Dimensions - -Systematically improve resilience: - -### Text Overflow & Wrapping - -**Long text handling**: -```css -/* Single line with ellipsis */ -.truncate { - overflow: hidden; - text-overflow: ellipsis; - white-space: nowrap; -} - -/* Multi-line with clamp */ -.line-clamp { - display: -webkit-box; - -webkit-line-clamp: 3; - -webkit-box-orient: vertical; - overflow: hidden; -} - -/* Allow wrapping */ -.wrap { - word-wrap: break-word; - overflow-wrap: break-word; - hyphens: auto; -} -``` - -**Flex/Grid overflow**: -```css -/* Prevent flex items from overflowing */ -.flex-item { - min-width: 0; /* Allow shrinking below content size */ - overflow: hidden; -} - -/* Prevent grid items from overflowing */ -.grid-item { - min-width: 0; - min-height: 0; -} -``` - -**Responsive text sizing**: -- Use `clamp()` for fluid typography -- Set minimum readable sizes (14px on mobile) -- Test text scaling (zoom to 200%) -- Ensure containers expand with text - -### Internationalization (i18n) - -**Text expansion**: -- Add 30-40% space budget for translations -- Use flexbox/grid that adapts to content -- Test with longest language (usually German) -- Avoid fixed widths on text containers - -```jsx -// ❌ Bad: Assumes short English text - - -// ✅ Good: Adapts to content - -``` - -**RTL (Right-to-Left) support**: -```css -/* Use logical properties */ -margin-inline-start: 1rem; /* Not margin-left */ -padding-inline: 1rem; /* Not padding-left/right */ -border-inline-end: 1px solid; /* Not border-right */ - -/* Or use dir attribute */ -[dir="rtl"] .arrow { transform: scaleX(-1); } -``` - -**Character set support**: -- Use UTF-8 encoding everywhere -- Test with Chinese/Japanese/Korean (CJK) characters -- Test with emoji (they can be 2-4 bytes) -- Handle different scripts (Latin, Cyrillic, Arabic, etc.) - -**Date/Time formatting**: -```javascript -// ✅ Use Intl API for proper formatting -new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 -new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 - -new Intl.NumberFormat('en-US', { - style: 'currency', - currency: 'USD' -}).format(1234.56); // $1,234.56 -``` - -**Pluralization**: -```javascript -// ❌ Bad: Assumes English pluralization -`${count} item${count !== 1 ? 's' : ''}` - -// ✅ Good: Use proper i18n library -t('items', { count }) // Handles complex plural rules -``` - -### Error Handling - -**Network errors**: -- Show clear error messages -- Provide retry button -- Explain what happened -- Offer offline mode (if applicable) -- Handle timeout scenarios - -```jsx -// Error states with recovery -{error && ( - -

      Failed to load data. {error.message}

      - -       -)} -``` - -**Form validation errors**: -- Inline errors near fields -- Clear, specific messages -- Suggest corrections -- Don't block submission unnecessarily -- Preserve user input on error - -**API errors**: -- Handle each status code appropriately - - 400: Show validation errors - - 401: Redirect to login - - 403: Show permission error - - 404: Show not found state - - 429: Show rate limit message - - 500: Show generic error, offer support - -**Graceful degradation**: -- Core functionality works without JavaScript -- Images have alt text -- Progressive enhancement -- Fallbacks for unsupported features - -### Edge Cases & Boundary Conditions - -**Empty states**: -- No items in list -- No search results -- No notifications -- No data to display -- Provide clear next action - -**Loading states**: -- Initial load -- Pagination load -- Refresh -- Show what's loading ("Loading your projects...") -- Time estimates for long operations - -**Large datasets**: -- Pagination or virtual scrolling -- Search/filter capabilities -- Performance optimization -- Don't load all 10,000 items at once - -**Concurrent operations**: -- Prevent double-submission (disable button while loading) -- Handle race conditions -- Optimistic updates with rollback -- Conflict resolution - -**Permission states**: -- No permission to view -- No permission to edit -- Read-only mode -- Clear explanation of why - -**Browser compatibility**: -- Polyfills for modern features -- Fallbacks for unsupported CSS -- Feature detection (not browser detection) -- Test in target browsers - -### Onboarding & First-Run Experience - -Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: - -**Empty states**: Every zero-data screen needs: -- What will appear here (description or illustration) -- Why it matters to the user -- Clear CTA to create the first item or start from a template -- Visual interest (not just blank space with "No items yet") - -Empty state types to handle: -- **First use**: emphasize value, provide templates -- **User cleared**: light touch, easy to recreate -- **No results**: suggest a different query, offer to clear filters -- **No permissions**: explain why, how to get access - -**First-run experience**: Get users to their "aha moment" as quickly as possible. -- Show, don't tell -- working examples over descriptions -- Progressive disclosure -- teach one thing at a time, not everything upfront -- Make onboarding optional -- let experienced users skip -- Provide smart defaults so required setup is minimal - -**Feature discovery**: Teach features when users need them, not upfront. -- Contextual tooltips at point of use (brief, dismissable, one-time) -- Badges or indicators on new or unused features -- Celebrate activation events quietly (a toast, not a modal) - -**NEVER**: -- Force long onboarding before users can touch the product -- Show the same tooltip repeatedly (track and respect dismissals) -- Block the entire UI during a guided tour -- Create separate tutorial modes disconnected from the real product -- Design empty states that just say "No items" with no next action - -### Input Validation & Sanitization - -**Client-side validation**: -- Required fields -- Format validation (email, phone, URL) -- Length limits -- Pattern matching -- Custom validation rules - -**Server-side validation** (always): -- Never trust client-side only -- Validate and sanitize all inputs -- Protect against injection attacks -- Rate limiting - -**Constraint handling**: -```html - - - - Letters and numbers only, up to 100 characters - -``` - -### Accessibility Resilience - -**Keyboard navigation**: -- All functionality accessible via keyboard -- Logical tab order -- Focus management in modals -- Skip links for long content - -**Screen reader support**: -- Proper ARIA labels -- Announce dynamic changes (live regions) -- Descriptive alt text -- Semantic HTML - -**Motion sensitivity**: -```css -@media (prefers-reduced-motion: reduce) { - * { - animation-duration: 0.01ms !important; - animation-iteration-count: 1 !important; - transition-duration: 0.01ms !important; - } -} -``` - -**High contrast mode**: -- Test in Windows high contrast mode -- Don't rely only on color -- Provide alternative visual cues - -### Performance Resilience - -**Slow connections**: -- Progressive image loading -- Skeleton screens -- Optimistic UI updates -- Offline support (service workers) - -**Memory leaks**: -- Clean up event listeners -- Cancel subscriptions -- Clear timers/intervals -- Abort pending requests on unmount - -**Throttling & Debouncing**: -```javascript -// Debounce search input -const debouncedSearch = debounce(handleSearch, 300); - -// Throttle scroll handler -const throttledScroll = throttle(handleScroll, 100); -``` - -## Testing Strategies - -**Manual testing**: -- Test with extreme data (very long, very short, empty) -- Test in different languages -- Test offline -- Test slow connection (throttle to 3G) -- Test with screen reader -- Test keyboard-only navigation -- Test on old browsers - -**Automated testing**: -- Unit tests for edge cases -- Integration tests for error scenarios -- E2E tests for critical paths -- Visual regression tests -- Accessibility tests (axe, WAVE) - -**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. - -**NEVER**: -- Assume perfect input (validate everything) -- Ignore internationalization (design for global) -- Leave error messages generic ("Error occurred") -- Forget offline scenarios -- Trust client-side validation alone -- Use fixed widths for text -- Assume English-length text -- Block entire interface when one component errors - -## Verify Hardening - -Test thoroughly with edge cases: - -- **Long text**: Try names with 100+ characters -- **Emoji**: Use emoji in all text fields -- **RTL**: Test with Arabic or Hebrew -- **CJK**: Test with Chinese/Japanese/Korean -- **Network issues**: Disable internet, throttle connection -- **Large datasets**: Test with 1000+ items -- **Concurrent actions**: Click submit 10 times rapidly -- **Errors**: Force API errors, test all error states -- **Empty**: Remove all data, test empty states - -Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. - diff --git a/source/skills/impeccable/SKILL.md b/source/skills/impeccable/SKILL.md index 62595c806..2bd1bad97 100644 --- a/source/skills/impeccable/SKILL.md +++ b/source/skills/impeccable/SKILL.md @@ -1,15 +1,19 @@ --- name: impeccable -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. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system." -argument-hint: "[craft|teach|extract]" +description: "Design fluency for frontend interfaces. Build distinctive, production-grade web components, pages, artifacts, posters, and applications with high design quality. Also handles: critique/review/evaluate designs, audit accessibility/performance/responsive, polish finishing touches, improve typography/fonts/readability, fix layout/spacing/hierarchy, add animation/transitions/motion, adapt for mobile/tablet/responsive, simplify/declutter/distill, amplify bland/generic/safe designs, tone down loud/overwhelming designs, add color to gray/monochromatic interfaces, improve UX copy/labels/error messages, harden for production with edge cases/i18n/errors/empty states, optimize slow/laggy performance, plan UX before coding, extract design tokens, or push boundaries with shaders/physics/scroll effects. Commands: craft, teach, extract, pin, audit, critique, polish, shape, adapt, animate, bolder, quieter, colorize, clarify, delight, distill, harden, layout, optimize, overdrive, typeset." +argument-hint: "[command] [target]" user-invocable: true +allowed-tools: + - Bash(npx impeccable *) license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. --- +This skill guides creation and editing/iteration of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic details and creative choices. + BEFORE doing any design work, run this one-time maintenance step. Tell the user: -> **Impeccable was updated.** A few skills were renamed or merged in this version (e.g. `/arrange` is now `/layout`, `/normalize` was folded into `/polish`). I'll clean up the old skill files so they don't clutter your project. This only runs once after an update. +> **Impeccable 3.0 consolidation.** All standalone commands (/audit, /polish, /critique, etc.) are now accessed through /impeccable (e.g., `/impeccable audit`). I'll clean up the old standalone skill files. Use `/impeccable pin ` to restore shortcuts for commands you use often. Then run: @@ -22,8 +26,6 @@ If the script removed files, briefly confirm what was cleaned up. If it found no After running the script, delete this entire section (from `` through `` inclusive) from THIS file so it does not run again until the next update. Save the file. -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. @@ -33,7 +35,7 @@ Design skills produce generic output without project context. You MUST have conf - **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. +Individual sub-commands may require additional context. Check the commands' 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. @@ -269,7 +271,7 @@ Make interactions feel fast. Use optimistic UI: update immediately, sync later. 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. +Review the DON'T guidelines above. They are the fingerprints of AI-generated work. --- @@ -283,82 +285,96 @@ Remember: {{model}} is capable of extraordinary creative work. Don't hold back. --- -## Craft Mode +## Command Router -If this skill is invoked with the argument "craft" (e.g., `{{command_prefix}}impeccable craft [feature description]`), follow the [craft flow](reference/craft.md). Pass any additional arguments as the feature description. +This skill supports sub-commands. Parse the first word of the argument string to determine routing. + +### Routing rules + +1. **No argument at all** (user typed just `{{command_prefix}}impeccable`): Display the command menu below, then ask the user what they'd like to do. +2. **First word matches a sub-command**: Route to that command's reference file. Everything after the sub-command name is the target. +3. **First word does NOT match any sub-command**: This is a general design invocation. Follow the Design Direction and Implementation Principles above, using the full argument string as context. + +### Command menu (display when invoked with no argument) + +> **Available commands:** +> +> **Build & Plan** +> `{{command_prefix}}impeccable craft [feature]` - Shape, then build a feature end-to-end +> `{{command_prefix}}impeccable shape [feature]` - Plan UX/UI before writing code +> `{{command_prefix}}impeccable teach` - Set up design context for this project (one-time) +> `{{command_prefix}}impeccable extract [target]` - Pull reusable tokens and components into design system +> +> **Evaluate** +> `{{command_prefix}}impeccable critique [target]` - UX design review with heuristic scoring +> `{{command_prefix}}impeccable audit [target]` - Technical quality checks (a11y, perf, responsive) +> +> **Refine** +> `{{command_prefix}}impeccable polish [target]` - Final quality pass before shipping +> `{{command_prefix}}impeccable bolder [target]` - Amplify safe/bland designs +> `{{command_prefix}}impeccable quieter [target]` - Tone down aggressive/overstimulating designs +> `{{command_prefix}}impeccable distill [target]` - Strip to essence, remove complexity +> `{{command_prefix}}impeccable harden [target]` - Production-ready: errors, i18n, edge cases +> +> **Enhance** +> `{{command_prefix}}impeccable animate [target]` - Add purposeful animations and motion +> `{{command_prefix}}impeccable colorize [target]` - Add strategic color to monochromatic UIs +> `{{command_prefix}}impeccable typeset [target]` - Improve typography hierarchy and fonts +> `{{command_prefix}}impeccable layout [target]` - Fix spacing, rhythm, and visual hierarchy +> `{{command_prefix}}impeccable delight [target]` - Add personality and memorable touches +> `{{command_prefix}}impeccable overdrive [target]` - Push past conventional limits +> +> **Fix** +> `{{command_prefix}}impeccable clarify [target]` - Improve UX copy, labels, and error messages +> `{{command_prefix}}impeccable adapt [target]` - Adapt for different devices and screen sizes +> `{{command_prefix}}impeccable optimize [target]` - Diagnose and fix UI performance +> +> **Manage** +> `{{command_prefix}}impeccable pin ` - Create a standalone shortcut (e.g., pin audit creates {{command_prefix}}audit) +> `{{command_prefix}}impeccable unpin ` - Remove a pinned shortcut +> +> Or use `{{command_prefix}}impeccable [description]` directly to apply design principles to any task. + +### Sub-command reference table + +When a sub-command is matched, load the linked reference and follow its instructions. The design principles, guidelines, and Context Gathering Protocol from this skill are already loaded. Do NOT re-invoke {{command_prefix}}impeccable. + +| Command | Reference | Summary | +|---------|-----------|---------| +| `craft` | [craft](reference/craft.md) | Full shape-then-build flow with visual iteration | +| `teach` | [teach](reference/teach.md) | One-time setup: gather design context for the project | +| `extract` | [extract](reference/extract.md) | Pull reusable tokens and components into design system | +| `shape` | [shape](reference/shape.md) | Plan UX and UI before writing code (produces a design brief) | +| `critique` | [critique](reference/critique.md) | UX design review with heuristic scoring and persona testing | +| `audit` | [audit](reference/audit.md) | Technical quality checks across a11y, perf, theming, responsive, anti-patterns | +| `polish` | [polish](reference/polish.md) | Final quality pass: alignment, spacing, consistency, micro-details | +| `bolder` | [bolder](reference/bolder.md) | Amplify safe or boring designs for more visual impact | +| `quieter` | [quieter](reference/quieter.md) | Tone down visually aggressive or overstimulating designs | +| `distill` | [distill](reference/distill.md) | Strip designs to their essence, remove unnecessary complexity | +| `harden` | [harden](reference/harden.md) | Production-ready: error handling, i18n, edge cases, onboarding | +| `animate` | [animate](reference/animate.md) | Add purposeful animations and micro-interactions | +| `colorize` | [colorize](reference/colorize.md) | Add strategic color to monochromatic interfaces | +| `typeset` | [typeset](reference/typeset.md) | Improve typography: fonts, hierarchy, sizing, readability | +| `layout` | [layout](reference/layout.md) | Improve layout, spacing, and visual rhythm | +| `delight` | [delight](reference/delight.md) | Add personality, joy, and memorable touches | +| `overdrive` | [overdrive](reference/overdrive.md) | Push interfaces past conventional limits | +| `clarify` | [clarify](reference/clarify.md) | Improve UX copy, labels, error messages, and microcopy | +| `adapt` | [adapt](reference/adapt.md) | Adapt designs across screen sizes, devices, and platforms | +| `optimize` | [optimize](reference/optimize.md) | Diagnose and fix UI performance issues | --- -## Teach Mode +## Pin / Unpin -If this skill is invoked with the argument "teach" (e.g., `{{command_prefix}}impeccable teach`), skip all design work above and instead run the teach flow below. This is a one-time setup that gathers design context for the project. +If this skill is invoked with `pin ` or `unpin `: -### Step 1: Explore the Codebase +**pin** creates a lightweight standalone skill so you can invoke the command directly (e.g., `{{command_prefix}}audit` instead of `{{command_prefix}}impeccable audit`). -Before asking questions, thoroughly scan the project to discover what you can: +**unpin** removes a previously pinned shortcut. -- **README and docs**: Project purpose, target audience, any stated goals -- **Package.json / config files**: Tech stack, dependencies, existing design libraries -- **Existing components**: Current design patterns, spacing, typography in use -- **Brand assets**: Logos, favicons, color values already defined -- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales -- **Any style guides or brand documentation** - -Note what you've learned and what remains unclear. - -### Step 2: Ask UX-Focused Questions - -{{ask_instruction}} Focus only on what you couldn't infer from the codebase: - -#### Users & Purpose -- Who uses this? What's their context when using it? -- What job are they trying to get done? -- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) - -#### Brand & Personality -- How would you describe the brand personality in 3 words? -- Any reference sites or apps that capture the right feel? What specifically about them? -- What should this explicitly NOT look like? Any anti-references? - -#### Aesthetic Preferences -- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) -- Light mode, dark mode, or both? -- Any colors that must be used or avoided? - -#### Accessibility & Inclusion -- Specific accessibility requirements? (WCAG level, known user needs) -- Considerations for reduced motion, color blindness, or other accommodations? - -Skip questions where the answer is already clear from the codebase exploration. - -### Step 3: Write Design Context - -Synthesize your findings and the user's answers into a `## Design Context` section: - -```markdown -## Design Context - -### Users -[Who they are, their context, the job to be done] - -### Brand Personality -[Voice, tone, 3-word personality, emotional goals] - -### Aesthetic Direction -[Visual tone, references, anti-references, theme] - -### Design Principles -[3-5 principles derived from the conversation that should guide all design decisions] +Run: +```bash +node {{scripts_path}}/pin.mjs ``` -Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. - -Then {{ask_instruction}} whether they'd also like the Design Context appended to {{config_file}}. If yes, append or update the section there as well. - -Confirm completion and summarize the key design principles that will now guide all future work. - ---- - -## Extract Mode - -If this skill is invoked with the argument "extract" (e.g., `{{command_prefix}}impeccable extract [target]`), follow the [extract flow](reference/extract.md). Pass any additional arguments as the extraction target. +Report what the script did. If it succeeded, confirm the new shortcut is available (for pin) or removed (for unpin). diff --git a/source/skills/impeccable/reference/adapt.md b/source/skills/impeccable/reference/adapt.md new file mode 100644 index 000000000..249653d4c --- /dev/null +++ b/source/skills/impeccable/reference/adapt.md @@ -0,0 +1,190 @@ +> **Additional context needed**: target platforms/devices and usage contexts. + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + + +--- + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. diff --git a/source/skills/animate/SKILL.md b/source/skills/impeccable/reference/animate.md similarity index 91% rename from source/skills/animate/SKILL.md rename to source/skills/impeccable/reference/animate.md index c5be7d04a..688ccc358 100644 --- a/source/skills/animate/SKILL.md +++ b/source/skills/impeccable/reference/animate.md @@ -1,15 +1,7 @@ ---- -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." -argument-hint: "[target]" -user-invocable: true ---- +> **Additional context needed**: performance constraints. Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. Additionally gather: performance constraints. --- diff --git a/source/skills/audit/SKILL.md b/source/skills/impeccable/reference/audit.md similarity index 85% rename from source/skills/audit/SKILL.md rename to source/skills/impeccable/reference/audit.md index bb9121888..7c3e2cf68 100644 --- a/source/skills/audit/SKILL.md +++ b/source/skills/impeccable/reference/audit.md @@ -1,16 +1,3 @@ ---- -name: audit -description: "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review." -argument-hint: "[area (feature, page, component...)]" -user-invocable: true ---- - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. - ---- - Run systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address. This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation. @@ -65,7 +52,7 @@ Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the ### 5. Anti-Patterns (CRITICAL) -Check against ALL the **DON'T** guidelines in the impeccable skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). +Check against ALL the **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). **Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design) @@ -127,13 +114,13 @@ List recommended commands in priority order (P0 first, then P1, then P2): 1. **[P?] `{{command_prefix}}command-name`** — Brief description (specific context from audit findings) 2. **[P?] `{{command_prefix}}command-name`** — Brief description (specific context) -**Rules**: Only recommend commands from: {{available_commands}}. Map findings to the most appropriate command. End with `{{command_prefix}}polish` as the final step if any fixes were recommended. +**Rules**: Only recommend commands from: {{available_commands}}. Map findings to the most appropriate command. End with `{{command_prefix}}impeccable polish` as the final step if any fixes were recommended. After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `{{command_prefix}}audit` after fixes to see your score improve. +> Re-run `{{command_prefix}}impeccable audit` after fixes to see your score improve. **IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters. diff --git a/source/skills/bolder/SKILL.md b/source/skills/impeccable/reference/bolder.md similarity index 87% rename from source/skills/bolder/SKILL.md rename to source/skills/impeccable/reference/bolder.md index 07b1cfc99..992ae4235 100644 --- a/source/skills/bolder/SKILL.md +++ b/source/skills/impeccable/reference/bolder.md @@ -1,15 +1,5 @@ ---- -name: bolder -description: "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character." -argument-hint: "[target]" -user-invocable: true ---- - Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. --- @@ -35,7 +25,7 @@ If any of these are unclear from the codebase, {{ask_instruction}} **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. -**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the impeccable skill before proceeding. Bold means distinctive, not "more effects." +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold. They're generic. Review ALL the DON'T guidelines from the parent impeccable skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects." ## Plan Amplification @@ -53,7 +43,7 @@ Create a strategy to increase impact while maintaining coherence: Systematically increase impact across these dimensions: ### Typography Amplification -- **Replace generic fonts**: Swap system fonts for distinctive choices (see impeccable skill for inspiration) +- **Replace generic fonts**: Swap system fonts for distinctive choices (see the parent skill's typography guidelines and [typography.md](typography.md) for inspiration) - **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) - **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 - **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) diff --git a/source/skills/impeccable/reference/clarify.md b/source/skills/impeccable/reference/clarify.md new file mode 100644 index 000000000..dc116e745 --- /dev/null +++ b/source/skills/impeccable/reference/clarify.md @@ -0,0 +1,174 @@ +> **Additional context needed**: audience technical level and users' mental state in context. + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + + +--- + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. diff --git a/source/skills/critique/reference/cognitive-load.md b/source/skills/impeccable/reference/cognitive-load.md similarity index 100% rename from source/skills/critique/reference/cognitive-load.md rename to source/skills/impeccable/reference/cognitive-load.md diff --git a/source/skills/colorize/SKILL.md b/source/skills/impeccable/reference/colorize.md similarity index 90% rename from source/skills/colorize/SKILL.md rename to source/skills/impeccable/reference/colorize.md index 067713958..363d2aae2 100644 --- a/source/skills/colorize/SKILL.md +++ b/source/skills/impeccable/reference/colorize.md @@ -1,15 +1,7 @@ ---- -name: colorize -description: "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette." -argument-hint: "[target]" -user-invocable: true ---- +> **Additional context needed**: existing brand colors. Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. Additionally gather: existing brand colors. --- diff --git a/source/skills/impeccable/reference/craft.md b/source/skills/impeccable/reference/craft.md index 2bc10df79..4374144f4 100644 --- a/source/skills/impeccable/reference/craft.md +++ b/source/skills/impeccable/reference/craft.md @@ -4,11 +4,11 @@ Build a feature with impeccable UX and UI quality through a structured process: ## Step 1: Shape the Design -Run {{command_prefix}}shape, passing along whatever feature description the user provided. +Run {{command_prefix}}impeccable shape, passing along whatever feature description the user provided. Wait for the design brief to be fully confirmed before proceeding. The brief is your blueprint, and every implementation decision should trace back to it. -If the user has already run {{command_prefix}}shape and has a confirmed design brief, skip this step and use the existing brief. +If the user has already run {{command_prefix}}impeccable shape and has a confirmed design brief, skip this step and use the existing brief. ## Step 2: Load References diff --git a/source/skills/critique/SKILL.md b/source/skills/impeccable/reference/critique.md similarity index 86% rename from source/skills/critique/SKILL.md rename to source/skills/impeccable/reference/critique.md index de859a69e..7e9136baa 100644 --- a/source/skills/critique/SKILL.md +++ b/source/skills/impeccable/reference/critique.md @@ -1,19 +1,6 @@ ---- -name: critique -description: "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component." -argument-hint: "[area (feature, page, component...)]" -user-invocable: true -allowed-tools: - - Bash(npx impeccable *) ---- +> **Additional context needed**: what the interface is trying to accomplish. -## STEPS - -### Step 1: Preparation - -Invoke {{command_prefix}}impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run {{command_prefix}}impeccable teach first. Additionally gather: what the interface is trying to accomplish. - -### Step 2: Gather Assessments +### Gather Assessments Launch two independent assessments. **Neither must see the other's output** to avoid bias. @@ -31,11 +18,11 @@ document.title = '[LLM] ' + document.title; ``` Think like a design director. Evaluate: -**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines in the impeccable skill. Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? +**AI Slop Detection (CRITICAL)**: Does this look like every other AI-generated interface? Review against ALL **DON'T** guidelines from the parent impeccable skill (already loaded in this context). Check for AI color palette, gradient text, dark glows, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. **The test**: If someone said "AI made this," would you believe them immediately? **Holistic Design Review**: visual hierarchy (eye flow, primary action clarity), information architecture (structure, grouping, cognitive load), emotional resonance (does it match brand and audience?), discoverability (are interactive elements obvious?), composition (balance, whitespace, rhythm), typography (hierarchy, readability, font choices), color (purposeful use, cohesion, accessibility), states & edge cases (empty, loading, error, success), microcopy (clarity, tone, helpfulness). -**Cognitive Load** (consult [cognitive-load](reference/cognitive-load.md)): +**Cognitive Load** (consult [cognitive-load](cognitive-load.md)): - Run the 8-item cognitive load checklist. Report failure count: 0-1 = low (good), 2-3 = moderate, 4+ = critical. - Count visible options at each decision point. If >4, flag it. - Check for progressive disclosure: is complexity revealed only when needed? @@ -45,7 +32,7 @@ Think like a design director. Evaluate: - **Peak-end rule**: Is the most intense moment positive? Does the experience end well? - **Emotional valleys**: Check for anxiety spikes at high-stakes moments (payment, delete, commit). Are there design interventions (progress indicators, reassurance copy, undo options)? -**Nielsen's Heuristics** (consult [heuristics-scoring](reference/heuristics-scoring.md)): +**Nielsen's Heuristics** (consult [heuristics-scoring](heuristics-scoring.md)): Score each of the 10 heuristics 0-4. This scoring will be presented in the report. Return structured findings covering: AI slop verdict, heuristic scores, cognitive load assessment, what's working (2-3 items), priority issues (3-5 with what/why/fix), minor observations, and provocative questions. @@ -95,14 +82,14 @@ For multi-view targets, inject on 3-5 representative pages. If injection fails, Return: CLI findings (JSON), browser console findings (if applicable), and any false positives noted. -### Step 3: Generate Combined Critique Report +### Generate Combined Critique Report Synthesize both assessments into a single report. Do NOT simply concatenate. Weave the findings together, noting where the LLM review and detector agree, where the detector caught issues the LLM missed, and where detector findings are false positives. Structure your feedback as a design director would: #### Design Health Score -> *Consult [heuristics-scoring](reference/heuristics-scoring.md)* +> *Consult [heuristics-scoring](heuristics-scoring.md)* Present the Nielsen's 10 heuristics scores as a table: @@ -141,14 +128,14 @@ Highlight 2-3 things done well. Be specific about why they work. #### Priority Issues The 3-5 most impactful design problems, ordered by importance. -For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](reference/heuristics-scoring.md) for severity definitions): +For each issue, tag with **P0-P3 severity** (consult [heuristics-scoring](heuristics-scoring.md) for severity definitions): - **[P?] What**: Name the problem clearly - **Why it matters**: How this hurts users or undermines goals - **Fix**: What to do about it (be concrete) - **Suggested command**: Which command could address this (from: {{available_commands}}) #### Persona Red Flags -> *Consult [personas](reference/personas.md)* +> *Consult [personas](personas.md)* Auto-select 2-3 personas most relevant to this interface type (use the selection table in the reference). If `{{config_file}}` contains a `## Design Context` section from `impeccable teach`, also generate 1-2 project-specific personas from the audience/brand info. @@ -177,7 +164,7 @@ Provocative questions that might unlock better solutions: - Prioritize ruthlessly. If everything is important, nothing is. - Don't soften criticism. Developers need honest feedback to ship great design. -### Step 4: Ask the User +### Ask the User **After presenting findings**, use targeted questions based on what was actually found. {{ask_instruction}} These answers will shape the action plan. @@ -197,7 +184,7 @@ Ask questions along these lines (adapt to the specific findings; do NOT ask gene - Offer concrete options, not open-ended prompts. - If findings are straightforward (e.g., only 1-2 clear issues), skip questions and go directly to Step 5. -### Step 5: Recommended Actions +### Recommended Actions **After receiving the user's answers**, present a prioritized action summary reflecting the user's priorities and scope from Step 4. @@ -217,10 +204,10 @@ List recommended commands in priority order, based on the user's answers: - Skip commands that would address zero issues - If the user chose a limited scope, only include items within that scope - If the user marked areas as off-limits, exclude commands that would touch those areas -- End with `{{command_prefix}}polish` as the final step if any fixes were recommended +- End with `{{command_prefix}}impeccable polish` as the final step if any fixes were recommended After presenting the summary, tell the user: > You can ask me to run these one at a time, all at once, or in any order you prefer. > -> Re-run `{{command_prefix}}critique` after fixes to see your score improve. +> Re-run `{{command_prefix}}impeccable critique` after fixes to see your score improve. diff --git a/source/skills/delight/SKILL.md b/source/skills/impeccable/reference/delight.md similarity index 92% rename from source/skills/delight/SKILL.md rename to source/skills/impeccable/reference/delight.md index fd74d41eb..c3df1420e 100644 --- a/source/skills/delight/SKILL.md +++ b/source/skills/impeccable/reference/delight.md @@ -1,15 +1,7 @@ ---- -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." -argument-hint: "[target]" -user-invocable: true ---- +> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant). Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant). --- diff --git a/source/skills/distill/SKILL.md b/source/skills/impeccable/reference/distill.md similarity index 90% rename from source/skills/distill/SKILL.md rename to source/skills/impeccable/reference/distill.md index eee17b88c..c66418318 100644 --- a/source/skills/distill/SKILL.md +++ b/source/skills/impeccable/reference/distill.md @@ -1,15 +1,5 @@ ---- -name: distill -description: "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused." -argument-hint: "[target]" -user-invocable: true ---- - Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. --- diff --git a/source/skills/impeccable/reference/harden.md b/source/skills/impeccable/reference/harden.md new file mode 100644 index 000000000..af8b8a703 --- /dev/null +++ b/source/skills/impeccable/reference/harden.md @@ -0,0 +1,381 @@ +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

      Failed to load data. {error.message}

      + +       +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Onboarding & First-Run Experience + +Production-ready features work for first-time users, not just power users. Design the paths that get new users to value: + +**Empty states**: Every zero-data screen needs: +- What will appear here (description or illustration) +- Why it matters to the user +- Clear CTA to create the first item or start from a template +- Visual interest (not just blank space with "No items yet") + +Empty state types to handle: +- **First use**: emphasize value, provide templates +- **User cleared**: light touch, easy to recreate +- **No results**: suggest a different query, offer to clear filters +- **No permissions**: explain why, how to get access + +**First-run experience**: Get users to their "aha moment" as quickly as possible. +- Show, don't tell -- working examples over descriptions +- Progressive disclosure -- teach one thing at a time, not everything upfront +- Make onboarding optional -- let experienced users skip +- Provide smart defaults so required setup is minimal + +**Feature discovery**: Teach features when users need them, not upfront. +- Contextual tooltips at point of use (brief, dismissable, one-time) +- Badges or indicators on new or unused features +- Celebrate activation events quietly (a toast, not a modal) + +**NEVER**: +- Force long onboarding before users can touch the product +- Show the same tooltip repeatedly (track and respect dismissals) +- Block the entire UI during a guided tour +- Create separate tutorial modes disconnected from the real product +- Design empty states that just say "No items" with no next action + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. diff --git a/source/skills/critique/reference/heuristics-scoring.md b/source/skills/impeccable/reference/heuristics-scoring.md similarity index 100% rename from source/skills/critique/reference/heuristics-scoring.md rename to source/skills/impeccable/reference/heuristics-scoring.md diff --git a/source/skills/impeccable/reference/layout.md b/source/skills/impeccable/reference/layout.md new file mode 100644 index 000000000..cd6b778e7 --- /dev/null +++ b/source/skills/impeccable/reference/layout.md @@ -0,0 +1,114 @@ +Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. + + +--- + +## Assess Current Layout + +Analyze what's weak about the current spatial design: + +1. **Spacing**: + - Is spacing consistent or arbitrary? (Random padding/margin values) + - Is all spacing the same? (Equal padding everywhere = no rhythm) + - Are related elements grouped tightly, with generous space between groups? + +2. **Visual hierarchy**: + - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? + - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) + - Does whitespace guide the eye to what matters? + +3. **Grid & structure**: + - Is there a clear underlying structure, or does the layout feel random? + - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) + - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) + +4. **Rhythm & variety**: + - Does the layout have visual rhythm? (Alternating tight/generous spacing) + - Is every section structured the same way? (Monotonous repetition) + - Are there intentional moments of surprise or emphasis? + +5. **Density**: + - Is the layout too cramped? (Not enough breathing room) + - Is the layout too sparse? (Excessive whitespace without purpose) + - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) + +**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. + +## Plan Layout Improvements + +Consult the [spatial design reference](spatial-design.md) for detailed guidance on grids, rhythm, and container queries. + +Create a systematic plan: + +- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. +- **Hierarchy strategy**: How will space communicate importance? +- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. +- **Rhythm**: Where should spacing be tight vs generous? + +## Improve Layout Systematically + +### Establish a Spacing System + +- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. +- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` +- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks +- Apply `clamp()` for fluid spacing that breathes on larger screens + +### Create Visual Rhythm + +- **Tight grouping** for related elements (8-12px between siblings) +- **Generous separation** between distinct sections (48-96px) +- **Varied spacing** within sections — not every row needs the same gap +- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense + +### Choose the Right Layout Tool + +- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. +- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. +- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. +- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. +- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. + +### Break Card Grid Monotony + +- Don't default to card grids for everything — spacing and alignment create visual grouping naturally +- Use cards only when content is truly distinct and actionable — never nest cards inside cards +- Vary card sizes, span columns, or mix cards with non-card content to break repetition + +### Strengthen Visual Hierarchy + +- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. +- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). +- Create clear content groupings through proximity and separation. + +### Manage Depth & Elevation + +- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) +- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle +- Use elevation to reinforce hierarchy, not as decoration + +### Optical Adjustments + +- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. + +**NEVER**: +- Use arbitrary spacing values outside your scale +- Make all spacing equal — variety creates hierarchy +- Wrap everything in cards — not everything needs a container +- Nest cards inside cards — use spacing and dividers for hierarchy within +- Use identical card grids everywhere (icon + heading + text, repeated) +- Center everything — left-aligned with asymmetry feels more designed +- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. +- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job +- Use arbitrary z-index values (999, 9999) — build a semantic scale + +## Verify Layout Improvements + +- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? +- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? +- **Hierarchy**: Is the most important content obvious within 2 seconds? +- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? +- **Consistency**: Is the spacing system applied uniformly? +- **Responsiveness**: Does the layout adapt gracefully across screen sizes? + +Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/source/skills/impeccable/reference/optimize.md b/source/skills/impeccable/reference/optimize.md new file mode 100644 index 000000000..4abf575ec --- /dev/null +++ b/source/skills/impeccable/reference/optimize.md @@ -0,0 +1,258 @@ +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. diff --git a/source/skills/overdrive/SKILL.md b/source/skills/impeccable/reference/overdrive.md similarity index 77% rename from source/skills/overdrive/SKILL.md rename to source/skills/impeccable/reference/overdrive.md index 93d44c757..15d76818d 100644 --- a/source/skills/overdrive/SKILL.md +++ b/source/skills/impeccable/reference/overdrive.md @@ -1,10 +1,3 @@ ---- -name: overdrive -description: "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary." -argument-hint: "[target]" -user-invocable: true ---- - Start your response with: ``` @@ -12,19 +5,15 @@ Start your response with: 》》》 Entering overdrive mode... ``` -Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. +Push an interface past conventional limits. This isn't just about visual effects. It's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. - -**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. +**EXTRA IMPORTANT FOR THIS COMMAND**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate. ### Propose Before Building -This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: +This command has the highest potential to misfire. Do NOT jump straight into implementation. You MUST: -1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. +1. **Think through 2-3 different directions**: consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like. 2. **{{ask_instruction}}** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity). 3. Only proceed with the direction the user confirms. @@ -32,7 +21,7 @@ Skipping this step risks building something embarrassing that needs to be thrown ### Iterate with Browser Automation -Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. +Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right, check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone. --- @@ -90,7 +79,7 @@ Organized by what you're trying to achieve, not by technology name. - **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start. - **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission. -**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. +**NOTE**: This command is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary. ## Implement with Discipline @@ -127,7 +116,7 @@ The gap between "cool" and "extraordinary" is in the last 20% of refinement: the - Ship effects that cause jank on mid-range devices - Use bleeding-edge APIs without a functional fallback - Add sound without explicit user opt-in -- Use technical ambition to mask weak design fundamentals — fix those first with other skills +- Use technical ambition to mask weak design fundamentals; fix those first with other commands - Layer multiple competing extraordinary moments — focus creates impact, excess creates noise ## Verify the Result diff --git a/source/skills/critique/reference/personas.md b/source/skills/impeccable/reference/personas.md similarity index 100% rename from source/skills/critique/reference/personas.md rename to source/skills/impeccable/reference/personas.md diff --git a/source/skills/impeccable/reference/polish.md b/source/skills/impeccable/reference/polish.md new file mode 100644 index 000000000..597c68847 --- /dev/null +++ b/source/skills/impeccable/reference/polish.md @@ -0,0 +1,212 @@ +> **Additional context needed**: 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. + +## Design System Discovery + +Before polishing, understand the system you are polishing toward: + +1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. +2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? +3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. + +If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. + +## 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) +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens + +## 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 + +## Clean Up + +After polishing, ensure code quality: + +- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. +- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. +- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. +- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. + +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. diff --git a/source/skills/quieter/SKILL.md b/source/skills/impeccable/reference/quieter.md similarity index 88% rename from source/skills/quieter/SKILL.md rename to source/skills/impeccable/reference/quieter.md index 3985b772a..507a9eac4 100644 --- a/source/skills/quieter/SKILL.md +++ b/source/skills/impeccable/reference/quieter.md @@ -1,15 +1,5 @@ ---- -name: quieter -description: "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic." -argument-hint: "[target]" -user-invocable: true ---- - Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. --- diff --git a/source/skills/shape/SKILL.md b/source/skills/impeccable/reference/shape.md similarity index 77% rename from source/skills/shape/SKILL.md rename to source/skills/impeccable/reference/shape.md index cb62822b7..eea66ccfa 100644 --- a/source/skills/shape/SKILL.md +++ b/source/skills/impeccable/reference/shape.md @@ -1,25 +1,12 @@ ---- -name: shape -description: "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written." -argument-hint: "[feature to shape]" -user-invocable: true ---- +Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. -## MANDATORY PREPARATION +**Scope**: Design planning only. This command does NOT write code. It produces the thinking that makes code good. -Invoke {{command_prefix}}impeccable, which contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding. If no design context exists yet, you MUST run {{command_prefix}}impeccable teach first. - ---- - -Shape the UX and UI for a feature before any code is written. This skill produces a **design brief**: a structured artifact that guides implementation through discovery, not guesswork. - -**Scope**: Design planning only. This skill does NOT write code. It produces the thinking that makes code good. - -**Output**: A design brief that can be handed off to {{command_prefix}}impeccable craft, {{command_prefix}}impeccable, or any other implementation skill. +**Output**: A design brief that can be handed off to {{command_prefix}}impeccable craft, or directly to {{command_prefix}}impeccable for freeform implementation. ## Philosophy -Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise. +Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This command inverts that: understand deeply first, so implementation is precise. ## Phase 1: Discovery Interview @@ -57,7 +44,7 @@ Ask these questions in conversation, adapting based on answers. Don't dump them ## Phase 2: Design Brief -After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this skill complete. +After the interview, synthesize everything into a structured design brief. Present it to the user for confirmation before considering this command complete. ### Brief Structure @@ -92,4 +79,4 @@ Anything unresolved that the implementer should resolve during build. {{ask_instruction}} Get explicit confirmation of the brief before finishing. If the user disagrees with any part, revisit the relevant discovery questions. -Once confirmed, the brief is complete. The user can now hand it to {{command_prefix}}impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use {{command_prefix}}impeccable craft instead, which runs this skill internally.) +Once confirmed, the brief is complete. The user can now hand it to {{command_prefix}}impeccable, or use it to guide any other implementation approach. (If the user wants the full discovery-then-build flow in one step, they should use {{command_prefix}}impeccable craft instead, which runs this command internally.) diff --git a/source/skills/impeccable/reference/teach.md b/source/skills/impeccable/reference/teach.md new file mode 100644 index 000000000..b56a55e19 --- /dev/null +++ b/source/skills/impeccable/reference/teach.md @@ -0,0 +1,67 @@ +# Teach Flow + +One-time setup that gathers design context for a project. Design without context produces generic output, so every other command reads this file before doing any work. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +{{ask_instruction}} Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. + +Then {{ask_instruction}} whether they'd also like the Design Context appended to {{config_file}}. If yes, append or update the section there as well. + +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/source/skills/impeccable/reference/typeset.md b/source/skills/impeccable/reference/typeset.md new file mode 100644 index 000000000..2e49ab6c0 --- /dev/null +++ b/source/skills/impeccable/reference/typeset.md @@ -0,0 +1,105 @@ +Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. + + +--- + +## Assess Current Typography + +Analyze what's weak or generic about the current type: + +1. **Font choices**: + - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) + - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) + - Are there too many font families? (More than 2-3 is almost always a mess) + +2. **Hierarchy**: + - Can you tell headings from body from captions at a glance? + - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) + - Are weight contrasts strong enough? (Medium vs Regular is barely visible) + +3. **Sizing & scale**: + - Is there a consistent type scale, or are sizes arbitrary? + - Does body text meet minimum readability? (16px+) + - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) + +4. **Readability**: + - Are line lengths comfortable? (45-75 characters ideal) + - Is line-height appropriate for the font and context? + - Is there enough contrast between text and background? + +5. **Consistency**: + - Are the same elements styled the same way throughout? + - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) + - Is letter-spacing intentional or default everywhere? + +**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. + +## Plan Typography Improvements + +Consult the [typography reference](typography.md) for detailed guidance on scales, pairing, and loading strategies. + +Create a systematic plan: + +- **Font selection**: Do fonts need replacing? What fits the brand/context? +- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy +- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) +- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements + +## Improve Typography Systematically + +### Font Selection + +If fonts need replacing: +- Choose fonts that reflect the brand personality +- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights +- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) + +### Establish Hierarchy + +Build a clear type scale: +- **5 sizes cover most needs**: caption, secondary, body, subheading, heading +- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) +- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone +- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need +- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed + +### Fix Readability + +- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) +- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) +- Increase line-height slightly for light-on-dark text +- Ensure body text is at least 16px / 1rem + +### Refine Details + +- Use `tabular-nums` for data tables and numbers that should align +- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text +- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) +- Set `font-kerning: normal` and consider OpenType features where appropriate + +### Weight Consistency + +- Define clear roles for each weight and stick to them +- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) +- Load only the weights you actually use (each weight adds to page load) + +**NEVER**: +- Use more than 2-3 font families +- Pick sizes arbitrarily — commit to a scale +- Set body text below 16px +- Use decorative/display fonts for body text +- Disable browser zoom (`user-scalable=no`) +- Use `px` for font sizes — use `rem` to respect user settings +- Default to Inter/Roboto/Open Sans when personality matters +- Pair fonts that are similar but not identical (two geometric sans-serifs) + +## Verify Typography Improvements + +- **Hierarchy**: Can you identify heading vs body vs caption instantly? +- **Readability**: Is body text comfortable to read in long passages? +- **Consistency**: Are same-role elements styled identically throughout? +- **Personality**: Does the typography reflect the brand? +- **Performance**: Are web fonts loading efficiently without layout shift? +- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? + +Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/source/skills/impeccable/scripts/cleanup-deprecated.mjs b/source/skills/impeccable/scripts/cleanup-deprecated.mjs index 5b8a2177c..0194aa8fc 100644 --- a/source/skills/impeccable/scripts/cleanup-deprecated.mjs +++ b/source/skills/impeccable/scripts/cleanup-deprecated.mjs @@ -21,14 +21,34 @@ import { existsSync, readFileSync, writeFileSync, rmSync, readdirSync, statSync, lstatSync, unlinkSync } from 'node:fs'; import { join, resolve } from 'node:path'; -// Skills that were renamed, merged, or folded in v2.0 and v2.1. +// Skills that were renamed, merged, or folded in v2.0, v2.1, and v3.0. const DEPRECATED_NAMES = [ - 'frontend-design', // renamed to impeccable (v2.0) - 'teach-impeccable', // folded into /impeccable teach (v2.0) - 'arrange', // renamed to layout (v2.1) - 'normalize', // merged into polish (v2.1) - 'onboard', // merged into harden (v2.1) - 'extract', // merged into /impeccable extract (v2.1) + // v2.0 renames + 'frontend-design', // renamed to impeccable + 'teach-impeccable', // folded into /impeccable teach + // v2.1 merges + 'arrange', // renamed to layout + 'normalize', // merged into polish + 'onboard', // merged into harden + 'extract', // merged into /impeccable extract + // v3.0 consolidation: all standalone skills -> /impeccable sub-commands + 'adapt', + 'animate', + 'audit', + 'bolder', + 'clarify', + 'colorize', + 'critique', + 'delight', + 'distill', + 'harden', + 'layout', + 'optimize', + 'overdrive', + 'polish', + 'quieter', + 'shape', + 'typeset', ]; // All known harness directories that may contain a skills/ subfolder. diff --git a/source/skills/impeccable/scripts/command-metadata.json b/source/skills/impeccable/scripts/command-metadata.json new file mode 100644 index 000000000..38806f3f5 --- /dev/null +++ b/source/skills/impeccable/scripts/command-metadata.json @@ -0,0 +1,82 @@ +{ + "craft": { + "description": "Full shape-then-build flow with visual iteration. Plans the UX with /impeccable shape, loads the right reference files, then builds and iterates visually until the result is delightful. Use when building a new feature end-to-end.", + "argumentHint": "[feature description]" + }, + "teach": { + "description": "One-time setup that gathers design context for a project. Runs a short discovery interview and writes the answers to .impeccable.md. Every other command reads this file before doing work. Use once per project.", + "argumentHint": "" + }, + "extract": { + "description": "Pull reusable patterns, components, and design tokens into the design system. Identifies repeated patterns and consolidates them. Use when you have drift across the codebase and want to bring things back to a consistent system.", + "argumentHint": "[target]" + }, + "adapt": { + "description": "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.", + "argumentHint": "[target] [context (mobile, tablet, print...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "audit": { + "description": "Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.", + "argumentHint": "[area (feature, page, component...)]" + }, + "bolder": { + "description": "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.", + "argumentHint": "[target]" + }, + "clarify": { + "description": "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.", + "argumentHint": "[target]" + }, + "colorize": { + "description": "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.", + "argumentHint": "[target]" + }, + "critique": { + "description": "Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.", + "argumentHint": "[area (feature, page, component...)]" + }, + "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.", + "argumentHint": "[target]" + }, + "distill": { + "description": "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.", + "argumentHint": "[target]" + }, + "harden": { + "description": "Make interfaces production-ready: error handling, empty states, onboarding flows, i18n, text overflow, and edge case management. Use when the user asks to harden, make production-ready, handle edge cases, add error states, design empty states, improve onboarding, or fix overflow and i18n issues.", + "argumentHint": "[target]" + }, + "layout": { + "description": "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.", + "argumentHint": "[target]" + }, + "optimize": { + "description": "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.", + "argumentHint": "[target]" + }, + "overdrive": { + "description": "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.", + "argumentHint": "[target]" + }, + "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.", + "argumentHint": "[target]" + }, + "quieter": { + "description": "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.", + "argumentHint": "[target]" + }, + "shape": { + "description": "Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.", + "argumentHint": "[feature to shape]" + }, + "typeset": { + "description": "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.", + "argumentHint": "[target]" + } +} diff --git a/source/skills/impeccable/scripts/pin.mjs b/source/skills/impeccable/scripts/pin.mjs new file mode 100644 index 000000000..2abfc6050 --- /dev/null +++ b/source/skills/impeccable/scripts/pin.mjs @@ -0,0 +1,214 @@ +#!/usr/bin/env node +/** + * Pin/unpin sub-commands as standalone skill shortcuts. + * + * Usage: + * node /pin.mjs pin + * node /pin.mjs unpin + * + * `pin audit` creates a lightweight /audit skill that redirects to /impeccable audit. + * `unpin audit` removes that shortcut. + * + * The script discovers harness directories (.claude/skills, .cursor/skills, etc.) + * in the project root and creates/removes the pin in all of them. + */ + +import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync, readdirSync } from 'node:fs'; +import { join, resolve, dirname } from 'node:path'; +import { fileURLToPath } from 'node:url'; + +const __dirname = dirname(fileURLToPath(import.meta.url)); + +// All known harness directories +const HARNESS_DIRS = [ + '.claude', '.cursor', '.gemini', '.codex', '.agents', + '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev', +]; + +// Valid sub-command names +const VALID_COMMANDS = [ + 'craft', 'teach', 'extract', 'shape', + 'critique', 'audit', + 'polish', 'bolder', 'quieter', 'distill', 'harden', + 'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive', + 'clarify', 'adapt', 'optimize', +]; + +// Marker to identify pinned skills (so unpin doesn't delete user skills) +const PIN_MARKER = ''; + +/** + * Walk up from startDir to find a project root. + */ +function findProjectRoot(startDir = process.cwd()) { + let dir = resolve(startDir); + while (dir !== '/') { + if ( + existsSync(join(dir, 'package.json')) || + existsSync(join(dir, '.git')) || + existsSync(join(dir, 'skills-lock.json')) + ) { + return dir; + } + const parent = resolve(dir, '..'); + if (parent === dir) break; + dir = parent; + } + return resolve(startDir); +} + +/** + * Find harness skill directories that have an impeccable skill installed. + */ +function findHarnessDirs(projectRoot) { + const dirs = []; + for (const harness of HARNESS_DIRS) { + const skillsDir = join(projectRoot, harness, 'skills'); + // Only pin in harness dirs that already have impeccable installed + const impeccableDir = join(skillsDir, 'impeccable'); + if (existsSync(impeccableDir) || existsSync(join(skillsDir, 'i-impeccable'))) { + dirs.push(skillsDir); + } + } + return dirs; +} + +/** + * Load command metadata (descriptions for pinned skills). + */ +function loadCommandMetadata() { + const metadataPath = join(__dirname, 'command-metadata.json'); + if (existsSync(metadataPath)) { + return JSON.parse(readFileSync(metadataPath, 'utf-8')); + } + return {}; +} + +/** + * Generate a pinned skill's SKILL.md content. + */ +function generatePinnedSkill(command, metadata) { + const desc = metadata[command]?.description || `Shortcut for /impeccable ${command}.`; + const hint = metadata[command]?.argumentHint || '[target]'; + + return `--- +name: ${command} +description: "${desc}" +argument-hint: "${hint}" +user-invocable: true +--- + +${PIN_MARKER} + +This is a pinned shortcut for \`{{command_prefix}}impeccable ${command}\`. + +Invoke {{command_prefix}}impeccable ${command}, passing along any arguments provided here, and follow its instructions. +`; +} + +/** + * Pin a command: create shortcut skill in all harness dirs. + */ +function pin(command, projectRoot) { + const metadata = loadCommandMetadata(); + const harnessDirs = findHarnessDirs(projectRoot); + + if (harnessDirs.length === 0) { + console.log('No harness directories with impeccable installed found.'); + return false; + } + + const content = generatePinnedSkill(command, metadata); + let created = 0; + + for (const skillsDir of harnessDirs) { + // Check if skill already exists (and isn't a pin) + const skillDir = join(skillsDir, command); + if (existsSync(skillDir)) { + const existingMd = join(skillDir, 'SKILL.md'); + if (existsSync(existingMd)) { + const existing = readFileSync(existingMd, 'utf-8'); + if (!existing.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (non-pinned skill already exists)`); + continue; + } + } + } + + mkdirSync(skillDir, { recursive: true }); + writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8'); + console.log(` + ${skillDir}`); + created++; + } + + if (created > 0) { + console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`); + console.log(`You can now use /${command} directly.`); + } + + return created > 0; +} + +/** + * Unpin a command: remove shortcut skill from all harness dirs. + */ +function unpin(command, projectRoot) { + const harnessDirs = findHarnessDirs(projectRoot); + let removed = 0; + + for (const skillsDir of harnessDirs) { + const skillDir = join(skillsDir, command); + if (!existsSync(skillDir)) continue; + + const skillMd = join(skillDir, 'SKILL.md'); + if (!existsSync(skillMd)) continue; + + // Safety: only remove if it's a pinned skill + const content = readFileSync(skillMd, 'utf-8'); + if (!content.includes(PIN_MARKER)) { + console.log(` SKIP: ${skillDir} (not a pinned skill)`); + continue; + } + + rmSync(skillDir, { recursive: true, force: true }); + console.log(` - ${skillDir}`); + removed++; + } + + if (removed > 0) { + console.log(`\nUnpinned '${command}' from ${removed} location(s).`); + console.log(`Use /impeccable ${command} to access it.`); + } else { + console.log(`No pinned '${command}' shortcut found.`); + } + + return removed > 0; +} + +// --- CLI --- +const [,, action, command] = process.argv; + +if (!action || !command) { + console.log('Usage: node pin.mjs '); + console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +if (action !== 'pin' && action !== 'unpin') { + console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`); + process.exit(1); +} + +if (!VALID_COMMANDS.includes(command)) { + console.error(`Unknown command: ${command}`); + console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`); + process.exit(1); +} + +const root = findProjectRoot(); + +if (action === 'pin') { + pin(command, root); +} else { + unpin(command, root); +} diff --git a/source/skills/layout/SKILL.md b/source/skills/layout/SKILL.md deleted file mode 100644 index 747fb66be..000000000 --- a/source/skills/layout/SKILL.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -name: layout -description: "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition." -argument-hint: "[target]" -user-invocable: true ---- - -Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions. - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. - ---- - -## Assess Current Layout - -Analyze what's weak about the current spatial design: - -1. **Spacing**: - - Is spacing consistent or arbitrary? (Random padding/margin values) - - Is all spacing the same? (Equal padding everywhere = no rhythm) - - Are related elements grouped tightly, with generous space between groups? - -2. **Visual hierarchy**: - - Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - - Does whitespace guide the eye to what matters? - -3. **Grid & structure**: - - Is there a clear underlying structure, or does the layout feel random? - - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule) - -4. **Rhythm & variety**: - - Does the layout have visual rhythm? (Alternating tight/generous spacing) - - Is every section structured the same way? (Monotonous repetition) - - Are there intentional moments of surprise or emphasis? - -5. **Density**: - - Is the layout too cramped? (Not enough breathing room) - - Is the layout too sparse? (Excessive whitespace without purpose) - - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air) - -**CRITICAL**: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention. - -## Plan Layout Improvements - -Consult the [spatial design reference](reference/spatial-design.md) from the impeccable skill for detailed guidance on grids, rhythm, and container queries. - -Create a systematic plan: - -- **Spacing system**: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency. -- **Hierarchy strategy**: How will space communicate importance? -- **Layout approach**: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts. -- **Rhythm**: Where should spacing be tight vs generous? - -## Improve Layout Systematically - -### Establish a Spacing System - -- Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers. -- Name tokens semantically if using custom properties: `--space-xs` through `--space-xl`, not `--spacing-8` -- Use `gap` for sibling spacing instead of margins — eliminates margin collapse hacks -- Apply `clamp()` for fluid spacing that breathes on larger screens - -### Create Visual Rhythm - -- **Tight grouping** for related elements (8-12px between siblings) -- **Generous separation** between distinct sections (48-96px) -- **Varied spacing** within sections — not every row needs the same gap -- **Asymmetric compositions** — break the predictable centered-content pattern when it makes sense - -### Choose the Right Layout Tool - -- **Use Flexbox for 1D layouts**: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks. -- **Use Grid for 2D layouts**: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control. -- **Don't default to Grid** when Flexbox with `flex-wrap` would be simpler and more flexible. -- Use `repeat(auto-fit, minmax(280px, 1fr))` for responsive grids without breakpoints. -- Use named grid areas (`grid-template-areas`) for complex page layouts — redefine at breakpoints. - -### Break Card Grid Monotony - -- Don't default to card grids for everything — spacing and alignment create visual grouping naturally -- Use cards only when content is truly distinct and actionable — never nest cards inside cards -- Vary card sizes, span columns, or mix cards with non-card content to break repetition - -### Strengthen Visual Hierarchy - -- Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient. -- Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation). -- Create clear content groupings through proximity and separation. - -### Manage Depth & Elevation - -- Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip) -- Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle -- Use elevation to reinforce hierarchy, not as decoration - -### Optical Adjustments - -- If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively. - -**NEVER**: -- Use arbitrary spacing values outside your scale -- Make all spacing equal — variety creates hierarchy -- Wrap everything in cards — not everything needs a container -- Nest cards inside cards — use spacing and dividers for hierarchy within -- Use identical card grids everywhere (icon + heading + text, repeated) -- Center everything — left-aligned with asymmetry feels more designed -- Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers. -- Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job -- Use arbitrary z-index values (999, 9999) — build a semantic scale - -## Verify Layout Improvements - -- **Squint test**: Can you identify primary, secondary, and groupings with blurred vision? -- **Rhythm**: Does the page have a satisfying beat of tight and generous spacing? -- **Hierarchy**: Is the most important content obvious within 2 seconds? -- **Breathing room**: Does the layout feel comfortable, not cramped or wasteful? -- **Consistency**: Is the spacing system applied uniformly? -- **Responsiveness**: Does the layout adapt gracefully across screen sizes? - -Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional. diff --git a/source/skills/optimize/SKILL.md b/source/skills/optimize/SKILL.md deleted file mode 100644 index ad3a40552..000000000 --- a/source/skills/optimize/SKILL.md +++ /dev/null @@ -1,266 +0,0 @@ ---- -name: optimize -description: "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience." -argument-hint: "[target]" -user-invocable: true ---- - -Identify and fix performance issues to create faster, smoother user experiences. - -## Assess Performance Issues - -Understand current performance and identify problems: - -1. **Measure current state**: - - **Core Web Vitals**: LCP, FID/INP, CLS scores - - **Load time**: Time to interactive, first contentful paint - - **Bundle size**: JavaScript, CSS, image sizes - - **Runtime performance**: Frame rate, memory usage, CPU usage - - **Network**: Request count, payload sizes, waterfall - -2. **Identify bottlenecks**: - - What's slow? (Initial load? Interactions? Animations?) - - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) - - How bad is it? (Perceivable? Annoying? Blocking?) - - Who's affected? (All users? Mobile only? Slow connections?) - -**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. - -## Optimization Strategy - -Create systematic improvement plan: - -### Loading Performance - -**Optimize Images**: -- Use modern formats (WebP, AVIF) -- Proper sizing (don't load 3000px image for 300px display) -- Lazy loading for below-fold images -- Responsive images (`srcset`, `picture` element) -- Compress images (80-85% quality is usually imperceptible) -- Use CDN for faster delivery - -```html -Hero image -``` - -**Reduce JavaScript Bundle**: -- Code splitting (route-based, component-based) -- Tree shaking (remove unused code) -- Remove unused dependencies -- Lazy load non-critical code -- Use dynamic imports for large components - -```javascript -// Lazy load heavy component -const HeavyChart = lazy(() => import('./HeavyChart')); -``` - -**Optimize CSS**: -- Remove unused CSS -- Critical CSS inline, rest async -- Minimize CSS files -- Use CSS containment for independent regions - -**Optimize Fonts**: -- Use `font-display: swap` or `optional` -- Subset fonts (only characters you need) -- Preload critical fonts -- Use system fonts when appropriate -- Limit font weights loaded - -```css -@font-face { - font-family: 'CustomFont'; - src: url('/fonts/custom.woff2') format('woff2'); - font-display: swap; /* Show fallback immediately */ - unicode-range: U+0020-007F; /* Basic Latin only */ -} -``` - -**Optimize Loading Strategy**: -- Critical resources first (async/defer non-critical) -- Preload critical assets -- Prefetch likely next pages -- Service worker for offline/caching -- HTTP/2 or HTTP/3 for multiplexing - -### Rendering Performance - -**Avoid Layout Thrashing**: -```javascript -// ❌ Bad: Alternating reads and writes (causes reflows) -elements.forEach(el => { - const height = el.offsetHeight; // Read (forces layout) - el.style.height = height * 2; // Write -}); - -// ✅ Good: Batch reads, then batch writes -const heights = elements.map(el => el.offsetHeight); // All reads -elements.forEach((el, i) => { - el.style.height = heights[i] * 2; // All writes -}); -``` - -**Optimize Rendering**: -- Use CSS `contain` property for independent regions -- Minimize DOM depth (flatter is faster) -- Reduce DOM size (fewer elements) -- Use `content-visibility: auto` for long lists -- Virtual scrolling for very long lists (react-window, react-virtualized) - -**Reduce Paint & Composite**: -- Use `transform` and `opacity` for animations (GPU-accelerated) -- Avoid animating layout properties (width, height, top, left) -- Use `will-change` sparingly for known expensive operations -- Minimize paint areas (smaller is faster) - -### Animation Performance - -**GPU Acceleration**: -```css -/* ✅ GPU-accelerated (fast) */ -.animated { - transform: translateX(100px); - opacity: 0.5; -} - -/* ❌ CPU-bound (slow) */ -.animated { - left: 100px; - width: 300px; -} -``` - -**Smooth 60fps**: -- Target 16ms per frame (60fps) -- Use `requestAnimationFrame` for JS animations -- Debounce/throttle scroll handlers -- Use CSS animations when possible -- Avoid long-running JavaScript during animations - -**Intersection Observer**: -```javascript -// Efficiently detect when elements enter viewport -const observer = new IntersectionObserver((entries) => { - entries.forEach(entry => { - if (entry.isIntersecting) { - // Element is visible, lazy load or animate - } - }); -}); -``` - -### React/Framework Optimization - -**React-specific**: -- Use `memo()` for expensive components -- `useMemo()` and `useCallback()` for expensive computations -- Virtualize long lists -- Code split routes -- Avoid inline function creation in render -- Use React DevTools Profiler - -**Framework-agnostic**: -- Minimize re-renders -- Debounce expensive operations -- Memoize computed values -- Lazy load routes and components - -### Network Optimization - -**Reduce Requests**: -- Combine small files -- Use SVG sprites for icons -- Inline small critical assets -- Remove unused third-party scripts - -**Optimize APIs**: -- Use pagination (don't load everything) -- GraphQL to request only needed fields -- Response compression (gzip, brotli) -- HTTP caching headers -- CDN for static assets - -**Optimize for Slow Connections**: -- Adaptive loading based on connection (navigator.connection) -- Optimistic UI updates -- Request prioritization -- Progressive enhancement - -## Core Web Vitals Optimization - -### Largest Contentful Paint (LCP < 2.5s) -- Optimize hero images -- Inline critical CSS -- Preload key resources -- Use CDN -- Server-side rendering - -### First Input Delay (FID < 100ms) / INP (< 200ms) -- Break up long tasks -- Defer non-critical JavaScript -- Use web workers for heavy computation -- Reduce JavaScript execution time - -### Cumulative Layout Shift (CLS < 0.1) -- Set dimensions on images and videos -- Don't inject content above existing content -- Use `aspect-ratio` CSS property -- Reserve space for ads/embeds -- Avoid animations that cause layout shifts - -```css -/* Reserve space for image */ -.image-container { - aspect-ratio: 16 / 9; -} -``` - -## Performance Monitoring - -**Tools to use**: -- Chrome DevTools (Lighthouse, Performance panel) -- WebPageTest -- Core Web Vitals (Chrome UX Report) -- Bundle analyzers (webpack-bundle-analyzer) -- Performance monitoring (Sentry, DataDog, New Relic) - -**Key metrics**: -- LCP, FID/INP, CLS (Core Web Vitals) -- Time to Interactive (TTI) -- First Contentful Paint (FCP) -- Total Blocking Time (TBT) -- Bundle size -- Request count - -**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. - -**NEVER**: -- Optimize without measuring (premature optimization) -- Sacrifice accessibility for performance -- Break functionality while optimizing -- Use `will-change` everywhere (creates new layers, uses memory) -- Lazy load above-fold content -- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) -- Forget about mobile performance (often slower devices, slower connections) - -## Verify Improvements - -Test that optimizations worked: - -- **Before/after metrics**: Compare Lighthouse scores -- **Real user monitoring**: Track improvements for real users -- **Different devices**: Test on low-end Android, not just flagship iPhone -- **Slow connections**: Throttle to 3G, test experience -- **No regressions**: Ensure functionality still works -- **User perception**: Does it *feel* faster? - -Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. - diff --git a/source/skills/polish/SKILL.md b/source/skills/polish/SKILL.md deleted file mode 100644 index 0cd35a7a5..000000000 --- a/source/skills/polish/SKILL.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -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." -argument-hint: "[target]" -user-invocable: true ---- - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach 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. - -## Design System Discovery - -Before polishing, understand the system you are polishing toward: - -1. **Find the design system**: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. -2. **Note the conventions**: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? -3. **Identify drift**: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. - -If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. - -## 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) -- Create new one-off components when design system equivalents exist -- Hard-code values that should use design tokens - -## 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 - -## Clean Up - -After polishing, ensure code quality: - -- **Replace custom implementations**: If the design system provides a component you reimplemented, switch to the shared version. -- **Remove orphaned code**: Delete unused styles, components, or files made obsolete by polish. -- **Consolidate tokens**: If you introduced new values, check whether they should be tokens. -- **Verify DRYness**: Look for duplication introduced during polishing and consolidate. - -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. - diff --git a/source/skills/typeset/SKILL.md b/source/skills/typeset/SKILL.md deleted file mode 100644 index c76f77406..000000000 --- a/source/skills/typeset/SKILL.md +++ /dev/null @@ -1,115 +0,0 @@ ---- -name: typeset -description: "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography." -argument-hint: "[target]" -user-invocable: true ---- - -Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type. - -## MANDATORY PREPARATION - -Invoke {{command_prefix}}impeccable — 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 {{command_prefix}}impeccable teach first. - ---- - -## Assess Current Typography - -Analyze what's weak or generic about the current type: - -1. **Font choices**: - - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults) - - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface) - - Are there too many font families? (More than 2-3 is almost always a mess) - -2. **Hierarchy**: - - Can you tell headings from body from captions at a glance? - - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy) - - Are weight contrasts strong enough? (Medium vs Regular is barely visible) - -3. **Sizing & scale**: - - Is there a consistent type scale, or are sizes arbitrary? - - Does body text meet minimum readability? (16px+) - - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings) - -4. **Readability**: - - Are line lengths comfortable? (45-75 characters ideal) - - Is line-height appropriate for the font and context? - - Is there enough contrast between text and background? - -5. **Consistency**: - - Are the same elements styled the same way throughout? - - Are font weights used consistently? (Not bold in one section, semibold in another for the same role) - - Is letter-spacing intentional or default everywhere? - -**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting. - -## Plan Typography Improvements - -Consult the [typography reference](reference/typography.md) from the impeccable skill for detailed guidance on scales, pairing, and loading strategies. - -Create a systematic plan: - -- **Font selection**: Do fonts need replacing? What fits the brand/context? -- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy -- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits) -- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements - -## Improve Typography Systematically - -### Font Selection - -If fonts need replacing: -- Choose fonts that reflect the brand personality -- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights -- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks) - -### Establish Hierarchy - -Build a clear type scale: -- **5 sizes cover most needs**: caption, secondary, body, subheading, heading -- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5) -- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone -- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need -- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed - -### Fix Readability - -- Set `max-width` on text containers using `ch` units (`max-width: 65ch`) -- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7) -- Increase line-height slightly for light-on-dark text -- Ensure body text is at least 16px / 1rem - -### Refine Details - -- Use `tabular-nums` for data tables and numbers that should align -- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text -- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`) -- Set `font-kerning: normal` and consider OpenType features where appropriate - -### Weight Consistency - -- Define clear roles for each weight and stick to them -- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty) -- Load only the weights you actually use (each weight adds to page load) - -**NEVER**: -- Use more than 2-3 font families -- Pick sizes arbitrarily — commit to a scale -- Set body text below 16px -- Use decorative/display fonts for body text -- Disable browser zoom (`user-scalable=no`) -- Use `px` for font sizes — use `rem` to respect user settings -- Default to Inter/Roboto/Open Sans when personality matters -- Pair fonts that are similar but not identical (two geometric sans-serifs) - -## Verify Typography Improvements - -- **Hierarchy**: Can you identify heading vs body vs caption instantly? -- **Readability**: Is body text comfortable to read in long passages? -- **Consistency**: Are same-role elements styled identically throughout? -- **Personality**: Does the typography reflect the brand? -- **Performance**: Are web fonts loading efficiently without layout shift? -- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%? - -Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make. diff --git a/tests/cleanup-deprecated.test.mjs b/tests/cleanup-deprecated.test.mjs index 7dead6b3a..2a1fad6f9 100644 --- a/tests/cleanup-deprecated.test.mjs +++ b/tests/cleanup-deprecated.test.mjs @@ -77,7 +77,7 @@ describe('cleanup-deprecated', () => { assert.ok(names.includes('i-arrange')); assert.ok(names.includes('frontend-design')); assert.ok(names.includes('i-frontend-design')); - assert.equal(names.length, 12); // 6 deprecated * 2 + assert.equal(names.length, 46); // 23 deprecated * 2 }); }); @@ -128,11 +128,11 @@ describe('cleanup-deprecated', () => { }); it('leaves non-deprecated skills alone', () => { - writeSkill(tmp, '.claude', 'polish', 'Invoke /impeccable first.'); + writeSkill(tmp, '.claude', 'my-custom-skill', 'Invoke /impeccable first.'); writeSkill(tmp, '.claude', 'arrange', 'Invoke /impeccable first.'); const deleted = removeDeprecatedSkills(tmp); assert.equal(deleted.length, 1); // only arrange - assert.equal(existsSync(join(tmp, '.claude', 'skills', 'polish')), true); + assert.equal(existsSync(join(tmp, '.claude', 'skills', 'my-custom-skill')), true); }); it('handles symlinks to deprecated skills', () => { @@ -152,7 +152,7 @@ describe('cleanup-deprecated', () => { version: 1, skills: { arrange: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'abc' }, - polish: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'def' }, + impeccable: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'def' }, 'resolve-reviews': { source: 'pbakaus/agent-reviews', sourceType: 'github', computedHash: 'ghi' }, }, }; @@ -161,7 +161,7 @@ describe('cleanup-deprecated', () => { assert.deepEqual(removed, ['arrange']); const updated = JSON.parse(readFileSync(join(tmp, 'skills-lock.json'), 'utf-8')); assert.equal(updated.skills.arrange, undefined); - assert.ok(updated.skills.polish); // not deprecated + assert.ok(updated.skills.impeccable); // not deprecated assert.ok(updated.skills['resolve-reviews']); // different source }); @@ -209,7 +209,7 @@ describe('cleanup-deprecated', () => { skills: { arrange: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'a' }, extract: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'b' }, - polish: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'c' }, + impeccable: { source: 'pbakaus/impeccable', sourceType: 'github', computedHash: 'c' }, }, }; writeFileSync(join(tmp, 'skills-lock.json'), JSON.stringify(lock), 'utf-8'); @@ -221,13 +221,13 @@ describe('cleanup-deprecated', () => { assert.equal(existsSync(join(tmp, '.agents', 'skills', 'arrange')), false); const updated = JSON.parse(readFileSync(join(tmp, 'skills-lock.json'), 'utf-8')); - assert.ok(updated.skills.polish); + assert.ok(updated.skills.impeccable); // not deprecated assert.equal(updated.skills.arrange, undefined); assert.equal(updated.skills.extract, undefined); }); it('is a no-op when nothing needs cleaning', () => { - writeSkill(tmp, '.claude', 'polish', 'Invoke /impeccable.'); + writeSkill(tmp, '.claude', 'my-custom-skill', 'Invoke /impeccable.'); const result = cleanup(tmp); assert.equal(result.deletedPaths.length, 0); assert.equal(result.removedLockEntries.length, 0);