diff --git a/.claude/commands/adapt.md b/.claude/commands/adapt.md new file mode 100644 index 000000000..ecd9dd8ad --- /dev/null +++ b/.claude/commands/adapt.md @@ -0,0 +1,197 @@ +--- +name: adapt +description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments. +args: + - name: target + description: The feature or component to adapt (optional) + required: false + - name: context + description: What to adapt for (mobile, tablet, desktop, print, email, etc.) + required: false +--- + +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. \ No newline at end of file diff --git a/.claude/commands/animate.md b/.claude/commands/animate.md new file mode 100644 index 000000000..6382841f6 --- /dev/null +++ b/.claude/commands/animate.md @@ -0,0 +1,168 @@ +--- +name: animate +description: Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. +args: + - name: target + description: The feature or component to animate (optional) + required: false +--- + +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?) + +**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/.claude/commands/audit.md b/.claude/commands/audit.md new file mode 100644 index 000000000..11db6c75a --- /dev/null +++ b/.claude/commands/audit.md @@ -0,0 +1,127 @@ +--- +name: audit +description: Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations. +args: + - name: area + description: The feature or area to audit (optional) + required: false +--- + +Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address. + +## Diagnostic Scan + +Run comprehensive checks across multiple dimensions: + +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 + +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 + +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 + +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 + +5. **Design Anti-Patterns** - Check for: + - **Pure gray/black**: Using `#000`, `#808080`, or untinted grays (should have subtle color tint) + - **Gray on color**: Gray text on colored backgrounds (looks washed out—use a shade of the background color instead) + - **Nested cards**: Cards inside cards (visual noise, flatten hierarchy) + - **Bounce/elastic easing**: Dated animation curves (use ease-out-quart/quint/expo instead) + - **Redundant copy**: Headers restating intros, repeated explanations + - **Placeholder as label**: Using placeholder text as the only field label + - **Generic fonts**: Defaulting to Inter/Roboto/Arial without intentional choice + +**CRITICAL**: This is an audit, not a fix. Document issues thoroughly with clear explanations of impact. Use other commands (normalize, optimize, harden, etc.) to fix issues after audit. + +## Generate Comprehensive Report + +Create a detailed audit report with the following structure: + +### Executive Summary +- Total issues found (count by severity) +- Most critical issues (top 3-5) +- Overall quality score (if applicable) +- Recommended next steps + +### Detailed Findings by Severity + +For each issue, document: +- **Location**: Where the issue occurs (component, file, line) +- **Severity**: Critical / High / Medium / Low +- **Category**: Accessibility / Performance / Theming / Responsive +- **Description**: What the issue is +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (e.g., `/normalize`, `/optimize`, `/harden`) + +#### Critical Issues +[Issues that block core functionality or violate WCAG A] + +#### High-Severity Issues +[Significant usability/accessibility impact, WCAG AA violations] + +#### Medium-Severity Issues +[Quality issues, WCAG AAA violations, performance concerns] + +#### Low-Severity Issues +[Minor inconsistencies, optimization opportunities] + +### Patterns & Systemic Issues + +Identify recurring problems: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" +- "Missing focus indicators on all custom interactive components" + +### Positive Findings + +Note what's working well: +- Good practices to maintain +- Exemplary implementations to replicate elsewhere + +### Recommendations by Priority + +Create actionable plan: +1. **Immediate**: Critical blockers to fix first +2. **Short-term**: High-severity issues (this sprint) +3. **Medium-term**: Quality improvements (next sprint) +4. **Long-term**: Nice-to-haves and optimizations + +### Suggested Commands for Fixes + +Map issues to appropriate commands: +- "Use `/normalize` to align components with design system (addresses 23 theming issues)" +- "Use `/optimize` to improve performance (addresses 12 performance issues)" +- "Use `/harden` to improve i18n and text handling (addresses 8 edge cases)" + +**IMPORTANT**: Be thorough but actionable. Too many low-priority issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Mix severity levels inconsistently +- Skip positive findings (celebrate what works) +- Provide generic recommendations (be specific and actionable) +- Forget to prioritize (everything can't be critical) +- Report false positives without verification + +Remember: You're a quality auditor with exceptional attention to detail. Document systematically, prioritize ruthlessly, and provide clear paths to improvement. A good audit makes fixing easy. \ No newline at end of file diff --git a/.claude/commands/bolder.md b/.claude/commands/bolder.md new file mode 100644 index 000000000..186386242 --- /dev/null +++ b/.claude/commands/bolder.md @@ -0,0 +1,105 @@ +--- +name: bolder +description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. +args: + - name: target + description: The feature or component to make bolder (optional) + required: false +--- + +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) + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +## 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 frontend-design 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, monospace as accent + +### 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 +- **Background treatments**: Gradients, mesh patterns, noise textures, geometric patterns +- **Blur effects**: Glassmorphism, backdrop blur, depth effects +- **Borders & frames**: Thick borders, decorative frames, custom shapes +- **Custom elements**: Illustrative elements, custom icons, decorative details + +### 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: + +- **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? + +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/.claude/commands/clarify.md b/.claude/commands/clarify.md new file mode 100644 index 000000000..0ed67e8c3 --- /dev/null +++ b/.claude/commands/clarify.md @@ -0,0 +1,178 @@ +--- +name: clarify +description: Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use. +args: + - name: target + description: The feature or component with unclear copy (optional) + required: false +--- + +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. \ No newline at end of file diff --git a/.claude/commands/colorize.md b/.claude/commands/colorize.md new file mode 100644 index 000000000..c25a64187 --- /dev/null +++ b/.claude/commands/colorize.md @@ -0,0 +1,136 @@ +--- +name: colorize +description: Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive. +args: + - name: target + description: The feature or component to colorize (optional) + required: false +--- + +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 + +**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/.claude/commands/delight.md b/.claude/commands/delight.md new file mode 100644 index 000000000..8224a2dda --- /dev/null +++ b/.claude/commands/delight.md @@ -0,0 +1,295 @@ +--- +name: delight +description: Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. +args: + - name: target + description: The feature or area to add delight to (optional) + required: false +--- + +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) + +**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 ("Herding pixels..." "Teaching robots to dance...") +- 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 that bounce 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 rotation: +- "Waking up the servers..." +- "Teaching robots to dance..." +- "Consulting the magic 8-ball..." +- "Counting backwards from infinity..." +``` + +### 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/.claude/commands/extract.md b/.claude/commands/extract.md new file mode 100644 index 000000000..e0d42967a --- /dev/null +++ b/.claude/commands/extract.md @@ -0,0 +1,93 @@ +--- +name: extract +description: Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. +args: + - name: target + description: The feature, component, or area to extract from (optional) + required: false +--- + +Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse. + +## Discover + +Analyze the target area to identify extraction opportunities: + +1. **Find the design system**: Locate your design system, component library, or shared UI directory (grep for "design system", "ui", "components", etc.). Understand its structure: + - Component organization and naming conventions + - Design token structure (if any) + - Documentation patterns + - Import/export conventions + + **CRITICAL**: If no design system exists, ask before creating one. Understand the preferred location and structure first. + +2. **Identify patterns**: Look for: + - **Repeated components**: Similar UI patterns used multiple times (buttons, cards, inputs, etc.) + - **Hard-coded values**: Colors, spacing, typography, shadows that should be tokens + - **Inconsistent variations**: Multiple implementations of the same concept (3 different button styles) + - **Reusable patterns**: Layout patterns, composition patterns, interaction patterns worth systematizing + +3. **Assess value**: Not everything should be extracted. Consider: + - Is this used 3+ times, or likely to be reused? + - Would systematizing this improve consistency? + - Is this a general pattern or context-specific? + - What's the maintenance cost vs benefit? + +## Plan Extraction + +Create a systematic extraction plan: + +- **Components to extract**: Which UI elements become reusable components? +- **Tokens to create**: Which hard-coded values become design tokens? +- **Variants to support**: What variations does each component need? +- **Naming conventions**: Component names, token names, prop names that match existing patterns +- **Migration path**: How to refactor existing uses to consume the new shared versions + +**IMPORTANT**: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable. + +## Extract & Enrich + +Build improved, reusable versions: + +- **Components**: Create well-designed components with: + - Clear props API with sensible defaults + - Proper variants for different use cases + - Accessibility built in (ARIA, keyboard navigation, focus management) + - Documentation and usage examples + +- **Design tokens**: Create tokens with: + - Clear naming (primitive vs semantic) + - Proper hierarchy and organization + - Documentation of when to use each token + +- **Patterns**: Document patterns with: + - When to use this pattern + - Code examples + - Variations and combinations + +**NEVER**: +- Extract one-off, context-specific implementations without generalization +- Create components so generic they're useless +- Extract without considering existing design system conventions +- Skip proper TypeScript types or prop documentation +- Create tokens for every single value (tokens should have semantic meaning) + +## Migrate + +Replace existing uses with the new shared versions: + +- **Find all instances**: Search for the patterns you've extracted +- **Replace systematically**: Update each use to consume the shared version +- **Test thoroughly**: Ensure visual and functional parity +- **Delete dead code**: Remove the old implementations + +## Document + +Update design system documentation: + +- Add new components to the component library +- Document token usage and values +- Add examples and guidelines +- Update any Storybook or component catalog + +Remember: A good design system is a living system. Extract patterns as they emerge, enrich them thoughtfully, and maintain them consistently. \ No newline at end of file diff --git a/.claude/commands/harden.md b/.claude/commands/harden.md new file mode 100644 index 000000000..830876692 --- /dev/null +++ b/.claude/commands/harden.md @@ -0,0 +1,356 @@ +--- +name: harden +description: Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. +args: + - name: target + description: The feature or area to harden (optional) + required: false +--- + +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 + +### 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/commands/normalize.md b/.claude/commands/normalize.md new file mode 100644 index 000000000..3c3cb0026 --- /dev/null +++ b/.claude/commands/normalize.md @@ -0,0 +1,66 @@ +--- +name: normalize +description: Normalize design to match your design system and ensure consistency +args: + - name: feature + description: The page, route, or feature to normalize (optional) + required: false +--- + +Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns. + +## Plan + +Before making changes, deeply understand the context: + +1. **Discover the design system**: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand: + - Core design principles and aesthetic direction + - Target audience and personas + - Component patterns and conventions + - Design tokens (colors, typography, spacing) + + **CRITICAL**: If something isn't clear, ask. Don't guess at design system principles. + +2. **Analyze the current feature**: Assess what works and what doesn't: + - Where does it deviate from design system patterns? + - Which inconsistencies are cosmetic vs. functional? + - What's the root cause—missing tokens, one-off implementations, or conceptual misalignment? + +3. **Create a normalization plan**: Define specific changes that will align the feature with the design system: + - Which components can be replaced with design system equivalents? + - Which styles need to use design tokens instead of hard-coded values? + - How can UX patterns match established user flows? + + **IMPORTANT**: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first. + +## Execute + +Systematically address all inconsistencies across these dimensions: + +- **Typography**: Use design system fonts, sizes, weights, and line heights. Replace hard-coded values with typographic tokens or classes. +- **Color & Theme**: Apply design system color tokens. Remove one-off color choices that break the palette. +- **Spacing & Layout**: Use spacing tokens (margins, padding, gaps). Align with grid systems and layout patterns used elsewhere. +- **Components**: Replace custom implementations with design system components. Ensure props and variants match established patterns. +- **Motion & Interaction**: Match animation timing, easing, and interaction patterns to other features. +- **Responsive Behavior**: Ensure breakpoints and responsive patterns align with design system standards. +- **Accessibility**: Verify contrast ratios, focus states, ARIA labels match design system requirements. +- **Progressive Disclosure**: Match information hierarchy and complexity management to established patterns. + +**NEVER**: +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens +- Introduce new patterns that diverge from the design system +- Compromise accessibility for visual consistency + +This is not an exhaustive list—apply judgment to identify all areas needing normalization. + +## Clean Up + +After normalization, ensure code quality: + +- **Consolidate reusable components**: If you created new components that should be shared, move them to the design system or shared UI component path. +- **Remove orphaned code**: Delete unused implementations, styles, or files made obsolete by normalization. +- **Verify quality**: Lint, type-check, and test according to repository guidelines. Ensure normalization didn't introduce regressions. +- **Ensure DRYness**: Look for duplication introduced during refactoring and consolidate. + +Remember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness. \ No newline at end of file diff --git a/.claude/commands/onboard.md b/.claude/commands/onboard.md new file mode 100644 index 000000000..64c3f6bba --- /dev/null +++ b/.claude/commands/onboard.md @@ -0,0 +1,241 @@ +--- +name: onboard +description: Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly. +args: + - name: target + description: The feature or area needing onboarding (optional) + required: false +--- + +Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly. + +## Assess Onboarding Needs + +Understand what users need to learn and why: + +1. **Identify the challenge**: + - What are users trying to accomplish? + - What's confusing or unclear about current experience? + - Where do users get stuck or drop off? + - What's the "aha moment" we want users to reach? + +2. **Understand the users**: + - What's their experience level? (Beginners, power users, mixed?) + - What's their motivation? (Excited and exploring? Required by work?) + - What's their time commitment? (5 minutes? 30 minutes?) + - What alternatives do they know? (Coming from competitor? New to category?) + +3. **Define success**: + - What's the minimum users need to learn to be successful? + - What's the key action we want them to take? (First project? First invite?) + - How do we know onboarding worked? (Completion rate? Time to value?) + +**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible. + +## Onboarding Principles + +Follow these core principles: + +### Show, Don't Tell +- Demonstrate with working examples, not just descriptions +- Provide real functionality in onboarding, not separate tutorial mode +- Use progressive disclosure - teach one thing at a time + +### Make It Optional (When Possible) +- Let experienced users skip onboarding +- Don't block access to product +- Provide "Skip" or "I'll explore on my own" options + +### Time to Value +- Get users to their "aha moment" ASAP +- Front-load most important concepts +- Teach 20% that delivers 80% of value +- Save advanced features for contextual discovery + +### Context Over Ceremony +- Teach features when users need them, not upfront +- Empty states are onboarding opportunities +- Tooltips and hints at point of use + +### Respect User Intelligence +- Don't patronize or over-explain +- Be concise and clear +- Assume users can figure out standard patterns + +## Design Onboarding Experiences + +Create appropriate onboarding for the context: + +### Initial Product Onboarding + +**Welcome Screen**: +- Clear value proposition (what is this product?) +- What users will learn/accomplish +- Time estimate (honest about commitment) +- Option to skip (for experienced users) + +**Account Setup**: +- Minimal required information (collect more later) +- Explain why you're asking for each piece of information +- Smart defaults where possible +- Social login when appropriate + +**Core Concept Introduction**: +- Introduce 1-3 core concepts (not everything) +- Use simple language and examples +- Interactive when possible (do, don't just read) +- Progress indication (step 1 of 3) + +**First Success**: +- Guide users to accomplish something real +- Pre-populated examples or templates +- Celebrate completion (but don't overdo it) +- Clear next steps + +### Feature Discovery & Adoption + +**Empty States**: +Instead of blank space, show: +- What will appear here (description + screenshot/illustration) +- Why it's valuable +- Clear CTA to create first item +- Example or template option + +Example: +``` +No projects yet +Projects help you organize your work and collaborate with your team. +[Create your first project] or [Start from template] +``` + +**Contextual Tooltips**: +- Appear at relevant moment (first time user sees feature) +- Point directly at relevant UI element +- Brief explanation + benefit +- Dismissable (with "Don't show again" option) +- Optional "Learn more" link + +**Feature Announcements**: +- Highlight new features when they're released +- Show what's new and why it matters +- Let users try immediately +- Dismissable + +**Progressive Onboarding**: +- Teach features when users encounter them +- Badges or indicators on new/unused features +- Unlock complexity gradually (don't show all options immediately) + +### Guided Tours & Walkthroughs + +**When to use**: +- Complex interfaces with many features +- Significant changes to existing product +- Industry-specific tools needing domain knowledge + +**How to design**: +- Spotlight specific UI elements (dim rest of page) +- Keep steps short (3-7 steps max per tour) +- Allow users to click through tour freely +- Include "Skip tour" option +- Make replayable (help menu) + +**Best practices**: +- Interactive > passive (let users click real buttons) +- Focus on workflow, not features ("Create a project" not "This is the project button") +- Provide sample data so actions work + +### Interactive Tutorials + +**When to use**: +- Users need hands-on practice +- Concepts are complex or unfamiliar +- High stakes (better to practice in safe environment) + +**How to design**: +- Sandbox environment with sample data +- Clear objectives ("Create a chart showing sales by region") +- Step-by-step guidance +- Validation (confirm they did it right) +- Graduation moment (you're ready!) + +### Documentation & Help + +**In-product help**: +- Contextual help links throughout interface +- Keyboard shortcut reference +- Search-able help center +- Video tutorials for complex workflows + +**Help patterns**: +- `?` icon near complex features +- "Learn more" links in tooltips +- Keyboard shortcut hints (`⌘K` shown on search box) + +## Empty State Design + +Every empty state needs: + +### What Will Be Here +"Your recent projects will appear here" + +### Why It Matters +"Projects help you organize your work and collaborate with your team" + +### How to Get Started +[Create project] or [Import from template] + +### Visual Interest +Illustration or icon (not just text on blank page) + +### Contextual Help +"Need help getting started? [Watch 2-min tutorial]" + +**Empty state types**: +- **First use**: Never used this feature (emphasize value, provide template) +- **User cleared**: Intentionally deleted everything (light touch, easy to recreate) +- **No results**: Search or filter returned nothing (suggest different query, clear filters) +- **No permissions**: Can't access (explain why, how to get access) +- **Error state**: Failed to load (explain what happened, retry option) + +## Implementation Patterns + +### Technical approaches: + +**Tooltip libraries**: Tippy.js, Popper.js +**Tour libraries**: Intro.js, Shepherd.js, React Joyride +**Modal patterns**: Focus trap, backdrop, ESC to close +**Progress tracking**: LocalStorage for "seen" states +**Analytics**: Track completion, drop-off points + +**Storage patterns**: +```javascript +// Track which onboarding steps user has seen +localStorage.setItem('onboarding-completed', 'true'); +localStorage.setItem('feature-tooltip-seen-reports', 'true'); +``` + +**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals. + +**NEVER**: +- Force users through long onboarding before they can use product +- Patronize users with obvious explanations +- Show same tooltip repeatedly (respect dismissals) +- Block all UI during tour (let users explore) +- Create separate tutorial mode disconnected from real product +- Overwhelm with information upfront (progressive disclosure!) +- Hide "Skip" or make it hard to find +- Forget about returning users (don't show initial onboarding again) + +## Verify Onboarding Quality + +Test with real users: + +- **Time to completion**: Can users complete onboarding quickly? +- **Comprehension**: Do users understand after completing? +- **Action**: Do users take desired next step? +- **Skip rate**: Are too many users skipping? (Maybe it's too long/not valuable) +- **Completion rate**: Are users completing? (If low, simplify) +- **Time to value**: How long until users get first value? + +Remember: You're a product educator with excellent teaching instincts. Get users to their "aha moment" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence. \ No newline at end of file diff --git a/.claude/commands/optimize.md b/.claude/commands/optimize.md new file mode 100644 index 000000000..35cbf5f50 --- /dev/null +++ b/.claude/commands/optimize.md @@ -0,0 +1,267 @@ +--- +name: optimize +description: Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother. +args: + - name: target + description: The feature or area to optimize (optional) + required: false +--- + +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/commands/polish.md b/.claude/commands/polish.md new file mode 100644 index 000000000..806888a10 --- /dev/null +++ b/.claude/commands/polish.md @@ -0,0 +1,198 @@ +--- +name: polish +description: Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great. +args: + - name: target + description: The feature or area to polish (optional) + required: false +--- + +Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished. + +## Pre-Polish Assessment + +Understand the current state and goals: + +1. **Review completeness**: + - Is it functionally complete? + - Are there known issues to preserve (mark with TODOs)? + - What's the quality bar? (MVP vs flagship feature?) + - When does it ship? (How much time for polish?) + +2. **Identify polish areas**: + - Visual inconsistencies + - Spacing and alignment issues + - Interaction state gaps + - Copy inconsistencies + - Edge cases and error states + - Loading and transition smoothness + +**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete. + +## Polish Systematically + +Work through these dimensions methodically: + +### Visual Alignment & Spacing + +- **Pixel-perfect alignment**: Everything lines up to grid +- **Consistent spacing**: All gaps use spacing scale (no random 13px gaps) +- **Optical alignment**: Adjust for visual weight (icons may need offset for optical centering) +- **Responsive consistency**: Spacing and alignment work at all breakpoints +- **Grid adherence**: Elements snap to baseline grid + +**Check**: +- Enable grid overlay and verify alignment +- Check spacing with browser inspector +- Test at multiple viewport sizes +- Look for elements that "feel" off + +### Typography Refinement + +- **Hierarchy consistency**: Same elements use same sizes/weights throughout +- **Line length**: 45-75 characters for body text +- **Line height**: Appropriate for font size and context +- **Widows & orphans**: No single words on last line +- **Hyphenation**: Appropriate for language and column width +- **Kerning**: Adjust letter spacing where needed (especially headlines) +- **Font loading**: No FOUT/FOIT flashes + +### Color & Contrast + +- **Contrast ratios**: All text meets WCAG standards +- **Consistent token usage**: No hard-coded colors, all use design tokens +- **Theme consistency**: Works in all theme variants +- **Color meaning**: Same colors mean same things throughout +- **Accessible focus**: Focus indicators visible with sufficient contrast +- **Tinted neutrals**: No pure gray or pure black—add subtle color tint (0.01 chroma) +- **Gray on color**: Never put gray text on colored backgrounds—use a shade of that color or transparency + +### Interaction States + +Every interactive element needs all states: + +- **Default**: Resting state +- **Hover**: Subtle feedback (color, scale, shadow) +- **Focus**: Keyboard focus indicator (never remove without replacement) +- **Active**: Click/tap feedback +- **Disabled**: Clearly non-interactive +- **Loading**: Async action feedback +- **Error**: Validation or error state +- **Success**: Successful completion + +**Missing states create confusion and broken experiences**. + +### Micro-interactions & Transitions + +- **Smooth transitions**: All state changes animated appropriately (150-300ms) +- **Consistent easing**: Use ease-out-quart/quint/expo for natural deceleration. Never bounce or elastic—they feel dated. +- **No jank**: 60fps animations, only animate transform and opacity +- **Appropriate motion**: Motion serves purpose, not decoration +- **Reduced motion**: Respects `prefers-reduced-motion` + +### Content & Copy + +- **Consistent terminology**: Same things called same names throughout +- **Consistent capitalization**: Title Case vs Sentence case applied consistently +- **Grammar & spelling**: No typos +- **Appropriate length**: Not too wordy, not too terse +- **Punctuation consistency**: Periods on sentences, not on labels (unless all labels have them) + +### Icons & Images + +- **Consistent style**: All icons from same family or matching style +- **Appropriate sizing**: Icons sized consistently for context +- **Proper alignment**: Icons align with adjacent text optically +- **Alt text**: All images have descriptive alt text +- **Loading states**: Images don't cause layout shift, proper aspect ratios +- **Retina support**: 2x assets for high-DPI screens + +### Forms & Inputs + +- **Label consistency**: All inputs properly labeled +- **Required indicators**: Clear and consistent +- **Error messages**: Helpful and consistent +- **Tab order**: Logical keyboard navigation +- **Auto-focus**: Appropriate (don't overuse) +- **Validation timing**: Consistent (on blur vs on submit) + +### Edge Cases & Error States + +- **Loading states**: All async actions have loading feedback +- **Empty states**: Helpful empty states, not just blank space +- **Error states**: Clear error messages with recovery paths +- **Success states**: Confirmation of successful actions +- **Long content**: Handles very long names, descriptions, etc. +- **No content**: Handles missing data gracefully +- **Offline**: Appropriate offline handling (if applicable) + +### Responsiveness + +- **All breakpoints**: Test mobile, tablet, desktop +- **Touch targets**: 44x44px minimum on touch devices +- **Readable text**: No text smaller than 14px on mobile +- **No horizontal scroll**: Content fits viewport +- **Appropriate reflow**: Content adapts logically + +### Performance + +- **Fast initial load**: Optimize critical path +- **No layout shift**: Elements don't jump after load (CLS) +- **Smooth interactions**: No lag or jank +- **Optimized images**: Appropriate formats and sizes +- **Lazy loading**: Off-screen content loads lazily + +### Code Quality + +- **Remove console logs**: No debug logging in production +- **Remove commented code**: Clean up dead code +- **Remove unused imports**: Clean up unused dependencies +- **Consistent naming**: Variables and functions follow conventions +- **Type safety**: No TypeScript `any` or ignored errors +- **Accessibility**: Proper ARIA labels and semantic HTML + +## Polish Checklist + +Go through systematically: + +- [ ] Visual alignment perfect at all breakpoints +- [ ] Spacing uses design tokens consistently +- [ ] Typography hierarchy consistent +- [ ] All interactive states implemented +- [ ] All transitions smooth (60fps) +- [ ] Copy is consistent and polished +- [ ] Icons are consistent and properly sized +- [ ] All forms properly labeled and validated +- [ ] Error states are helpful +- [ ] Loading states are clear +- [ ] Empty states are welcoming +- [ ] Touch targets are 44x44px minimum +- [ ] Contrast ratios meet WCAG AA +- [ ] Keyboard navigation works +- [ ] Focus indicators visible +- [ ] No console errors or warnings +- [ ] No layout shift on load +- [ ] Works in all supported browsers +- [ ] Respects reduced motion preference +- [ ] Code is clean (no TODOs, console.logs, commented code) + +**IMPORTANT**: Polish is about details. Zoom in. Squint at it. Use it yourself. The little things add up. + +**NEVER**: +- Polish before it's functionally complete +- Spend hours on polish if it ships in 30 minutes (triage) +- Introduce bugs while polishing (test thoroughly) +- Ignore systematic issues (if spacing is off everywhere, fix the system) +- Perfect one thing while leaving others rough (consistent quality level) + +## Final Verification + +Before marking as done: + +- **Use it yourself**: Actually interact with the feature +- **Test on real devices**: Not just browser DevTools +- **Ask someone else to review**: Fresh eyes catch things +- **Compare to design**: Match intended design +- **Check all states**: Don't just test happy path + +Remember: You have impeccable attention to detail and exquisite taste. Polish until it feels effortless, looks intentional, and works flawlessly. Sweat the details - they matter. \ No newline at end of file diff --git a/.claude/commands/quieter.md b/.claude/commands/quieter.md new file mode 100644 index 000000000..f37759a5f --- /dev/null +++ b/.claude/commands/quieter.md @@ -0,0 +1,96 @@ +--- +name: quieter +description: Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact. +args: + - name: target + description: The feature or component to make quieter (optional) + required: false +--- + +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) + +**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/.claude/commands/simplify.md b/.claude/commands/simplify.md new file mode 100644 index 000000000..f3c3060e6 --- /dev/null +++ b/.claude/commands/simplify.md @@ -0,0 +1,115 @@ +--- +name: simplify +description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. +args: + - name: target + description: The feature or component to simplify (optional) + required: false +--- + +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? + +**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/.claude/skills/frontend-design/SKILL.md b/.claude/skills/frontend-design/SKILL.md new file mode 100644 index 000000000..5b4f244b2 --- /dev/null +++ b/.claude/skills/frontend-design/SKILL.md @@ -0,0 +1,123 @@ +--- +name: frontend-design +description: Create distinctive, production-grade frontend interfaces with comprehensive expertise in typography, color systems, spatial design, responsive layouts, interaction patterns, motion, and UX writing. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. +license: Complete terms in LICENSE.txt +--- + +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. + +The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. + +## Design Thinking + +Before coding, understand the context and commit to a BOLD aesthetic direction: +- **Purpose**: What problem does this interface solve? Who uses it? +- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction. +- **Constraints**: Technical requirements (framework, performance, accessibility). +- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember? + +**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity. + +Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is: +- Production-grade and functional +- Visually striking and memorable +- Cohesive with a clear aesthetic point-of-view +- Meticulously refined in every detail + +## Frontend Aesthetics Guidelines + +Focus on: +- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font. +- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. +- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise. +- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. +- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays. + +NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character. + +Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations. + +**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well. + +Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision. + + + +## Design Patterns Reference + +This reference defines what TO do and what NOT to do when creating frontend interfaces. These patterns fight against model bias—the tendency of LLMs to converge on the same predictable choices. + +### What TO Do (Patterns) + +Focus on intentional, distinctive design choices: + +**Typography**: Use a modular type scale with a distinctive display font paired with a refined body font. Establish clear hierarchy through weight, size, and spacing—not size alone. + +**Color**: Build palettes from a dominant color with sharp accents. Use off-whites and near-blacks for sophistication. Always meet WCAG AA contrast requirements. + +**Space**: Use a spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96). Create visual rhythm through varied spacing. Let content breathe. Break the grid intentionally. + +**Motion**: Animate with purpose—guide attention and confirm actions. Use 150-300ms for micro-interactions. Prefer transform and opacity with smooth ease-out curves (quart, quint, expo). Stagger reveals for orchestrated page loads. + +**Interaction**: Design clear focus indicators. Make touch targets 44×44px minimum. Provide immediate feedback. Write specific, helpful error messages. + +**Responsive**: Design mobile-first. Use fluid typography with clamp(). Ensure all functionality works across devices. + +### What NOT to Do (Anti-Patterns) + +These patterns create generic "AI slop" aesthetics: + +**Generic Visuals**: Defaulting to Inter/Roboto/Arial, purple-to-blue gradients on white, pure grays without color tint, wrapping everything in rounded cards, decorative shadows without purpose. + +**Structural Issues**: Arbitrary spacing without a scale, hierarchy through size alone, equal spacing everywhere, cards nested inside cards, redundant copy (headers restating intros, repeated explanations). + +**Motion Mistakes**: Bounce and elastic easing (dated and tacky), animating layout properties, durations over 500ms for feedback, animation without purpose. + +**Interaction Failures**: Removing focus outlines without alternatives, placeholder text as labels, touch targets under 44×44px, generic "Something went wrong" errors, gray text on colored backgrounds. + +**Accessibility Violations**: Color-only meaning, ignoring prefers-reduced-motion, failing WCAG contrast, creating keyboard traps. + +These anti-patterns are baked into training data from countless generic templates. Without explicit guidance, AI reproduces them. This skill ensures your AI knows both what to do AND what to avoid. + +--- + +## Domain Reference Files + +For deeper expertise in specific design domains, consult these reference files: + +### Typography +For type systems, font selection, readability, and typographic hierarchy. +**See**: [reference/typography.md](reference/typography.md) + +### Color & Contrast +For color systems, palettes, accessibility, theming, and WCAG compliance. +**See**: [reference/color-and-contrast.md](reference/color-and-contrast.md) + +### Spatial Design +For spacing systems, grids, visual hierarchy, and composition. +**See**: [reference/spatial-design.md](reference/spatial-design.md) + +### Responsive Design +For mobile-first layouts, breakpoints, fluid design, and cross-device adaptation. +**See**: [reference/responsive-design.md](reference/responsive-design.md) + +### Interaction Design +For forms, states, feedback patterns, keyboard navigation, and touch optimization. +**See**: [reference/interaction-design.md](reference/interaction-design.md) + +### Motion Design +For animations, micro-interactions, transitions, and performance optimization. +**See**: [reference/motion-design.md](reference/motion-design.md) + +### UX Writing +For interface copy, error messages, microcopy, and voice/tone guidelines. +**See**: [reference/ux-writing.md](reference/ux-writing.md) + +--- + +## When to Use Reference Files + +- **Quick builds**: Use this main skill file for most frontend work +- **Deep dives**: Consult specific reference files when facing complex challenges in that domain +- **Systematic work**: When building design systems or establishing patterns, reference multiple domain files +- **Troubleshooting**: When something feels "off", check the relevant domain reference for best practices \ No newline at end of file diff --git a/.claude/skills/frontend-design/reference/color-and-contrast.md b/.claude/skills/frontend-design/reference/color-and-contrast.md new file mode 100644 index 000000000..29a1f9851 --- /dev/null +++ b/.claude/skills/frontend-design/reference/color-and-contrast.md @@ -0,0 +1,216 @@ +# Color & Contrast + +This reference guides the creation of color systems that are both beautiful and functional, balancing creative expression with accessibility and systematic coherence. + +The user provides a color challenge: building a color palette, implementing theming, fixing contrast issues, establishing brand colors, or creating dark mode variants. They may include brand guidelines, accessibility requirements, or existing design constraints. + +## Color System Thinking + +Before choosing colors, understand the strategic requirements: + +- **Brand & Emotion**: What feelings should the colors evoke? Trust (blues)? Energy (reds/oranges)? Growth (greens)? Luxury (purples/golds)? Colors are never neutral. +- **Functional Requirements**: How many semantic states needed? Success, error, warning, info? How many UI layers? Background, surface, border, text? +- **Context**: Industry conventions (avoid red for finance), cultural considerations, competitor differentiation. +- **Accessibility Goals**: WCAG level (A/AA/AAA), audience considerations (aging users need higher contrast). + +**CRITICAL**: Color is both an art and a science. Aesthetics matter, but accessibility is non-negotiable. + +Then build a color system that is: +- Accessible and WCAG compliant +- Systematically organized with clear roles +- Flexible enough for theming and variations +- Aesthetically cohesive and on-brand + +## Color Spaces: Use OKLCH + +**Stop using HSL.** Use OKLCH (or LCH) instead. It's perceptually uniform, meaning equal steps in lightness *look* equal—unlike HSL where 50% lightness in yellow looks bright while 50% in blue looks dark. + +```css +/* OKLCH: lightness (0-100%), chroma (0-0.4+), hue (0-360) */ +--color-primary: oklch(60% 0.15 250); /* Blue */ +--color-primary-light: oklch(85% 0.08 250); /* Same hue, lighter */ +--color-primary-dark: oklch(35% 0.12 250); /* Same hue, darker */ +``` + +**Key insight**: As you move toward white or black, reduce chroma (saturation). High chroma at extreme lightness looks garish. A light blue at 85% lightness needs ~0.08 chroma, not the 0.15 of your base color. + +## Building Functional Palettes + +### The Tinted Neutral Trap + +**Pure gray is dead.** Add a subtle hint of your brand hue to all neutrals: + +```css +/* Dead grays */ +--gray-100: oklch(95% 0 0); /* No personality */ +--gray-900: oklch(15% 0 0); + +/* Warm-tinted grays (add brand warmth) */ +--gray-100: oklch(95% 0.01 60); /* Hint of warmth */ +--gray-900: oklch(15% 0.01 60); + +/* Cool-tinted grays (tech, professional) */ +--gray-100: oklch(95% 0.01 250); /* Hint of blue */ +--gray-900: oklch(15% 0.01 250); +``` + +The chroma is tiny (0.01) but perceptible. It creates subconscious cohesion between your brand color and your UI. + +### Palette Structure + +A complete system needs: + +| Role | Purpose | Example | +|------|---------|---------| +| **Primary** | Brand, CTAs, key actions | 1 color, 3-5 shades | +| **Neutral** | Text, backgrounds, borders | 9-11 shade scale | +| **Semantic** | Success, error, warning, info | 4 colors, 2-3 shades each | +| **Surface** | Cards, modals, overlays | 2-3 elevation levels | + +**Skip secondary/tertiary unless you need them.** Most apps work fine with one accent color. Adding more creates decision fatigue and visual noise. + +### The 60-30-10 Rule (Applied Correctly) + +This rule is about **visual weight**, not pixel count: + +- **60%**: Neutral backgrounds, white space, base surfaces +- **30%**: Secondary colors—text, borders, inactive states +- **10%**: Accent—CTAs, highlights, focus states + +The common mistake: using the accent color everywhere because it's "the brand color." Accent colors work *because* they're rare. Overuse kills their power. + +## Contrast & Accessibility + +### WCAG Requirements + +| Content Type | AA Minimum | AAA Target | +|--------------|------------|------------| +| Body text | 4.5:1 | 7:1 | +| Large text (18px+ or 14px bold) | 3:1 | 4.5:1 | +| UI components, icons | 3:1 | 4.5:1 | +| Non-essential decorations | None | None | + +**The gotcha**: Placeholder text still needs 4.5:1. That light gray placeholder you see everywhere? Usually fails WCAG. + +### Dangerous Color Combinations + +These commonly fail contrast or cause readability issues: + +- Light gray text on white (the #1 accessibility fail) +- **Gray text on any colored background**—gray looks washed out and dead on color. Use a darker shade of the background color, or transparency +- Red text on green background (or vice versa)—8% of men can't distinguish these +- Blue text on red background (vibrates visually) +- Yellow text on white (almost always fails) +- Thin light text on images (unpredictable contrast) + +### Never Use Pure Gray or Pure Black + +Pure gray (`oklch(50% 0 0)`) and pure black (`#000`) don't exist in nature—real shadows and surfaces always have a color cast. They look uncanny and lifeless. + +```css +/* Dead and artificial */ +--gray: oklch(50% 0 0); +--black: oklch(0% 0 0); + +/* Natural and warm */ +--gray: oklch(50% 0.01 60); /* Warm gray */ +--black: oklch(12% 0.01 250); /* Very dark blue-gray */ +``` + +Even a chroma of 0.005-0.01 is enough to feel natural without being obviously tinted. + +### Testing + +Don't trust your eyes. Use tools: + +- [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/) +- Browser DevTools → Rendering → Emulate vision deficiencies +- [Polypane](https://polypane.app/) for real-time testing + +## Theming: Light & Dark Mode + +### Dark Mode Is Not Inverted Light Mode + +You can't just swap colors. Dark mode requires different design decisions: + +| Light Mode | Dark Mode | +|------------|-----------| +| Shadows for depth | Lighter surfaces for depth (no shadows) | +| Dark text on light | Light text on dark (reduce font weight) | +| Vibrant accents | Desaturate accents slightly | +| White backgrounds | Never pure black—use dark gray (oklch 12-18%) | + +```css +/* Dark mode depth via surface color, not shadow */ +:root[data-theme="dark"] { + --surface-1: oklch(15% 0.01 250); + --surface-2: oklch(20% 0.01 250); /* "Higher" = lighter */ + --surface-3: oklch(25% 0.01 250); + + /* Reduce text weight slightly */ + --body-weight: 350; /* Instead of 400 */ +} +``` + +### Token Hierarchy + +Use two layers of abstraction: + +```css +/* Layer 1: Primitive tokens (rarely use directly) */ +--blue-500: oklch(55% 0.2 250); +--blue-600: oklch(45% 0.2 250); + +/* Layer 2: Semantic tokens (use these) */ +--color-primary: var(--blue-500); +--color-primary-hover: var(--blue-600); +--color-text: var(--gray-900); +--color-text-muted: var(--gray-600); +--color-border: var(--gray-200); +--color-surface: var(--white); +``` + +**For dark mode, only redefine the semantic layer:** + +```css +:root[data-theme="dark"] { + --color-primary: var(--blue-400); /* Lighter in dark mode */ + --color-text: var(--gray-100); + --color-surface: var(--gray-900); +} +``` + +## Alpha Is A Design Smell + +If you're using lots of transparency (rgba, hsla), your palette is probably incomplete. Alpha creates: +- Unpredictable contrast (depends on what's behind it) +- Performance overhead (compositing) +- Inconsistency across contexts + +**Instead**: Define explicit overlay colors: + +```css +/* Bad: unpredictable */ +--overlay: rgba(0, 0, 0, 0.5); + +/* Good: explicit colors for each context */ +--overlay-on-light: oklch(40% 0 0); +--overlay-on-dark: oklch(70% 0 0); +--overlay-on-image: oklch(20% 0 0 / 60%); /* Alpha only when necessary */ +``` + +The exception: Focus rings and interactive states where you need to see through to the element beneath. + +--- + +**IMPORTANT**: Test color combinations in context, not in isolation. Colors behave differently on different backgrounds and at different sizes. + +**NEVER**: +- Rely on color alone to convey information +- Use color combinations that fail WCAG contrast requirements +- Create palettes with arbitrary color choices (every color needs a purpose) +- Ignore color blindness (8% of men, 0.5% of women) +- Use pure black (#000) or pure white (#fff) for large areas +- Create theme systems without testing all combinations + +Remember: Color is powerful. Use it deliberately, systematically, and inclusively. diff --git a/.claude/skills/frontend-design/reference/interaction-design.md b/.claude/skills/frontend-design/reference/interaction-design.md new file mode 100644 index 000000000..a6cbbe014 --- /dev/null +++ b/.claude/skills/frontend-design/reference/interaction-design.md @@ -0,0 +1,273 @@ +# Interaction Design + +This reference guides the creation of interaction patterns that are intuitive, accessible, and delightful - the conversation between user and interface. + +The user provides an interaction challenge: designing forms, improving button states, fixing navigation patterns, optimizing input UX, implementing keyboard navigation, or creating feedback mechanisms. They may include accessibility requirements, device constraints, or specific interaction problems to solve. + +## Interaction Design Thinking + +Before designing interactions, understand the user's mental model and context: + +- **User Context**: What are users trying to accomplish? What's their experience level? What's their emotional state (stressed during checkout vs relaxed browsing)? +- **Device & Input**: Touch vs pointer? Keyboard navigation? Voice input? Gamepad? Different inputs need different affordances. +- **Error Tolerance**: High-stakes actions (delete, purchase) vs low-stakes (filter, sort)? Design appropriate safeguards. +- **Speed vs Accuracy**: Quick scanning vs careful reading? Simple taps vs precise manipulation? + +**CRITICAL**: Good interaction design is invisible. Users should complete tasks without thinking about the interface. + +Then implement interactions that are: +- Intuitive with clear affordances and feedback +- Accessible to all users and input methods +- Forgiving with error prevention and recovery +- Responsive with immediate feedback and state changes + +## The Eight Interactive States + +Every interactive element needs these states designed: + +| State | When | Visual Treatment | +|-------|------|------------------| +| **Default** | At rest | Base styling | +| **Hover** | Pointer over (not touch) | Subtle lift, color shift | +| **Focus** | Keyboard/programmatic focus | Visible ring (see below) | +| **Active** | Being pressed | Pressed in, darker | +| **Disabled** | Not interactive | Reduced opacity, no pointer | +| **Loading** | Processing | Spinner, skeleton | +| **Error** | Invalid state | Red border, icon, message | +| **Success** | Completed | Green check, confirmation | + +**The common miss**: Designing hover without focus, or vice versa. They're different. Keyboard users never see hover states. + +## Focus Rings: Do Them Right + +**Never `outline: none` without replacement.** It's an accessibility violation. Instead, use `:focus-visible` to show focus only for keyboard users: + +```css +/* Hide focus ring for mouse/touch */ +button:focus { + outline: none; +} + +/* Show focus ring for keyboard */ +button:focus-visible { + outline: 2px solid var(--color-accent); + outline-offset: 2px; +} +``` + +**Focus ring design**: +- High contrast (3:1 minimum against adjacent colors) +- 2-3px thick +- Offset from element (not inside it) +- Consistent across all interactive elements + +## Form Design: The Non-Obvious + +### Don't Use Placeholders as Labels + +Placeholders disappear when you type. Users forget what the field was for. Screen readers may not announce them. + +```html + + + + + + +``` + +Use placeholders only for examples or format hints, never as the primary label. + +### Validate on Blur, Not on Input + +Real-time validation (validating every keystroke) is annoying. Users can't finish typing before seeing errors. + +```javascript +// Bad: fires on every keystroke +input.addEventListener('input', validate); + +// Good: fires when user leaves field +input.addEventListener('blur', validate); + +// Exception: password strength (show progress while typing) +passwordInput.addEventListener('input', showStrength); +``` + +### Error Message Placement + +Place errors **below** the field (users scan top-down), not above. Keep messages close to the field—not in a summary at the top unless also repeated inline. + +```html + + +Please enter a valid email +``` + +The `aria-describedby` connects the error to the input for screen readers. + +## Loading States: Optimistic Updates + +**Show success immediately, handle failure gracefully.** Users perceive the app as faster. + +```javascript +// Optimistic update pattern +async function toggleLike() { + // 1. Update UI immediately + setLiked(true); + + try { + // 2. Send request + await api.like(postId); + } catch { + // 3. Rollback on failure + setLiked(false); + showToast('Like failed. Please try again.'); + } +} +``` + +**When to use**: Low-stakes actions (likes, follows, small edits). **Not for**: Payments, destructive actions, critical data changes. + +### Skeleton Screens > Spinners + +Spinners say "something is happening" but give no sense of what or how long. Skeletons preview the content shape: + +```css +.skeleton { + background: linear-gradient( + 90deg, + var(--gray-200) 25%, + var(--gray-100) 50%, + var(--gray-200) 75% + ); + background-size: 200% 100%; + animation: shimmer 1.5s infinite; +} + +@keyframes shimmer { + 0% { background-position: 200% 0; } + 100% { background-position: -200% 0; } +} +``` + +## Modals: The Inert Approach + +Focus trapping in modals used to require complex JavaScript. Now use the `inert` attribute: + +```html + +
+ +
+ +

