monomind 1.19.0 → 2.0.0

package/.claude/skills/monodesign/reference/delight.md

@@ -1,302 +0,0 @@
-> **Additional context needed**: what's appropriate for the domain (playful vs professional vs quirky vs elegant).
-
-Find the moments where personality and unexpected polish would turn a functional interface into one users remember and tell other people about. Add only where the moment earns it; delight everywhere reads as noise.
-
----
-
-## Register
-
-Brand: delight can be distributed across copy voice, section transitions, discovery rewards, seasonal touches, personality across the whole surface.
-
-Product: delight at specific moments, not pages. Completion, first-time actions, error recovery, milestone crossings. Reliability and consistency carry the rest of the experience; delight pushed everywhere reads as noise.
-
----
-
-## Assess Delight Opportunities
-
-Identify where delight would enhance (not distract from) the experience:
-
-1. **Find natural delight moments**:
-   - **Success states**: Completed actions (save, send, publish)
-   - **Empty states**: First-time experiences, onboarding
-   - **Loading states**: Waiting periods that could be entertaining
-   - **Achievements**: Milestones, streaks, completions
-   - **Interactions**: Hover states, clicks, drags
-   - **Errors**: Softening frustrating moments
-   - **Easter eggs**: Hidden discoveries for curious users
-
-2. **Understand the context**:
-   - What's the brand personality? (Playful? Professional? Quirky? Elegant?)
-   - Who's the audience? (Tech-savvy? Creative? Corporate?)
-   - What's the emotional context? (Accomplishment? Exploration? Frustration?)
-   - What's appropriate? (Banking app ≠ gaming app)
-
-3. **Define delight strategy**:
-   - **Subtle sophistication**: Refined micro-interactions (luxury brands)
-   - **Playful personality**: Whimsical illustrations and copy (consumer apps)
-   - **Helpful surprises**: Anticipating needs before users ask (productivity tools)
-   - **Sensory richness**: Satisfying sounds, smooth animations (creative tools)
-
-If any of these are unclear from the codebase, Ask the user for clarification before proceeding.
-
-**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far.
-
-## Delight Principles
-
-Follow these guidelines:
-
-### Delight Amplifies, Never Blocks
-- Delight moments should be quick (< 1 second)
-- Never delay core functionality for delight
-- Make delight skippable or subtle
-- Respect user's time and task focus
-
-### Surprise and Discovery
-- Hide delightful details for users to discover
-- Reward exploration and curiosity
-- Don't announce every delight moment
-- Let users share discoveries with others
-
-### Appropriate to Context
-- Match delight to emotional moment (celebrate success, empathize with errors)
-- Respect the user's state (don't be playful during critical errors)
-- Match brand personality and audience expectations
-- Cultural sensitivity (what's delightful varies by culture)
-
-### Compound Over Time
-- Delight should remain fresh with repeated use
-- Vary responses (not same animation every time)
-- Reveal deeper layers with continued use
-- Build anticipation through patterns
-
-## Delight Techniques
-
-Add personality and joy through these methods:
-
-### Micro-interactions & Animation
-
-**Button delight**:
-```css
-/* Satisfying button press */
-.button {
-  transition: transform 0.1s, box-shadow 0.1s;
-}
-.button:active {
-  transform: translateY(2px);
-  box-shadow: 0 2px 4px rgba(0,0,0,0.2);
-}
-
-/* Ripple effect on click */
-/* Smooth lift on hover */
-.button:hover {
-  transform: translateY(-2px);
-  transition: transform 0.2s cubic-bezier(0.25, 1, 0.5, 1); /* ease-out-quart */
-}
-```
-
-**Loading delight**:
-- Playful loading animations (not just spinners)
-- Personality in loading messages (write product-specific ones, not generic AI filler)
-- Progress indication with encouraging messages
-- Skeleton screens with subtle animations
-
-**Success animations**:
-- Checkmark draw animation
-- Confetti burst for major achievements
-- Gentle scale + fade for confirmation
-- Satisfying sound effects (subtle)
-
-**Hover surprises**:
-- Icons that animate on hover
-- Color shifts or glow effects
-- Tooltip reveals with personality
-- Cursor changes (custom cursors for branded experiences)
-
-### Personality in Copy
-
-**Playful error messages**:
-```
-"Error 404"
-"This page is playing hide and seek. (And winning)"
-
-"Connection failed"
-"Looks like the internet took a coffee break. Want to retry?"
-```
-
-**Encouraging empty states**:
-```
-"No projects"
-"Your canvas awaits. Create something amazing."
-
-"No messages"
-"Inbox zero! You're crushing it today."
-```
-
-**Playful labels & tooltips**:
-```
-"Delete"
-"Send to void" (for playful brand)
-
-"Help"
-"Rescue me" (tooltip)
-```
-
-**IMPORTANT**: Match copy personality to brand. Banks shouldn't be wacky, but they can be warm.
-
-### Illustrations & Visual Personality
-
-**Custom illustrations**:
-- Empty state illustrations (not stock icons)
-- Error state illustrations (friendly monsters, quirky characters)
-- Loading state illustrations (animated characters)
-- Success state illustrations (celebrations)
-
-**Icon personality**:
-- Custom icon set matching brand personality
-- Animated icons (subtle motion on hover/click)
-- Illustrative icons (more detailed than generic)
-- Consistent style across all icons
-
-**Background effects**:
-- Subtle particle effects
-- Gradient mesh backgrounds
-- Geometric patterns
-- Parallax depth
-- Time-of-day themes (morning vs night)
-
-### Satisfying Interactions
-
-**Drag and drop delight**:
-- Lift effect on drag (shadow, scale)
-- Snap animation when dropped
-- Satisfying placement sound
-- Undo toast ("Dropped in wrong place? [Undo]")
-
-**Toggle switches**:
-- Smooth slide with spring physics
-- Color transition
-- Haptic feedback on mobile
-- Optional sound effect
-
-**Progress & achievements**:
-- Streak counters with celebratory milestones
-- Progress bars that "celebrate" at 100%
-- Badge unlocks with animation
-- Playful stats ("You're on fire! 5 days in a row")
-
-**Form interactions**:
-- Input fields that animate on focus
-- Checkboxes with a satisfying scale pulse when checked
-- Success state that celebrates valid input
-- Auto-grow textareas
-
-### Sound Design
-
-**Subtle audio cues** (when appropriate):
-- Notification sounds (distinctive but not annoying)
-- Success sounds (satisfying "ding")
-- Error sounds (empathetic, not harsh)
-- Typing sounds for chat/messaging
-- Ambient background audio (very subtle)
-
-**IMPORTANT**:
-- Respect system sound settings
-- Provide mute option
-- Keep volumes quiet (subtle cues, not alarms)
-- Don't play on every interaction (sound fatigue is real)
-
-### Easter Eggs & Hidden Delights
-
-**Discovery rewards**:
-- Konami code unlocks special theme
-- Hidden keyboard shortcuts (Cmd+K for special features)
-- Hover reveals on logos or illustrations
-- Alt text jokes on images (for screen reader users too!)
-- Console messages for developers ("Like what you see? We're hiring!")
-
-**Seasonal touches**:
-- Holiday themes (subtle, tasteful)
-- Seasonal color shifts
-- Weather-based variations
-- Time-based changes (dark at night, light during day)
-
-**Contextual personality**:
-- Different messages based on time of day
-- Responses to specific user actions
-- Randomized variations (not same every time)
-- Progressive reveals with continued use
-
-### Loading & Waiting States
-
-**Make waiting engaging**:
-- Interesting loading messages that rotate
-- Progress bars with personality
-- Mini-games during long loads
-- Fun facts or tips while waiting
-- Countdown with encouraging messages
-
-```
-Loading messages: write ones specific to your product, not generic AI filler:
-- "Crunching your latest numbers..."
-- "Syncing with your team's changes..."
-- "Preparing your dashboard..."
-- "Checking for updates since yesterday..."
-```
-
-**WARNING**: Avoid cliched loading messages like "Herding pixels", "Teaching robots to dance", "Consulting the magic 8-ball", "Counting backwards from infinity". These are AI-slop copy, instantly recognizable as machine-generated. Write messages that are specific to what your product actually does.
-
-### Celebration Moments
-
-**Success celebrations**:
-- Confetti for major milestones
-- Animated checkmarks for completions
-- Progress bar celebrations at 100%
-- "Achievement unlocked" style notifications
-- Personalized messages ("You published your 10th article!")
-
-**Milestone recognition**:
-- First-time actions get special treatment
-- Streak tracking and celebration
-- Progress toward goals
-- Anniversary celebrations
-
-## Implementation Patterns
-
-**Animation libraries**:
-- Framer Motion (React)
-- GSAP (universal)
-- Lottie (After Effects animations)
-- Canvas confetti (party effects)
-
-**Sound libraries**:
-- Howler.js (audio management)
-- Use-sound (React hook)
-
-**Physics libraries**:
-- React Spring (spring physics)
-- Popmotion (animation primitives)
-
-**IMPORTANT**: File size matters. Compress images, optimize animations, lazy load delight features.
-
-**NEVER**:
-- Delay core functionality for delight
-- Force users through delightful moments (make skippable)
-- Use delight to hide poor UX
-- Overdo it (less is more)
-- Ignore accessibility (animate responsibly, provide alternatives)
-- Make every interaction delightful (special moments should be special)
-- Sacrifice performance for delight
-- Be inappropriate for context (read the room)
-
-## Verify Delight Quality
-
-Test that delight actually delights:
-
-- **User reactions**: Do users smile? Share screenshots?
-- **Doesn't annoy**: Still pleasant after 100th time?
-- **Doesn't block**: Can users opt out or skip?
-- **Performant**: No jank, no slowdown
-- **Appropriate**: Matches brand and context
-- **Accessible**: Works with reduced motion, screen readers
-
-When the moments feel earned, hand off to `/monodesign polish` for the final pass.

package/.claude/skills/monodesign/reference/design-principles.md

@@ -1,246 +0,0 @@
-# Design Principles — The Editorial Sanctuary
-
-The north star aesthetic. Nine load-bearing rules that override project-specific decisions. When a project brief conflicts with these, the rules win.
-
-## The Nine Rules
-
-### 1. The One Voice Rule
-Editorial Magenta is the only vibrant color. No supporting accent, ever. If a second emphasis point is needed, use scale or weight — never a second hue.
-
-**Enforcement:** When you find yourself reaching for a second accent color, stop. Ask: can scale, weight, or spacing carry the emphasis instead?
-
-### 2. The Paper-Not-White Rule
-Page background is Warm Ash Cream (`oklch(96% 0.005 350)`), never Crisp Paper White (`oklch(98% 0 0)`). The warmth is load-bearing — it creates subconscious cohesion with the accent.
-
-**Enforcement:** `background: white` and `background: #fff` are never acceptable as page-level backgrounds. Always use the Warm Ash Cream token.
-
-### 3. The OKLCH-Only Rule
-All new colors are declared in OKLCH. Hex is reserved only for the fenced Command Category Tints (the six category tag colors).
-
-**Enforcement:** Color picking in hex, hsl, or rgb = disqualified. Write the OKLCH equivalent before shipping.
-
-### 4. The Italic-Is-Voice Rule
-Italic is a voice choice for display type, not emphasis inside body copy. Body emphasis is weight — `font-weight: 600` or `700`. Italic inside running text = wrong register.
-
-**Enforcement:** `<em>` and `font-style: italic` inside paragraph elements = flag. Display headings in italic = intentional editorial voice.
-
-### 5. The 1.6 Leading Rule
-Body `line-height` is exactly `1.6` everywhere. Not `1.5`, not `1.7`. This is the load-bearing readability decision. Headings use tighter leading (`1.1`–`1.25`).
-
-**Enforcement:** Check `line-height` on `body`, `p`, and long-copy elements. `1.6` is non-negotiable.
-
-### 6. The Fluid-Headlines-Only Rule
-Headings use `clamp()` fluid sizing. Body copy uses fixed `rem` values.
-
-```css
-/* Correct */
-h1 { font-size: clamp(2rem, 5vw + 1rem, 4.5rem); }
-h2 { font-size: clamp(1.5rem, 3vw + 0.75rem, 3rem); }
-p  { font-size: 1rem; } /* fixed */
-
-/* Wrong */
-h1 { font-size: 4.5rem; } /* no clamp */
-p  { font-size: clamp(0.875rem, 1vw, 1rem); } /* body shouldn't fluid-scale */
-```
-
-### 7. The Flat-By-Default Rule
-Surfaces are flat at rest. Shadows appear only on hover or deliberate elevation. A surface with a resting shadow has skipped a design decision.
-
-```css
-/* Correct */
-.card {
-  box-shadow: none; /* flat at rest */
-  transition: box-shadow 0.3s var(--ease-out);
-}
-.card:hover { box-shadow: var(--shadow-md); }
-
-/* Wrong */
-.card { box-shadow: 0 4px 20px rgba(0,0,0,0.15); } /* always elevated */
-```
-
-### 8. The Low-Alpha Rule
-Every shadow's strongest blur uses ≤0.15 alpha. Higher alphas read as 2014 Material Design drop shadows.
-
-```css
-/* Correct */
---shadow-md: 0 4px 24px -4px rgba(0,0,0,0.12), 0 1px 3px rgba(0,0,0,0.06);
-
-/* Wrong */
-box-shadow: 0 10px 30px rgba(0,0,0,0.3); /* 0.3 alpha — too heavy */
-```
-
-### 9. The Tinted-Shadow-Only-For-Accent Rule
-Neutral shadows (`rgba(0,0,0,...)`) for structure. Magenta-tinted shadows (`oklch(60% 0.25 350 / ...)`) only for deliberate accent-glow moments — not as defaults on any surface.
-
----
-
-## Do / Don't Reference
-
-**Do:**
-- Treat Warm Ash Cream as the default page background
-- Use Editorial Magenta on ≤10% of any given screen
-- Set all new colors in OKLCH
-- Use italic display type as a voice, not emphasis inside paragraphs
-- Use `clamp()` fluid sizing for headings; fixed rem for body
-- Keep the primary CTA sharp: `border-radius: 0`, uppercase, letter-tracked
-- Use `--ease-out` (`cubic-bezier(0.16, 1, 0.3, 1)`) on all transitions
-- Leave surfaces flat at rest — shadows only on hover or elevation
-- Respect `prefers-reduced-motion` on every animation
-- Cap body line length at 65–75ch via `max-width`
-
-**Don't:**
-- Use pure black (`#000`) or pure white (`#fff`)
-- Use `border-left` or `border-right` > 1px as a colored stripe
-- Use `background-clip: text` with a gradient
-- Default to dark mode without a scene sentence that forces the answer
-- Use glassmorphism decoratively
-- Add a second accent color
-- Use rounded rectangles with generic drop shadows
-- Use bounce or elastic easing
-- Animate layout properties (width, height, padding, margin)
-- Nest cards inside cards
-- Use identical card grids
-- Use the hero-metric layout template (big number, small label, gradient accent)
-- Extend the Command Category Tints vocabulary
-- Hedge in UI copy
-- Introduce a new spacing token outside the 8/16/24/32/48/80/120 scale
-
----
-
-## Reference Color System
-
-All colors in OKLCH. Named palette:
-
-| Name | OKLCH | Role |
-|---|---|---|
-| Editorial Magenta | `oklch(60% 0.25 350)` | Primary CTA, active states, one accent |
-| Editorial Magenta Deep | `oklch(52% 0.25 350)` | Hover/active state |
-| Warm Ash Cream | `oklch(96% 0.005 350)` | Primary page background |
-| Crisp Paper White | `oklch(98% 0 0)` | Inverted text moments, high-contrast surfaces |
-| Deep Graphite | `oklch(10% 0 0)` | Primary text, CTA backgrounds |
-| Soft Charcoal | `oklch(25% 0 0)` | Secondary text — taglines, hook paragraphs |
-| Mid Ash | `oklch(55% 0 0)` | Tertiary — micro-labels, captions, meta |
-| Paper Mist | `oklch(92% 0 0)` | Hairline borders, section dividers |
-| Magenta Whisper | `oklch(60% 0.25 350 / 0.15)` | Diffuse glow on hover, selection highlights |
-| Magenta Veil | `oklch(60% 0.25 350 / 0.25)` | Focus rings, emphasis shells |
-
-### Editorial Magenta Tonal Ramp
-
-```
-oklch(22% 0.12 350)   ← darkest
-oklch(32% 0.18 350)
-oklch(42% 0.22 350)
-oklch(52% 0.25 350)   ← hover
-oklch(60% 0.25 350)   ← base
-oklch(72% 0.18 350)
-oklch(84% 0.10 350)
-oklch(94% 0.04 350)   ← lightest
-```
-
----
-
-## Reference Typography System
-
-| Style | Purpose | Notes |
-|---|---|---|
-| Display | Hero title only | Light italic — author-signature feel |
-| Headline | Section headings | Larger editorial moments |
-| Title | Hero tagline / section leads | Quieter second display voice |
-| Body Lead | Opening paragraph of long copy | Slightly larger, medium weight |
-| Body | Running copy | 1rem, 1.6 line-height, 65–75ch measure |
-| Supporting | Captions, image credits | Smaller, recessed |
-| Label / Micro-Label | UI labels, form labels, tags | Uppercase, tracked |
-| Mono | Code, technical content | Space Grotesk |
-
----
-
-## Reference Component Specifications
-
-### Primary CTA
-```css
-.btn-primary {
-  background-color: var(--color-ink);      /* Deep Graphite on light bg */
-  color: var(--color-paper);
-  font-family: var(--font-body);
-  font-size: var(--font-size-sm);
-  font-weight: 700;
-  letter-spacing: 0.08em;
-  text-transform: uppercase;
-  border-radius: 0;                        /* sharp corners — editorial */
-  padding: var(--space-4) var(--space-8);
-  border: none;
-  cursor: pointer;
-  transition: background-color var(--duration-fast) var(--ease-out);
-}
-
-.btn-primary:hover {
-  background-color: var(--color-accent);  /* Magenta on hover */
-}
-```
-
-### Inline Text Link
-```css
-a {
-  color: inherit;
-  text-decoration: underline;
-  text-decoration-color: var(--color-accent-dim);
-  text-underline-offset: 3px;
-  transition: text-decoration-color var(--duration-fast) var(--ease-out);
-}
-
-a:hover {
-  text-decoration-color: var(--color-accent);
-}
-```
-
-### Site Navigation
-```css
-.nav-link {
-  font-size: var(--font-size-sm);
-  font-weight: 500;
-  letter-spacing: 0.02em;
-  color: var(--color-ash);
-  text-decoration: none;
-  transition: color var(--duration-fast) var(--ease-out);
-}
-
-.nav-link[aria-current="page"],
-.nav-link:hover {
-  color: var(--color-ink);
-}
-```
-
-### Feature Card
-- Flat at rest (`box-shadow: none`)
-- Shadow appears on hover (`var(--shadow-md)`)
-- `border: 1px solid var(--color-mist)` — always present
-- No rounded corners on brand-register cards; `var(--radius-sm)` on product-register
-- Content: title in Headline style, supporting text in Body, CTA in micro-label style
-
-### Email Input
-```html
-<form class="email-form">
-  <label for="email" class="sr-only">Email address</label>
-  <input type="email" id="email" name="email" placeholder="you@example.com" 
-         class="email-input" required>
-  <button type="submit" class="btn-primary">Subscribe</button>
-</form>
-```
-
-```css
-.email-input {
-  border: 1.5px solid var(--color-mist);
-  border-radius: 0;    /* sharp, editorial */
-  padding: var(--space-3) var(--space-4);
-  font-size: var(--font-size-base);
-  background: var(--color-paper);
-  color: var(--color-ink);
-  transition: border-color var(--duration-fast) var(--ease-out);
-}
-
-.email-input:focus {
-  outline: none;
-  border-color: var(--color-accent);
-  box-shadow: 0 0 0 3px var(--color-accent-dim);
-}
-```

package/.claude/skills/monodesign/reference/distill.md

@@ -1,111 +0,0 @@
-Strip a design to its essence. Remove anything that doesn't earn its place: redundant elements, repeated information, decorative noise, cosmetic complexity.
-
-
----
-
-## Assess Current State
-
-Analyze what makes the design feel complex or cluttered:
-
-1. **Identify complexity sources**:
-   - **Too many elements**: Competing buttons, redundant information, visual clutter
-   - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose
-   - **Information overload**: Everything visible at once, no progressive disclosure
-   - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations
-   - **Confusing hierarchy**: Unclear what matters most
-   - **Feature creep**: Too many options, actions, or paths forward
-
-2. **Find the essence**:
-   - What's the primary user goal? (There should be ONE)
-   - What's actually necessary vs nice-to-have?
-   - What can be removed, hidden, or combined?
-   - What's the 20% that delivers 80% of value?
-
-If any of these are unclear from the codebase, Ask the user for clarification before proceeding.
-
-**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
-
-When the cuts feel right, hand off to `/monodesign polish` for the final pass. As Antoine de Saint-Exupéry put it: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."