Modal Title

+ + +``` + +Or use the native `` element: + +```javascript +const dialog = document.querySelector('dialog'); +dialog.showModal(); // Opens with focus trap, closes on Escape +``` + +## The Popover API + +For tooltips, dropdowns, and non-modal overlays, use native popovers: + +```html + + +``` + +**Benefits**: Light-dismiss (click outside closes), proper stacking, no z-index wars, accessible by default. + +## Destructive Actions: Undo > Confirm + +Confirmation dialogs are friction. Users click through them mindlessly. **Undo is better**: + +```javascript +async function deleteItem(id) { + // 1. Remove from UI immediately + hideItem(id); + + // 2. Show undo toast + const toast = showToast('Item deleted', { + action: { label: 'Undo', onClick: () => restoreItem(id) }, + duration: 5000 + }); + + // 3. Actually delete after toast expires + toast.onClose(() => api.delete(id)); +} +``` + +**When to still use confirmation**: Irreversible actions (account deletion), high-cost actions (large purchases), batch operations on many items. + +## Keyboard Navigation Patterns + +### Roving Tabindex + +For component groups (tabs, menu items, radio groups), one item is tabbable; arrow keys move within: + +```html +
+ + + +
+``` + +Arrow keys move `tabindex="0"` between items. Tab moves to the next component entirely. + +### Skip Links + +For keyboard users, provide a skip link to jump past navigation: + +```html + + +
...
+``` + +```css +.skip-link { + position: absolute; + left: -9999px; +} +.skip-link:focus { + left: 0; + z-index: 9999; + /* Visible styling */ +} +``` + +## Gesture Discoverability + +Swipe-to-delete and similar gestures are invisible. Hint at their existence: + +- **Partially reveal**: Show delete button peeking from edge +- **Onboarding**: Coach marks on first use +- **Alternative**: Always provide a visible fallback (menu with "Delete") + +Don't rely on gestures as the only way to perform actions. + +--- + +**IMPORTANT**: Test interactions with actual users and diverse input methods. What works with a mouse might fail with touch or keyboard. + +**NEVER**: +- Remove focus indicators without providing visible alternatives (accessibility violation) +- Use placeholder text as labels (disappears on input, hard to remember) +- Make touch targets smaller than 44x44px +- Validate in real-time for long inputs (wait for blur) +- Show generic error messages ("Error occurred") - be specific and helpful +- Block user interaction without clear loading states +- Design only for mouse/pointer (test with keyboard and touch) +- Use custom controls without proper ARIA and keyboard support + +Remember: Interaction design is where users actually experience your interface. Get this right, and everything else falls into place. diff --git a/.claude/skills/frontend-design/reference/motion-design.md b/.claude/skills/frontend-design/reference/motion-design.md new file mode 100644 index 000000000..23f738668 --- /dev/null +++ b/.claude/skills/frontend-design/reference/motion-design.md @@ -0,0 +1,225 @@ +# Motion Design + +This reference guides the creation of motion design that enhances usability, provides feedback, and creates delight - without sacrificing performance or accessibility. + +The user provides a motion challenge: adding animations to components, improving interaction feedback, building page transitions, creating micro-interactions, or establishing motion design systems. They may include performance constraints, aesthetic goals, or specific interaction problems to solve. + +## Motion Design Thinking + +Before animating anything, understand the purpose and context: + +- **Purpose**: Why animate? Feedback? Delight? Guidance? Branding? Every animation needs a reason beyond "it looks cool." +- **Personality**: What character should motion convey? Snappy and energetic? Smooth and luxurious? Playful and bouncy? Subtle and refined? +- **Performance Budget**: Mobile devices? Complex pages? Can we afford GPU-intensive animations? +- **Accessibility**: Motion sensitivity, vestibular disorders, reduced motion preferences - some users need minimal animation. + +**CRITICAL**: Animation should enhance understanding and usability, not obscure it. When in doubt, be subtle. Users notice janky animation more than no animation. + +Then implement motion that is: +- Purposeful with clear functional or emotional goals +- Performant with smooth 60fps execution +- Accessible with reduced motion alternatives +- Choreographed with thoughtful timing and sequencing + +## Duration: The 100/300/500 Rule + +Timing matters more than easing. These durations feel right for most UI: + +| Duration | Use Case | Examples | +|----------|----------|----------| +| **100-150ms** | Instant feedback | Button press, toggle, color change | +| **200-300ms** | State changes | Menu open, tooltip, hover states | +| **300-500ms** | Layout changes | Accordion, modal, drawer | +| **500-800ms** | Entrance animations | Page load, hero reveals | + +**Exit animations are faster than entrances.** Users want to see what's leaving—quickly. Use ~75% of the enter duration: +```css +.modal { + --enter: 400ms; + --exit: 300ms; +} +``` + +## Easing: Pick the Right Curve + +**Don't use `ease`.** It's a compromise that's rarely optimal. Instead: + +| Curve | Use For | CSS | +|-------|---------|-----| +| **ease-out** | Elements entering | `cubic-bezier(0.16, 1, 0.3, 1)` | +| **ease-in** | Elements leaving | `cubic-bezier(0.7, 0, 0.84, 0)` | +| **ease-in-out** | State toggles (there → back) | `cubic-bezier(0.65, 0, 0.35, 1)` | + +**For micro-interactions, use exponential curves**—they feel natural because they mimic real physics (friction, deceleration): + +```css +/* Quart out - smooth, refined (recommended default) */ +--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1); + +/* Quint out - slightly more dramatic */ +--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1); + +/* Expo out - snappy, confident */ +--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1); +``` + +**Avoid bounce and elastic curves.** They were trendy in 2015 but now feel tacky and amateurish. Real objects don't bounce when they stop—they decelerate smoothly. Overshoot effects draw attention to the animation itself rather than the content. + +## The Only Two Properties You Should Animate + +**transform** and **opacity**. That's it. Everything else causes layout recalculation or repaints: + +```css +/* Good: GPU-accelerated, smooth */ +.slide-in { + transform: translateX(0); + opacity: 1; + transition: transform 300ms ease-out, opacity 300ms ease-out; +} +.slide-in.hidden { + transform: translateX(20px); + opacity: 0; +} + +/* Bad: triggers layout, janky */ +.slide-in { + left: 0; /* Layout thrashing */ + height: 100%; /* Expensive */ +} +``` + +**Exceptions**: Sometimes you must animate `height` for accordions. Use `max-height` with a value larger than content, or better yet, use CSS Grid's `grid-template-rows: 0fr → 1fr` trick. + +## Staggered Animations + +Staggering creates rhythm and direction. The formula: + +```css +.list-item { + animation: fade-in 400ms ease-out both; +} + +/* Stagger each item by 50ms */ +.list-item:nth-child(1) { animation-delay: 0ms; } +.list-item:nth-child(2) { animation-delay: 50ms; } +.list-item:nth-child(3) { animation-delay: 100ms; } +/* ... */ +``` + +**Better approach with CSS custom property:** + +```css +.list-item { + animation: fade-in 400ms ease-out both; + animation-delay: calc(var(--i, 0) * 50ms); +} +``` +```html +
  • First
    • +
  • Second
    • +
  • Third
    • +``` + +**Key insight**: Cap the total stagger time. 10 items at 50ms = 500ms before the last item appears. If you have 50 items, reduce to 20ms per item or cap at ~10 staggered items. + +## Reduced Motion + +This is not optional. Vestibular disorders affect ~35% of adults over 40. + +```css +/* Define animations normally */ +.card { + animation: slide-up 500ms ease-out; +} + +/* Provide alternative for reduced motion */ +@media (prefers-reduced-motion: reduce) { + .card { + animation: fade-in 200ms ease-out; /* Crossfade instead of motion */ + } +} + +/* Or disable entirely */ +@media (prefers-reduced-motion: reduce) { + *, *::before, *::after { + animation-duration: 0.01ms !important; + transition-duration: 0.01ms !important; + } +} +``` + +**What to preserve**: Functional animations like progress bars, loading spinners (slowed down), and focus indicators should still work—just without spatial movement. + +## Performance: Avoid These Mistakes + +### Don't Use will-change Preemptively + +```css +/* Bad: wastes GPU memory */ +.card { will-change: transform; } + +/* Good: only when animation is imminent */ +.card:hover { will-change: transform; } +.card.animating { will-change: transform; } +``` + +`will-change` forces the browser to create a compositing layer. Used everywhere = memory bloat. + +### Don't Animate During Scroll + +Scroll-linked animations (parallax, reveal) are expensive. If you must: + +```javascript +// Use Intersection Observer, not scroll events +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + entry.target.classList.add('visible'); + observer.unobserve(entry.target); // Animate once, then stop observing + } + }); +}, { threshold: 0.2 }); +``` + +### Don't Fight the Main Thread + +Heavy JavaScript animations block rendering. For complex choreography, use the Web Animations API or a library like Motion One that schedules efficiently. + +## Motion Tokens + +Create a system for consistency: + +```css +:root { + /* Durations */ + --duration-instant: 100ms; + --duration-fast: 200ms; + --duration-normal: 300ms; + --duration-slow: 500ms; + + /* Easings */ + --ease-out: cubic-bezier(0.16, 1, 0.3, 1); + --ease-in: cubic-bezier(0.7, 0, 0.84, 0); + --ease-in-out: cubic-bezier(0.65, 0, 0.35, 1); + + /* Common patterns */ + --transition-fade: opacity var(--duration-fast) var(--ease-out); + --transition-slide: transform var(--duration-normal) var(--ease-out); + --transition-all: var(--duration-normal) var(--ease-out); +} +``` + +--- + +**IMPORTANT**: One well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions everywhere. Focus on high-impact moments. + +**NEVER**: +- Animate everything (animation fatigue is real) +- Use long durations (>500ms) for UI feedback (users will perceive lag) +- Animate layout properties (width, height, top, left) - use transform instead +- Ignore prefers-reduced-motion (accessibility requirement) +- Use animation to hide slow loading (fix the loading time) +- Animate without purpose (every animation should answer "why?") +- Create animations that obscure content or block interaction + +Remember: Motion is powerful - it can guide attention, provide feedback, and create emotional connection. Use it thoughtfully, not reflexively. diff --git a/.claude/skills/frontend-design/reference/responsive-design.md b/.claude/skills/frontend-design/reference/responsive-design.md new file mode 100644 index 000000000..c78563b7b --- /dev/null +++ b/.claude/skills/frontend-design/reference/responsive-design.md @@ -0,0 +1,272 @@ +# Responsive Design + +This reference guides the creation of responsive interfaces that adapt beautifully across devices, screen sizes, input methods, and usage contexts. + +The user provides a responsive design challenge: building mobile-first layouts, defining breakpoint strategies, optimizing for touch vs pointer, creating fluid designs, or solving specific cross-device problems. They may include device requirements, constraints, or specific adaptation challenges. + +## Responsive Design Thinking + +Before implementing, understand the multi-device context: + +- **Device Landscape**: Which devices matter? (Mobile, tablet, desktop, TV, watch?) What's the primary device? +- **Usage Context**: How do usage patterns differ by device? (On-the-go mobile vs focused desktop work) +- **Input Methods**: Touch, pointer, keyboard, voice, gamepad - what input methods need support? +- **Network Conditions**: Fast wifi vs slow 3G - how does this impact design decisions? +- **Content Priority**: What's essential on all devices vs optional on larger screens? + +**CRITICAL**: Responsive design is not just about scaling - it's about adapting the experience appropriately for each context. + +Then build responsive systems that are: +- Mobile-first with progressive enhancement +- Fluid and adaptable across viewport sizes +- Optimized for different input methods +- Performant on constrained devices +- Contextually appropriate + +## Mobile-First: Write It Right + +Start with base styles for mobile, then layer complexity: + +```css +/* Base: mobile */ +.nav { + display: flex; + flex-direction: column; +} + +/* Enhancement: tablet and up */ +@media (min-width: 768px) { + .nav { + flex-direction: row; + } +} +``` + +**The mistake**: Writing desktop-first (max-width queries) means mobile loads desktop styles first, then overrides. Wasteful and error-prone. + +## Breakpoints: Content-Driven, Not Device-Driven + +**Don't chase device sizes.** iPhones change, Android varies wildly, tablets overlap with laptops. Instead, let content tell you where to break: + +1. Start narrow +2. Stretch the viewport until the design breaks +3. Add a breakpoint there + +Common content-driven breakpoints (as starting points): + +```css +:root { + --bp-sm: 640px; /* Larger phones, small content changes */ + --bp-md: 768px; /* Tablets, significant reflow */ + --bp-lg: 1024px; /* Laptops, multi-column */ + --bp-xl: 1280px; /* Desktops, max content width */ +} +``` + +**Three breakpoints usually suffice.** If you have more than five, you're probably over-engineering. + +## Fluid Design: The Clamp Formula + +`clamp(min, preferred, max)` creates fluid values without media queries. + +### The Formula + +```css +/* Font size: 16px min, scales with viewport, 24px max */ +font-size: clamp(1rem, 0.5rem + 2vw, 1.5rem); +``` + +**How to calculate the preferred value**: The middle value determines the scaling rate. Higher vw coefficient = faster scaling: + +- `1vw` = gentle scaling +- `2-3vw` = moderate scaling +- `4vw+` = aggressive scaling + +Add a rem offset to shift the baseline: `0.5rem + 2vw` ensures it doesn't collapse to 0 on small screens. + +### Fluid Spacing + +```css +:root { + --space-lg: clamp(2rem, 1rem + 3vw, 4rem); + --container-padding: clamp(1rem, 5vw, 4rem); +} +``` + +This creates breathing room that naturally expands on larger screens. + +## Detect Input Method, Not Just Screen Size + +**Screen size doesn't tell you input method.** A laptop with touchscreen, a tablet with keyboard—use pointer and hover queries: + +```css +/* Fine pointer (mouse, trackpad) */ +@media (pointer: fine) { + .button { padding: 8px 16px; } +} + +/* Coarse pointer (touch, stylus) */ +@media (pointer: coarse) { + .button { padding: 12px 20px; } /* Larger touch target */ +} + +/* Device supports hover */ +@media (hover: hover) { + .card:hover { transform: translateY(-2px); } +} + +/* Device doesn't support hover (touch) */ +@media (hover: none) { + .card { /* No hover state - use active instead */ } +} +``` + +**Critical**: Don't rely on hover for functionality. Touch users can't hover. + +## Safe Areas: Handle the Notch + +Modern phones have notches, rounded corners, and home indicators. Use `env()`: + +```css +body { + padding-top: env(safe-area-inset-top); + padding-bottom: env(safe-area-inset-bottom); + padding-left: env(safe-area-inset-left); + padding-right: env(safe-area-inset-right); +} + +/* With fallback */ +.footer { + padding-bottom: max(1rem, env(safe-area-inset-bottom)); +} +``` + +**Enable viewport-fit** in your meta tag: +```html + +``` + +## Responsive Images: Get It Right + +### srcset with Width Descriptors + +```html +Hero image +``` + +**How it works**: +- `srcset` lists available images with their actual widths (`w` descriptors) +- `sizes` tells the browser how wide the image will display +- Browser picks the best file based on viewport width AND device pixel ratio + +### Picture Element for Art Direction + +When you need different crops/compositions (not just resolutions): + +```html + + + + ... + +``` + +## Layout Adaptation Patterns + +### Navigation: The Three-Stage Pattern + +```css +/* Mobile: hamburger icon + drawer */ +.nav-menu { display: none; } +.nav-toggle { display: block; } + +/* Tablet: horizontal but compact */ +@media (min-width: 768px) { + .nav-menu { display: flex; } + .nav-toggle { display: none; } +} + +/* Desktop: full navigation with labels */ +@media (min-width: 1024px) { + .nav-item-label { display: inline; } +} +``` + +### Table to Cards + +Tables work on desktop, fail on mobile. Transform: + +```css +@media (max-width: 768px) { + table, thead, tbody, th, td, tr { + display: block; + } + + thead { display: none; } /* Hide headers */ + + tr { + margin-bottom: 1rem; + border: 1px solid var(--border); + padding: 1rem; + } + + td::before { + content: attr(data-label); /* Add labels via data attribute */ + font-weight: 600; + display: block; + } +} +``` + +### Progressive Disclosure + +Not everything needs to show on mobile: + +```css +/* Show summary on mobile */ +.details-content { display: none; } + +@media (min-width: 768px) { + /* Expand on desktop */ + .details-content { display: block; } +} +``` + +Combine with `
    /` for interactive expansion on mobile. + +## Testing: Don't Trust DevTools Alone + +DevTools device emulation is useful for layout but misses: + +- Actual touch interactions +- Real CPU/memory constraints +- Network latency patterns +- Font rendering differences +- Browser chrome/keyboard appearances + +**Test on at least**: One real iPhone, one real Android, a tablet if relevant. Cheap Android phones reveal performance issues you'll never see on simulators. + +--- + +**IMPORTANT**: Test on real devices, not just DevTools. Device emulation is useful but misses real-world constraints. + +**NEVER**: +- Design desktop-first and try to cram into mobile +- Hide critical functionality on mobile +- Use device detection instead of feature detection +- Create separate mobile/desktop codebases (maintain one responsive codebase) +- Ignore landscape orientation +- Use fixed pixel values without considering smaller/larger screens +- Forget about tablet (it's not just big phone or small desktop) +- Assume all mobile devices are powerful (many users have older devices) + +Remember: Responsive design is about creating experiences that work everywhere while feeling native nowhere. Adapt intelligently for context while maintaining consistency. diff --git a/.claude/skills/frontend-design/reference/spatial-design.md b/.claude/skills/frontend-design/reference/spatial-design.md new file mode 100644 index 000000000..4dfe26d24 --- /dev/null +++ b/.claude/skills/frontend-design/reference/spatial-design.md @@ -0,0 +1,297 @@ +# Spatial Design + +This reference guides the creation of spatial systems that balance mathematical precision with artistic composition, ensuring interfaces are both systematically organized and visually compelling. + +The user provides a layout challenge: building spacing systems, establishing grids, improving visual hierarchy, fixing composition issues, or implementing responsive layouts. They may include design system constraints, aesthetic goals, or specific spatial problems to solve. + +## Spatial Design Thinking + +Before arranging elements, understand the compositional strategy: + +- **Content Priority**: What's most important? What should users see first, second, third? Hierarchy starts here. +- **Visual Weight Distribution**: Where should the eye go? Balanced or intentionally unbalanced? Symmetrical or asymmetric? +- **Density vs Breathing Room**: Controlled density (information-rich) or generous space (editorial)? Match context and audience. +- **Reading Patterns**: Z-pattern (scanning), F-pattern (text-heavy), focal point (marketing), free-form (experimental)? + +**CRITICAL**: Space is not empty - it's an active design element. Negative space gives positive elements room to breathe and meaning. + +Then build layout systems that are: +- Systematically consistent with clear spacing rules +- Visually balanced with intentional hierarchy +- Responsive and adaptive across viewports +- Compositionally strong with clear focal points + +## Spacing Systems + +### Use 4pt Base, Not 8pt + +8pt systems are too coarse. **4pt gives you the granularity you actually need:** + +```css +:root { + --space-1: 4px; /* 0.25rem - tight */ + --space-2: 8px; /* 0.5rem */ + --space-3: 12px; /* 0.75rem */ + --space-4: 16px; /* 1rem - base */ + --space-6: 24px; /* 1.5rem */ + --space-8: 32px; /* 2rem */ + --space-12: 48px; /* 3rem */ + --space-16: 64px; /* 4rem */ + --space-24: 96px; /* 6rem - section gaps */ +} +``` + +**The insight**: You'll frequently need 12px (between 8 and 16). An 8pt-only system forces awkward choices. + +### Name Tokens by Relationship, Not Value + +```css +/* Bad: tied to pixels */ +--spacing-8: 8px; +--spacing-16: 16px; + +/* Better: semantic */ +--space-xs: 4px; /* Tight inline gaps */ +--space-sm: 8px; /* Between related elements */ +--space-md: 16px; /* Component padding */ +--space-lg: 24px; /* Between components */ +--space-xl: 48px; /* Section padding */ +--space-2xl: 96px; /* Section margins */ +``` + +### Gap Over Margin + +**Stop using margins for spacing between siblings.** Use `gap`: + +```css +/* Old way: margins create double-spacing bugs */ +.card { margin-bottom: 16px; } +.card:last-child { margin-bottom: 0; } /* Cleanup hack */ + +/* Modern way: gap just works */ +.card-list { + display: flex; + flex-direction: column; + gap: 16px; /* Automatic, no cleanup needed */ +} +``` + +Gap works in Flexbox and Grid. It's cleaner, more intentional, and eliminates margin collapse headaches. + +## Grid Systems + +### The Self-Adjusting Grid + +This pattern creates responsive grids without breakpoints: + +```css +.grid { + display: grid; + grid-template-columns: repeat(auto-fit, minmax(280px, 1fr)); + gap: var(--space-lg); +} +``` + +**How it works**: Columns are at least 280px. As many as fit per row. Leftovers stretch. No media queries needed. + +**Variation for exact counts:** +```css +/* Always 3 columns on desktop, stack on mobile */ +.grid-3 { + display: grid; + grid-template-columns: repeat(auto-fit, minmax(min(280px, 100%), 1fr)); + gap: var(--space-lg); +} +``` + +### Grid Area Naming + +For complex layouts, named areas are clearer than line numbers: + +```css +.page { + display: grid; + grid-template-areas: + "header header" + "sidebar main" + "footer footer"; + grid-template-columns: 280px 1fr; + grid-template-rows: auto 1fr auto; +} + +.header { grid-area: header; } +.sidebar { grid-area: sidebar; } +.main { grid-area: main; } +.footer { grid-area: footer; } +``` + +At mobile breakpoints, redefine the areas: +```css +@media (max-width: 768px) { + .page { + grid-template-areas: + "header" + "main" + "sidebar" + "footer"; + grid-template-columns: 1fr; + } +} +``` + +## Visual Hierarchy + +### The Squint Test + +Blur your eyes (or screenshot and blur). Can you still identify: +- The most important element? +- The second most important? +- Clear groupings? + +If everything looks the same weight blurred, you have a hierarchy problem. + +### Hierarchy Through Multiple Dimensions + +Don't rely on size alone. Combine: + +| Tool | Strong Hierarchy | Weak Hierarchy | +|------|------------------|----------------| +| **Size** | 3:1 ratio or more | <2:1 ratio | +| **Weight** | Bold vs Regular | Medium vs Regular | +| **Color** | High contrast | Similar tones | +| **Position** | Top/left (primary) | Bottom/right | +| **Space** | Surrounded by white space | Crowded | + +**The best hierarchy uses 2-3 dimensions at once**: A heading that's larger, bolder, AND has more space above it. + +### Cards Are Not Required + +Cards (bordered/shadowed containers) are overused. You don't need a card to create visual grouping—spacing and alignment do this naturally. + +**Use cards when**: +- Content is truly distinct and actionable (a product, a post, a task) +- Items need to be visually comparable in a grid +- Content needs clear boundaries for interaction (hover, click) + +**Don't use cards for**: +- General layout structure (use spacing instead) +- Single items (a lone card looks arbitrary) +- Nesting—**never put cards inside cards**. If you need hierarchy within a card, use spacing, typography, and subtle dividers instead + +```css +/* Bad: card in a card */ +.outer-card > .inner-card { /* Noisy and confusing */ } + +/* Good: hierarchy without nesting */ +.card > .card-section { border-top: 1px solid var(--border); } +``` + +## Container Queries + +Viewport queries are for page layouts. **Container queries are for components**: + +```css +.card-container { + container-type: inline-size; +} + +.card { + display: grid; + gap: var(--space-md); +} + +/* Card layout changes based on its container, not viewport */ +@container (min-width: 400px) { + .card { + grid-template-columns: 120px 1fr; + } +} +``` + +**Why this matters**: A card in a narrow sidebar stays compact, while the same card in a main content area expands—automatically, without viewport hacks. + +## Optical Adjustments + +### Text Doesn't Align + +A paragraph set to `margin-left: 0` looks indented because letterforms have internal whitespace. Fix with negative margin or padding: + +```css +.heading { + margin-left: -0.05em; /* Pull left to optically align */ +} +``` + +### Icons Need Optical Centering + +A geometrically centered icon often looks off-center. Play icons need to shift right, left-arrows need to shift left: + +```css +.play-button svg { + transform: translateX(2px); /* Optical center */ +} +``` + +### Touch Targets vs Visual Size + +Buttons can look small but need large touch targets (44px minimum). Use padding or pseudo-elements: + +```css +.icon-button { + width: 24px; /* Visual size */ + height: 24px; + position: relative; +} + +.icon-button::before { + content: ''; + position: absolute; + inset: -10px; /* Expand tap target to 44px */ +} +``` + +## Depth & Elevation + +### Semantic Z-Index + +Don't use arbitrary numbers. Create a scale: + +```css +:root { + --z-dropdown: 100; + --z-sticky: 200; + --z-modal-backdrop: 300; + --z-modal: 400; + --z-toast: 500; + --z-tooltip: 600; +} +``` + +### Shadow Scale for Elevation + +Shadows indicate elevation. Create a consistent scale: + +```css +:root { + --shadow-sm: 0 1px 2px rgba(0,0,0,0.05); /* Subtle lift */ + --shadow-md: 0 4px 6px rgba(0,0,0,0.07); /* Cards */ + --shadow-lg: 0 10px 15px rgba(0,0,0,0.1); /* Dropdowns */ + --shadow-xl: 0 20px 25px rgba(0,0,0,0.15); /* Modals */ +} +``` + +**Key insight**: Shadows should be subtle. If you can clearly see the shadow, it's probably too strong. + +--- + +**IMPORTANT**: Systematic spacing doesn't mean boring. Use the system as a foundation, then break it intentionally for impact. + +**NEVER**: +- Use arbitrary spacing values outside your scale (unless intentionally breaking the system) +- Create layouts that ignore natural reading patterns without good reason +- Forget that white space is a design element, not wasted space +- Make all spacing equal (variety creates hierarchy) +- Build responsive layouts that only work at breakpoint edges +- Create hierarchy through size alone (combine multiple tools) + +Remember: Composition is the invisible structure that makes everything else work. Master the fundamentals, then break rules intentionally. diff --git a/.claude/skills/frontend-design/reference/typography.md b/.claude/skills/frontend-design/reference/typography.md new file mode 100644 index 000000000..9874ab641 --- /dev/null +++ b/.claude/skills/frontend-design/reference/typography.md @@ -0,0 +1,240 @@ +# Typography + +This reference guides the creation and refinement of typography systems that balance timeless principles with modern web capabilities. + +The user provides a typography challenge: building a type system, improving readability, selecting fonts, fixing hierarchy, or implementing responsive typography. They may include context about the project's aesthetic direction, constraints, or specific problems to solve. + +## Typography Thinking + +Before implementing, understand the context and establish a clear typographic voice: + +- **Purpose & Audience**: What is being communicated? Who is reading? Technical docs need different type than marketing pages. +- **Tone & Character**: What personality should the typography convey? Authoritative? Playful? Elegant? Minimal? The fonts and system should embody this. +- **Constraints**: Performance budgets, browser support, existing design system, accessibility requirements. +- **Reading Context**: Long-form reading vs scanning, dense information vs spacious editorial, desktop vs mobile primary usage. + +**CRITICAL**: Typography is the voice of your interface. Invest time in getting it right - it impacts every single screen. + +Then build or refine a typography system that is: +- Readable and accessible across devices and contexts +- Systematically coherent with clear hierarchy +- Performant and technically sound +- Aesthetically distinctive and appropriate for the brand + +## Classic Typography Principles + +### Vertical Rhythm + +The non-obvious insight: your line-height should be the base unit for ALL vertical spacing in your design. If body text has `line-height: 1.5` on `16px` type (= 24px), then spacing values should be multiples of 24px: 24, 48, 72, etc. + +This creates subconscious harmony. Text and space feel "right" together because they share a mathematical foundation. + +```css +:root { + --baseline: 1.5rem; /* 24px if root is 16px */ + --space-1: var(--baseline); /* 24px */ + --space-2: calc(var(--baseline) * 2); /* 48px */ + --space-half: calc(var(--baseline) / 2); /* 12px */ +} +``` + +### Modular Scale & Hierarchy + +The common mistake: too many font sizes that are too close together (14px, 15px, 16px, 18px...). This creates muddy hierarchy. + +**Use fewer sizes with more contrast.** A 5-size system covers most needs: + +| Role | Typical Ratio | Use Case | +|------|---------------|----------| +| xs | 0.75rem | Captions, legal | +| sm | 0.875rem | Secondary UI, metadata | +| base | 1rem | Body text | +| lg | 1.25-1.5rem | Subheadings, lead text | +| xl+ | 2-4rem | Headlines, hero text | + +Popular ratios: 1.25 (major third), 1.333 (perfect fourth), 1.5 (perfect fifth). Pick one and commit. + +### Readability & Measure + +Line length (measure) guidelines are well-known (45-75 characters), but the implementation detail matters: + +```css +/* Use ch units for true character-based measure */ +.prose { max-width: 65ch; } + +/* Line-height scales inversely with line length */ +.narrow-column { max-width: 45ch; line-height: 1.4; } +.wide-column { max-width: 75ch; line-height: 1.6; } +``` + +**Non-obvious**: Increase line-height for light text on dark backgrounds. The perceived weight is lighter, so text needs more breathing room. Add 0.05-0.1 to your normal line-height. + +## Font Selection & Pairing + +### Choosing Distinctive Fonts + +**Avoid the invisible defaults**: Inter, Roboto, Open Sans, Lato, Montserrat. These are everywhere, making your design feel generic. They're fine for documentation or tools where personality isn't the goal—but if you want distinctive design, look elsewhere. + +**Better Google Fonts alternatives**: +- Instead of Inter → **Instrument Sans**, **Plus Jakarta Sans**, **Outfit** +- Instead of Roboto → **Onest**, **Figtree**, **Urbanist** +- Instead of Open Sans → **Source Sans 3**, **Nunito Sans**, **DM Sans** +- For editorial/premium feel → **Fraunces**, **Newsreader**, **Lora** + +**System fonts are underrated**: `-apple-system, BlinkMacSystemFont, "Segoe UI", system-ui` looks native, loads instantly, and is highly readable. Consider this for apps where performance > personality. + +### Pairing Principles + +**The non-obvious truth**: You often don't need a second font. One well-chosen font family in multiple weights creates cleaner hierarchy than two competing typefaces. Only add a second font when you need genuine contrast (e.g., display headlines + body serif). + +When pairing, contrast on multiple axes: +- Serif + Sans (structure contrast) +- Geometric + Humanist (personality contrast) +- Condensed display + Wide body (proportion contrast) + +**Never pair fonts that are similar but not identical** (e.g., two geometric sans-serifs). They create visual tension without clear hierarchy. + +### Web Font Loading + +The layout shift problem: fonts load late, text reflows, and users see content jump. Here's the fix: + +```css +/* 1. Use font-display: swap for visibility */ +@font-face { + font-family: 'CustomFont'; + src: url('font.woff2') format('woff2'); + font-display: swap; +} + +/* 2. Match fallback metrics to minimize shift */ +@font-face { + font-family: 'CustomFont-Fallback'; + src: local('Arial'); + size-adjust: 105%; /* Scale to match x-height */ + ascent-override: 90%; /* Match ascender height */ + descent-override: 20%; /* Match descender depth */ + line-gap-override: 10%; /* Match line spacing */ +} + +body { + font-family: 'CustomFont', 'CustomFont-Fallback', sans-serif; +} +``` + +Tools like [Fontaine](https://github.com/unjs/fontaine) calculate these overrides automatically. + +## Modern Web Typography + +### Fluid Type + +Fluid typography eliminates breakpoint jumps. The formula: + +```css +/* font-size: clamp(min, preferred, max) */ +h1 { font-size: clamp(2rem, 5vw + 1rem, 4rem); } +``` + +The `5vw + 1rem` creates smooth scaling. Adjust the vw coefficient for faster/slower scaling. + +**When NOT to use fluid type**: +- Button text, labels, UI elements (should be consistent, not fluid) +- Very short text (scaling makes less sense) +- When you need precise control at specific breakpoints + +### OpenType Features + +Most developers don't know these exist. Use them for polish: + +```css +/* Tabular numbers for data alignment */ +.data-table { font-variant-numeric: tabular-nums; } + +/* Proper fractions */ +.recipe-amount { font-variant-numeric: diagonal-fractions; } + +/* Small caps for abbreviations */ +abbr { font-variant-caps: all-small-caps; } + +/* Disable ligatures in code */ +code { font-variant-ligatures: none; } + +/* Enable kerning (usually on by default, but be explicit) */ +body { font-kerning: normal; } +``` + +Check what features your font supports at [Wakamai Fondue](https://wakamaifondue.com/). + +## Typography System Architecture + +### Token Structure + +**Name tokens semantically, not by value**: + +```css +/* Bad: tied to implementation */ +--font-size-16: 1rem; +--font-size-24: 1.5rem; + +/* Good: tied to purpose */ +--font-size-body: 1rem; +--font-size-heading: 1.5rem; +``` + +A complete token set: + +```css +:root { + /* Font stacks */ + --font-sans: 'CustomSans', system-ui, sans-serif; + --font-serif: 'CustomSerif', Georgia, serif; + --font-mono: 'JetBrains Mono', ui-monospace, monospace; + + /* Size scale (semantic) */ + --text-xs: 0.75rem; + --text-sm: 0.875rem; + --text-base: 1rem; + --text-lg: 1.25rem; + --text-xl: 1.5rem; + --text-2xl: 2rem; + --text-3xl: 3rem; + + /* Weight */ + --font-normal: 400; + --font-medium: 500; + --font-semibold: 600; + --font-bold: 700; + + /* Line height */ + --leading-tight: 1.25; + --leading-normal: 1.5; + --leading-relaxed: 1.75; + + /* Letter spacing */ + --tracking-tight: -0.02em; + --tracking-normal: 0; + --tracking-wide: 0.05em; +} +``` + +## Accessibility Considerations + +Beyond contrast ratios (which are well-documented), consider: + +- **Never disable zoom**: `user-scalable=no` breaks accessibility. If your layout breaks at 200% zoom, fix the layout. +- **Use rem/em for font sizes**: This respects user browser settings. Never `px` for body text. +- **Minimum 16px body text**: Smaller than this strains eyes and fails WCAG on mobile. +- **Adequate touch targets**: Text links need padding or line-height that creates 44px+ tap targets. + +--- + +**IMPORTANT**: Balance trendy font choices with timeless readability principles. A distinctive font is worthless if users can't comfortably read it. + +**NEVER**: +- Use more than 2-3 font families in a single project +- Sacrifice readability for aesthetic novelty +- Ignore font loading performance +- Skip fallback font definitions +- Use decorative fonts for body text +- Implement arbitrary font sizes without a systematic scale + +Remember: Typography is 95% of design. Master it, and everything else becomes easier. diff --git a/.claude/skills/frontend-design/reference/ux-writing.md b/.claude/skills/frontend-design/reference/ux-writing.md new file mode 100644 index 000000000..b2e833e73 --- /dev/null +++ b/.claude/skills/frontend-design/reference/ux-writing.md @@ -0,0 +1,299 @@ +# UX Writing + +This reference guides the creation of interface copy that is clear, concise, helpful, and human - the words that make products understandable and usable. + +The user provides a UX writing challenge: writing microcopy, improving error messages, crafting instructions, establishing voice and tone, or fixing unclear interface text. They may include brand guidelines, audience context, or specific copy problems to solve. + +## UX Writing Thinking + +Before writing, understand the context and user needs: + +- **User Context**: What are users trying to accomplish? What's their emotional state? What do they already know? +- **Content Purpose**: Inform? Guide? Reassure? Warn? Celebrate? Different moments need different approaches. +- **Brand Voice**: Professional? Casual? Playful? Technical? Voice should match brand and audience. +- **Constraints**: Character limits, space limitations, translation considerations, accessibility requirements. + +**CRITICAL**: Good UX writing is invisible - users understand immediately without noticing the words. Bad UX writing creates confusion and frustration. + +Then write copy that is: +- Clear and immediately understandable +- Concise without sacrificing clarity +- Helpful and action-oriented +- Human and empathetic +- Consistent in terminology and tone + +## The Button Label Problem + +**Never use "OK", "Submit", or "Yes/No".** These are lazy and ambiguous. Use specific verb + object patterns: + +| Bad | Good | Why | +|-----|------|-----| +| OK | Save changes | Says what will happen | +| Submit | Create account | Outcome-focused | +| Yes | Delete message | Confirms the action | +| Cancel | Keep editing | Clarifies what "cancel" means | +| Click here | Download PDF | Describes the destination | + +**For destructive actions**, name the destruction: +- "Delete" not "Remove" (delete is permanent, remove implies recoverable) +- "Delete 5 items" not "Delete selected" (show the count) + +## Error Messages: The Formula + +Every error message should answer three questions: + +1. **What happened?** (Clearly state the problem) +2. **Why?** (If not obvious) +3. **How to fix it?** (Specific action) + +``` +Bad: "Invalid input" + +Good: "Email address isn't valid. Please include an @ symbol." + +Bad: "Request failed" + +Good: "We couldn't save your changes. Check your internet connection and try again." +``` + +### Error Message Templates + +| Situation | Template | +|-----------|----------| +| **Format error** | "[Field] needs to be [format]. Example: [example]" | +| **Missing required** | "Please enter [what's missing]" | +| **Permission denied** | "You don't have access to [thing]. [What to do instead]" | +| **Network error** | "We couldn't reach [thing]. Check your connection and [action]." | +| **Server error** | "Something went wrong on our end. We're looking into it. [Alternative action]" | + +### Don't Blame the User + +``` +Bad: "You entered an invalid date" +Good: "Please enter a date in MM/DD/YYYY format" + +Bad: "Your password is too weak" +Good: "Add at least one number or symbol to strengthen your password" +``` + +## Empty States Are Opportunities + +An empty list isn't a dead end—it's an onboarding moment. + +``` +Bad: "No items" + +Good: "No projects yet + Projects help you organize your work. Create your first one to get started. + [+ Create project]" +``` + +**Empty state formula**: +1. Acknowledge the emptiness (briefly) +2. Explain the value of filling it +3. Provide a clear action + +## Voice vs Tone + +**Voice** is your brand's personality—consistent everywhere. +**Tone** adapts to the moment. + +| Moment | Tone Shift | +|--------|------------| +| Success | Celebratory, brief: "Done! Your changes are live." | +| Error | Empathetic, helpful: "That didn't work. Here's what to try..." | +| Loading | Reassuring: "Saving your work..." | +| Destructive confirm | Serious, clear: "Delete this project? This can't be undone." | + +**Never use humor for errors.** Users are already frustrated. Be helpful, not cute. + +## Writing for Accessibility + +### Link Text + +Screen readers can navigate by links. Vague links fail: + +```html + +Click here +Learn more + + +View pricing plans +Learn more about data export +``` + +### Alt Text + +Describe the **information**, not the image: + +```html + +Chart + + +Revenue increased 40% in Q4 + + + +``` + +### Button Context + +Buttons need context, especially icons: + +```html + + + + + +``` + +## Writing for Translation + +### Plan for Expansion + +German text is ~30% longer than English. Allocate space: + +| Language | Expansion | +|----------|-----------| +| German | +30% | +| French | +20% | +| Finnish | +30-40% | +| Chinese | -30% (fewer chars, but same width) | + +### Translation-Friendly Patterns + +``` +Bad: "You have 3 new messages" (number inside sentence) +Good: "New messages: 3" (number separate) + +Bad: "Welcome back, {name}!" (word order varies by language) +Good: "{greeting_message}" (full sentence as one string) + +Bad: "5 mins ago" (abbrev doesn't translate) +Good: "5 minutes ago" (full word) +``` + +### Give Translators Context + +```json +{ + "delete_confirm": { + "message": "Delete {item}?", + "context": "Confirmation dialog when deleting a file or folder. {item} is the name of the item being deleted." + } +} +``` + +## Consistency: The Terminology Problem + +Pick one term and stick with it: + +| Inconsistent | Consistent | +|--------------|------------| +| Delete / Remove / Trash | Delete | +| Settings / Preferences / Options | Settings | +| Sign in / Log in / Enter | Sign in | +| Create / Add / New | Create | + +Build a terminology glossary and enforce it. Variety creates confusion. + +## Avoid Redundant Copy + +Saying the same thing twice wastes space and dilutes impact. + +**Common redundancies**: +- Section header + intro paragraph saying the same thing +- Page title + section title with same/similar text +- CTA button + surrounding text repeating the action +- Outro that restates the intro + +``` +Bad: "Settings" + "Here you can adjust your settings and preferences." + [Settings form] + "Save your settings to apply changes." + +Good: "Settings" + [Settings form] + [Save] +``` + +**The rule**: If the heading explains it, the intro is redundant. If the button is clear, don't explain it again. Say it once, say it well. + +## Loading States + +Tell users what's happening: + +``` +Bad: "Loading..." +Good: "Saving your draft..." + +Bad: [spinner] +Good: "Searching 1,247 documents..." + +Bad: "Please wait" +Good: "Preparing your download... This usually takes 30 seconds." +``` + +For long waits, show progress or set expectations. + +## Confirmation Dialogs: Use Sparingly + +**Most confirmation dialogs are design failures.** If an action is dangerous enough to confirm, consider: +- Undo instead of confirm +- Making the action less destructive +- Showing consequences before the action + +When you must confirm: + +``` +Bad: "Are you sure?" + [Yes] [No] + +Good: "Delete 'Project Alpha'? + This will permanently delete the project and all its files. + [Delete project] [Keep project]" +``` + +Name the action, explain consequences, use specific button labels. + +## Form Instructions + +### Format Hints + +Show don't tell: + +``` +Bad: "Enter date in MMDDYYYY format" +Good: "Date of birth" + placeholder="04/15/1990" +``` + +### Why Are You Asking? + +For non-obvious fields, explain: + +```html + +We'll only use this to contact you about your order. +``` + +--- + +**IMPORTANT**: Read your copy out loud. If it sounds awkward or robotic, rewrite until it sounds human. + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" - explain what!) +- Use passive voice unnecessarily +- Vary terminology for variety (consistency matters) +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic) +- Assume technical knowledge +- Use all caps (except acronyms) +- End questions with periods (use question marks) + +Remember: You're a clarity expert and empathetic communicator. Write like you're helping a friend who's smart but unfamiliar with your product. Be clear, be helpful, be human. diff --git a/scripts/build.js b/scripts/build.js index 556cd5edb..4215baf50 100644 --- a/scripts/build.js +++ b/scripts/build.js @@ -11,6 +11,7 @@ */ import path from 'path'; +import fs from 'fs'; import { fileURLToPath } from 'url'; import { readSourceFiles, readPatterns } from './lib/utils.js'; import { @@ -21,6 +22,23 @@ import { } from './lib/transformers/index.js'; import { createAllZips } from './lib/zip.js'; +/** + * Copy directory recursively + */ +function copyDirSync(src, dest) { + fs.mkdirSync(dest, { recursive: true }); + const entries = fs.readdirSync(src, { withFileTypes: true }); + for (const entry of entries) { + const srcPath = path.join(src, entry.name); + const destPath = path.join(dest, entry.name); + if (entry.isDirectory()) { + copyDirSync(srcPath, destPath); + } else { + fs.copyFileSync(srcPath, destPath); + } + } +} + const __filename = fileURLToPath(import.meta.url); const __dirname = path.dirname(__filename); const ROOT_DIR = path.resolve(__dirname, '..'); @@ -45,7 +63,26 @@ async function build() { // Create ZIP bundles await createAllZips(DIST_DIR); - + + // Copy Claude Code output to project's .claude directory for local development + const claudeCodeSrc = path.join(DIST_DIR, 'claude-code', '.claude'); + const claudeCodeDest = path.join(ROOT_DIR, '.claude'); + + // Copy commands and skills directories (preserves other files like settings.local.json) + const commandsSrc = path.join(claudeCodeSrc, 'commands'); + const skillsSrc = path.join(claudeCodeSrc, 'skills'); + const commandsDest = path.join(claudeCodeDest, 'commands'); + const skillsDest = path.join(claudeCodeDest, 'skills'); + + // Remove existing and copy fresh + if (fs.existsSync(commandsDest)) fs.rmSync(commandsDest, { recursive: true }); + if (fs.existsSync(skillsDest)) fs.rmSync(skillsDest, { recursive: true }); + + copyDirSync(commandsSrc, commandsDest); + copyDirSync(skillsSrc, skillsDest); + + console.log(`📋 Synced to .claude/: commands + skills`); + console.log('\n✨ Build complete!'); }