codexkit 1.0.1 → 1.0.3

package/.codex/prompts/ship.md

@@ -39,11 +39,11 @@ Execute PRD tasks, verify each gate passes, run review, then request close appro
 
 ## Available Tools
 
-| Tool  | Use When                                  |
-| ----- | ----------------------------------------- |
-| `br`  | Task metadata, comments, close/sync       |
-| `git` | Branch, commits, diffs, verification prep |
-| `grep`| Stub checks and key-link checks           |
+| Tool   | Use When                                  |
+| ------ | ----------------------------------------- |
+| `br`   | Task metadata, comments, close/sync       |
+| `git`  | Branch, commits, diffs, verification prep |
+| `grep` | Stub checks and key-link checks           |
 
 ## Phase 0: Bootstrap Beads
 
@@ -115,11 +115,11 @@ For each task:
 
 ### Checkpoint Protocol
 
-| Type                      | Action                                                     |
-| ------------------------- | ---------------------------------------------------------- |
-| `checkpoint:human-verify` | Automate checks first, then pause for user verification    |
-| `checkpoint:decision`     | Present options, wait for explicit selection               |
-| `checkpoint:human-action` | Request specific action and provide verification command   |
+| Type                      | Action                                                   |
+| ------------------------- | -------------------------------------------------------- |
+| `checkpoint:human-verify` | Automate checks first, then pause for user verification  |
+| `checkpoint:decision`     | Present options, wait for explicit selection             |
+| `checkpoint:human-action` | Request specific action and provide verification command |
 
 **Checkpoint format:**
 
@@ -148,16 +148,19 @@ For each task:
 ### TDD Execution Flow
 
 **RED**
+
 1. Add failing test
 2. Run test (must fail)
 3. Commit: `test: add failing test for [feature]`
 
 **GREEN**
+
 1. Implement minimal fix
 2. Run test (must pass)
 3. Commit: `feat: implement [feature]`
 
 **REFACTOR** (optional)
+
 1. Clean up without behavior change
 2. Run tests (must remain green)
 3. Commit: `refactor: clean up [feature]`
@@ -177,13 +180,13 @@ git commit -m "feat(bead-$ARGUMENTS): <task description>
 
 Commit types:
 
-| Type       | Use For                                 |
-| ---------- | --------------------------------------- |
-| `feat`     | New user-visible behavior               |
-| `fix`      | Bug fix                                 |
-| `test`     | Test-only changes                       |
-| `refactor` | Internal cleanup, no behavior change    |
-| `chore`    | Tooling/config/dependency updates       |
+| Type       | Use For                              |
+| ---------- | ------------------------------------ |
+| `feat`     | New user-visible behavior            |
+| `fix`      | Bug fix                              |
+| `test`     | Test-only changes                    |
+| `refactor` | Internal cleanup, no behavior change |
+| `chore`    | Tooling/config/dependency updates    |
 
 ### Stop Conditions
 
@@ -218,7 +221,7 @@ Completion checklist before closing:
 - [ ] Durable memory artifacts were updated in the correct home if the work changed state, blockers, or learnings
 - [ ] User approval obtained before bead close
 
-## Phase 6: Review
+## Phase 5: Review
 
 Load and run `$requesting-code-review`. Dispatch **5 parallel review agents**, each covering one lens:
 
@@ -247,7 +250,7 @@ Wait for all 5 to return. Synthesize findings:
 
 If critical issues require architectural decisions, stop and present options.
 
-## Phase 6B: Goal-Backward Verification
+## Phase 5B: Goal-Backward Verification
 
 Three-level verification:
 
@@ -277,9 +280,10 @@ return Response.json({ ok: true })
 
 If Level 2/3 fails, fix and re-verify.
 
-## Phase 7: Close
+## Phase 6: Close
 
 > **Choose one:**
+>
 > 1. **Close bead (Recommended)** — All tasks complete, all gates pass, review clear.
 > 2. **Keep open** — Additional changes required.
 
@@ -297,6 +301,13 @@ If user confirms close:
 .codex/scripts/close_bead.sh $ARGUMENTS --reason "Shipped: PRD tasks complete, verification and review passed"
 ```
 
+After close, commit bead state:
+
+```bash
+git add .beads/
+git commit -m "chore(bead-$ARGUMENTS): close - shipped with all gates passing"
+```
+
 ## Output
 
 Report with six sections:
@@ -326,9 +337,9 @@ Report with six sections:
 
 ## Related Commands
 
-| Need        | Command              |
-| ----------- | -------------------- |
-| Create spec | `/prompts:create`    |
-| Claim task  | `/prompts:start <id>` |
+| Need        | Command                |
+| ----------- | ---------------------- |
+| Create spec | `/prompts:create`      |
+| Claim task  | `/prompts:start <id>`  |
 | Verify only | `/prompts:verify <id>` |
-| Create PR   | `/prompts:pr`        |
+| Create PR   | `/prompts:pr`          |

package/.codex/prompts/start.md

@@ -75,10 +75,10 @@ If missing/incomplete, route to `/prompts:create`.
 ## Phase 3: Claim
 
 ```bash
-.codex/scripts/start_bead.sh $ARGUMENTS
+.codex/scripts/start_bead.sh $ARGUMENTS --use-current-branch
 ```
 
-This helper validates `prd.md`, claims the bead, and prepares the default feature branch.
+This helper validates `prd.md` and claims the bead; workspace setup is handled in Phase 4.
 
 ## Phase 4: Prepare Workspace
 

package/.codex/prompts/ui-slop-check.md

@@ -0,0 +1,119 @@
+---
+description: Automated audit for AI aesthetic fingerprints with actionable fixes
+argument-hint: "<component-or-file-path> [--fix]"
+agent: vision
+---
+
+# UI Slop Check: $ARGUMENTS
+
+Scan frontend code for the 12 AI aesthetic fingerprint anti-patterns. Returns a pass/fail verdict with specific findings and actionable corrections.
+
+> Inspired by [pbakaus/impeccable](https://github.com/pbakaus/impeccable) design language kit.
+
+## Load Skills
+
+- `$frontend-design` — design principles and AI slop taxonomy
+- `$visual-analysis` — visual analysis and comparison
+
+## Options
+
+| Argument | Default | Description |
+| -------- | ------- | ------------------------------------------- |
+| `--fix` | false | Auto-apply corrections for detected issues |
+
+## Phase 1: Scan Target
+
+Parse `$ARGUMENTS` for the target path (component file, directory, or screenshot).
+
+Read all relevant files. For each file, scan against the 12 AI fingerprint anti-patterns from the `frontend-design` skill:
+
+| # | Anti-Pattern | What to Look For |
+|---|-------------|------------------|
+| 1 | **Inter/Roboto font** | `font-family` declarations using Inter, Roboto, Arial, Open Sans, system defaults as primary choice |
+| 2 | **Purple-to-blue gradients** | `linear-gradient` with purple/blue/cyan hues; neon accents on dark backgrounds |
+| 3 | **Cards-on-cards** | Nested card components; `Card` inside `Card`; excessive `.rounded` + `.shadow` nesting |
+| 4 | **Glassmorphism abuse** | `backdrop-filter: blur`, glass-effect classes used decoratively across multiple components |
+| 5 | **Bounce/elastic easing** | `cubic-bezier` with values >1 (overshoot); `bounce`, `elastic`, `spring` in animation names |
+| 6 | **Pure black/white** | `#000`, `#fff`, `rgb(0,0,0)`, `rgb(255,255,255)` without tinting |
+| 7 | **Hero metric template** | Big number + small label + supporting stats + gradient accent layout pattern |
+| 8 | **Identical card grids** | Same-sized cards with icon + heading + text repeated 3+ times identically |
+| 9 | **Gradient text impact** | `background-clip: text` + gradient on headings or metrics |
+| 10 | **Gray text on color** | Gray (`#6b7280`, `gray-500`, etc.) text on non-white/non-gray backgrounds |
+| 11 | **Decorative sparklines** | Chart/sparkline components with no real data binding or meaningful data |
+| 12 | **Dark mode default** | Only dark theme defined; dark mode with glowing accents and no light mode |
+
+## Phase 2: Generate Report
+
+### Verdict
+
+Start with a clear **PASS** or **FAIL** verdict.
+
+A single critical anti-pattern = FAIL. Explain why immediately.
+
+### Findings Table
+
+For each detected anti-pattern:
+
+```markdown
+| # | Anti-Pattern | Status | Location | Severity |
+|---|-------------|--------|----------|----------|
+| 1 | Inter font  | FOUND  | globals.css:3 | Medium |
+| 2 | Purple gradient | CLEAR | - | - |
+...
+```
+
+### Detailed Findings
+
+For each FOUND item:
+
+1. **Location**: File path and line number
+2. **Evidence**: The specific code or pattern detected
+3. **Impact**: Why this makes the UI look AI-generated
+4. **Fix**: Specific replacement code or approach
+
+### Summary
+
+- Total anti-patterns found: X/12
+- Severity breakdown: Critical / Medium / Low
+- Estimated fix effort: Quick (<30min) / Moderate (1-2hr) / Significant (>2hr)
+
+## Phase 3: Auto-Fix (if `--fix`)
+
+If `--fix` is passed, apply corrections for each detected anti-pattern:
+
+1. Replace generic fonts with distinctive alternatives
+2. Replace purple/blue gradients with project-appropriate OKLCH palette
+3. Flatten nested card structures
+4. Remove decorative glassmorphism; keep functional uses
+5. Replace bounce/elastic easing with exponential curves
+6. Tint pure black/white with subtle brand hue
+7. Redesign hero metric layouts
+8. Vary card grid sizes and layouts
+9. Replace gradient text with weight/size/color contrast
+10. Replace gray-on-color with shade-of-background text color
+11. Remove decorative sparklines or bind to real data
+12. Add light mode support if only dark mode exists
+
+After fixing, re-run the scan to confirm improvements.
+
+## Phase 4: Record
+
+If significant findings, append to `.codex/context/worklog.md`:
+
+```markdown
+## [YYYY-MM-DD] UI Slop Check: <target>
+
+- Verdict: PASS/FAIL
+- Anti-patterns found: X/12
+- Fixed: Y (if --fix)
+- Remaining: Z
+```
+
+## Related Commands
+
+| Need | Command |
+| ---- | ------- |
+| Full UI/UX review | `/prompts:ui-review` |
+| Design new UI | `/prompts:design` |
+| Gather inspiration | `/prompts:ui-inspire` |
+| Ship implementation | `/prompts:ship` |

package/.codex/scripts/start_bead.sh

@@ -6,9 +6,10 @@ set -euo pipefail
 PROJECT_ROOT="${CODEXKIT_PROJECT_ROOT:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)}"
 BEAD_ID="${1:-}"
 USE_CURRENT_BRANCH=false
+WORKTREE=false
 
 if [[ -z "$BEAD_ID" ]]; then
-  echo "Usage: $0 <bead-id> [--use-current-branch]" >&2
+  echo "Usage: $0 <bead-id> [--use-current-branch] [--worktree]" >&2
   exit 1
 fi
 shift || true
@@ -18,9 +19,12 @@ while [[ $# -gt 0 ]]; do
     --use-current-branch)
       USE_CURRENT_BRANCH=true
       ;;
+    --worktree)
+      WORKTREE=true
+      ;;
     *)
       echo "Unknown option: $1" >&2
-      echo "Usage: $0 <bead-id> [--use-current-branch]" >&2
+      echo "Usage: $0 <bead-id> [--use-current-branch] [--worktree]" >&2
       exit 1
       ;;
   esac
@@ -95,13 +99,13 @@ print(f"BEAD_SLUG={shlex.quote(slug)}")
 PY
 )"
 
-if [[ "$BEAD_STATUS" != "in_progress" ]]; then
-  (cd "$PROJECT_ROOT" && br update "$BEAD_ID" --status in_progress >/dev/null)
+if [[ "$BEAD_STATUS" == "open" ]]; then
+  (cd "$PROJECT_ROOT" && br update "$BEAD_ID" --claim >/dev/null)
 fi
 
 BRANCH_NAME="$(git -C "$PROJECT_ROOT" branch --show-current)"
 TARGET_BRANCH="$BRANCH_NAME"
-if ! $USE_CURRENT_BRANCH; then
+if ! $USE_CURRENT_BRANCH && ! $WORKTREE; then
   case "$BEAD_TYPE" in
     feature) prefix="feat" ;;
     bug) prefix="fix" ;;

package/.codex/scripts/verify_bead.sh

@@ -7,6 +7,8 @@ PROJECT_ROOT="${CODEXKIT_PROJECT_ROOT:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../.
 BEAD_ID="${1:-}"
 FULL=false
 NO_CACHE=false
+QUICK=false
+FIX=false
 
 if [[ -z "$BEAD_ID" ]]; then
   echo "Usage: $0 <bead-id> [--full] [--no-cache]" >&2
@@ -23,8 +25,10 @@ while [[ $# -gt 0 ]]; do
       NO_CACHE=true
       ;;
     --quick)
+      QUICK=true
       ;;
     --fix)
+      FIX=true
       ;;
     *)
       echo "Unknown option: $1" >&2
@@ -81,13 +85,14 @@ fi
 
 CURRENT_STAMP="$(
   cd "$PROJECT_ROOT" &&
-  printf '%s\n%s\n%s' \
+  printf '%s\n%s\n%s\n%s' \
+    "$BEAD_ID" \
     "$(git rev-parse HEAD)" \
     "$(git diff HEAD -- '*.ts' '*.tsx' '*.js' '*.jsx')" \
     "$(git ls-files --others --exclude-standard -- '*.ts' '*.tsx' '*.js' '*.jsx' | xargs cat 2>/dev/null)" \
     | shasum -a 256 | cut -d' ' -f1
 )"
-LAST_STAMP="$(tail -1 "$VERIFY_LOG" 2>/dev/null | awk '{print $1}' || true)"
+LAST_STAMP="$(grep -F "$CURRENT_STAMP" "$VERIFY_LOG" 2>/dev/null | tail -1 | awk '{print $1}' || true)"
 
 if ! $NO_CACHE && ! $FULL && [[ -n "$LAST_STAMP" && "$CURRENT_STAMP" = "$LAST_STAMP" ]]; then
   echo "cached-pass=$CURRENT_STAMP"
@@ -135,15 +140,22 @@ for raw_line in text.splitlines():
 PY
 }
 
+if $FIX; then
+  run_npm_script_if_present "lint:fix"
+  run_npm_script_if_present "format"
+fi
+
 run_npm_script_if_present typecheck
 run_npm_script_if_present lint
 run_npm_script_if_present test
 run_npm_script_if_present build
 
-while IFS= read -r verify_cmd; do
-  [[ -z "$verify_cmd" ]] && continue
-  (cd "$PROJECT_ROOT" && bash -lc "$verify_cmd" >/dev/null)
-done < <(run_verify_commands)
+if ! $QUICK; then
+  while IFS= read -r verify_cmd; do
+    [[ -z "$verify_cmd" ]] && continue
+    (cd "$PROJECT_ROOT" && bash -lc "$verify_cmd" >/dev/null)
+  done < <(run_verify_commands)
+fi
 
 mkdir -p "$(dirname "$VERIFY_LOG")"
 echo "$CURRENT_STAMP $(date -u +%Y-%m-%dT%H:%M:%SZ) PASS" >> "$VERIFY_LOG"

package/.codex/skills/frontend-design/SKILL.md

@@ -1,13 +1,16 @@
 ---
 name: frontend-design
-description: Create distinctive, production-grade frontend interfaces. Use when building web components, pages, or applications with React-based frameworks. Includes Tailwind CSS v4, shadcn/ui components, Motion animations, and visual design philosophy for avoiding generic AI aesthetics.
-version: 1.0.0
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+version: 1.1.0
 tags: [ui, design]
 dependencies: []
+license: Apache 2.0. Inspired by pbakaus/impeccable design language kit and Anthropic's frontend-design skill.
 ---
 
 # Frontend Design
 
+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.
+
 ## When to Use
 - Building or refactoring React UI (Next.js, Remix, Vite)
 - Creating reusable component systems with Tailwind and shadcn/ui
@@ -17,33 +20,146 @@ dependencies: []
 ## When NOT to Use
 - Backend-only tasks with no user-facing surface
 
-## Design Intent First
-Define before coding:
-1. Audience and usage context
-2. Visual direction (minimal/editorial/playful/industrial/luxury)
-3. Interaction tone (calm/fast/expressive/utilitarian)
-4. Primary success metric (clarity, conversion, task speed)
+---
+
+## Design Direction
+
+Commit to a BOLD aesthetic direction before coding:
+
+1. **Purpose**: What problem does this interface solve? Who uses it?
+2. **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. Use these for inspiration but design one true to the aesthetic direction.
+3. **Constraints**: Technical requirements (framework, performance, accessibility).
+4. **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.
+
+---
+
+## Frontend Aesthetics Guidelines
+
+### Typography
+*Consult [typography reference](references/typography-rules.md) for scales, pairing, and loading strategies.*
+
+Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.
+
+**DO**: Use a modular type scale with fluid sizing (clamp)
+**DO**: Vary font weights and sizes to create clear visual hierarchy
+**DON'T**: Use overused fonts — Inter, Roboto, Arial, Open Sans, system defaults
+**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes
+**DON'T**: Put large icons with rounded corners above every heading — they rarely add value and make sites look templated
+
+### Color & Theme
+*Consult [color reference](references/color-system.md) for OKLCH, palettes, and dark mode.*
+
+Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+
+**DO**: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes
+**DO**: Tint your neutrals toward your brand hue — even a subtle hint creates subconscious cohesion
+**DON'T**: Use gray text on colored backgrounds — it looks washed out; use a shade of the background color instead
+**DON'T**: Use pure black (#000) or pure white (#fff) — always tint; pure black/white never appears in nature
+**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds
+**DON'T**: Use gradient text for "impact" — especially on metrics or headings; it's decorative rather than meaningful
+**DON'T**: Default to dark mode with glowing accents — it looks "cool" without requiring actual design decisions
+
+### Layout & Space
+*Consult [spatial reference](references/spatial-design.md) for grids, rhythm, and container queries.*
+
+Create visual rhythm through varied spacing. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis.
+
+**DO**: Create visual rhythm through varied spacing — tight groupings, generous separations
+**DO**: Use fluid spacing with clamp() that breathes on larger screens
+**DO**: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis
+**DON'T**: Wrap everything in cards — not everything needs a container
+**DON'T**: Nest cards inside cards — visual noise, flatten the hierarchy
+**DON'T**: Use identical card grids — same-sized cards with icon + heading + text, repeated endlessly
+**DON'T**: Use the hero metric layout template — big number, small label, supporting stats, gradient accent
+**DON'T**: Center everything — left-aligned text with asymmetric layouts feels more designed
+**DON'T**: Use the same spacing everywhere — without rhythm, layouts feel monotonous
+
+### Visual Details
+**DO**: Use intentional, purposeful decorative elements that reinforce brand
+**DON'T**: Use glassmorphism everywhere — blur effects, glass cards, glow borders used decoratively rather than purposefully
+**DON'T**: Use rounded elements with thick colored border on one side — a lazy accent that almost never looks intentional
+**DON'T**: Use sparklines as decoration — tiny charts that look sophisticated but convey nothing meaningful
+**DON'T**: Use rounded rectangles with generic drop shadows — safe, forgettable, could be any AI output
+**DON'T**: Use modals unless there's truly no better alternative — modals are lazy
+
+### Motion
+*Consult [motion reference](references/motion-core.md) for timing, easing, and reduced motion.*
+
+Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.
 
-If intent is fuzzy, align first; implementation quality depends on this.
+**DO**: Use motion to convey state changes — entrances, exits, feedback
+**DO**: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration
+**DO**: For height animations, use grid-template-rows transitions instead of animating height directly
+**DON'T**: Animate layout properties (width, height, padding, margin) — use transform and opacity only
+**DON'T**: Use bounce or elastic easing — they feel dated and tacky; real objects decelerate smoothly
+
+### Interaction
+*Consult [interaction reference](references/interaction.md) for forms, focus, and loading patterns.*
+
+Make interactions feel fast. Use optimistic UI — update immediately, sync later.
+
+**DO**: Use progressive disclosure — start simple, reveal sophistication through interaction
+**DO**: Design empty states that teach the interface, not just say "nothing here"
+**DO**: Make every interactive surface feel intentional and responsive
+**DON'T**: Repeat the same information — redundant headers, intros that restate the heading
+**DON'T**: Make every button primary — use ghost buttons, text links, secondary styles; hierarchy matters
+
+### Responsive
+**DO**: Use container queries (@container) for component-level responsiveness
+**DO**: Adapt the interface for different contexts — don't just shrink it
+**DON'T**: Hide critical functionality on mobile — adapt the interface, don't amputate it
+
+### UX Writing
+*Consult [ux-writing reference](references/ux-writing.md) for labels, errors, and empty states.*
+
+**DO**: Make every word earn its place
+**DON'T**: Repeat information users can already see
+
+---
+
+## The AI Slop Taxonomy
+
+**Critical quality check**: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.
+
+A distinctive interface should make someone ask "how was this made?" not "which AI made this?"
+
+### 12 AI Fingerprint Anti-Patterns
+
+| # | Anti-Pattern | Description | Correction |
+|---|-------------|-------------|------------|
+| 1 | **Inter/Roboto font** | Defaulting to Inter, Roboto, Arial, or Open Sans for everything | Use distinctive fonts: Instrument Sans, Plus Jakarta Sans, Outfit, Fraunces, Newsreader |
+| 2 | **Purple-to-blue gradients** | Cyan-on-dark, purple gradients, neon accents on dark backgrounds — the "AI color palette" | Build an OKLCH palette with tinted neutrals and a single committed brand hue |
+| 3 | **Cards-on-cards** | Nesting cards inside cards, wrapping everything in rounded containers | Use spacing, typography, and subtle dividers; flatten the hierarchy |
+| 4 | **Glassmorphism abuse** | Blur effects, glass cards, glow borders used decoratively everywhere | Use transparency and blur only where it serves a purpose (overlay context) |
+| 5 | **Bounce/elastic easing** | Bounce and elastic animations that feel dated and draw attention to themselves | Use exponential easing (ease-out-quart/quint/expo) for natural deceleration |
+| 6 | **Pure black/white** | Using #000 or #fff without any tinting | Always tint — even oklch with 0.005-0.01 chroma creates natural feel |
+| 7 | **Hero metric template** | Big number, small label, supporting stats, gradient accent — the dashboard cliche | Design unique data presentations that serve the specific content |
+| 8 | **Identical card grids** | Same-sized cards with icon + heading + text, repeated endlessly | Vary card sizes, use featured items, break the repetition |
+| 9 | **Gradient text impact** | Using gradient text on metrics or headings for "impact" | Use weight, size, and color contrast for emphasis instead |
+| 10 | **Gray text on color** | Gray text on colored backgrounds — it looks washed out and dead | Use a darker shade of the background color, or transparency |
+| 11 | **Decorative sparklines** | Tiny charts that look sophisticated but convey nothing meaningful | Only use charts when they communicate real data the user needs |
+| 12 | **Dark mode default** | Defaulting to dark mode with glowing accents to avoid making real design decisions | Design in light mode first; dark mode should be a considered adaptation |
 
 ---
 
 ## Component Architecture Patterns
 
-### 1) Primitive → Composite → Screen
+### Primitive > Composite > Screen
 - **Primitives:** Button, Input, Badge, Icon, Stack
 - **Composites:** SearchBar, FilterPanel, ProductCard
 - **Screen sections:** Hero, ResultsGrid, CheckoutSummary
 
 Keep business logic out of primitives; place behavior in composites/hooks.
 
-### 2) Headless behavior + visual shells
+### Headless behavior + visual shells
 - Encapsulate logic in hooks (`useDialogState`, `useComboboxFilter`)
 - Keep visual components presentational
 - Improves portability and testability
 
-### 3) Composition over prop explosion
-Prefer slot/compound APIs over huge prop matrices.
+### Composition over prop explosion
+Prefer slot/compound APIs over huge prop matrices:
 
 ```tsx
 <Card>
@@ -53,7 +169,7 @@ Prefer slot/compound APIs over huge prop matrices.
 </Card>
 ```
 
-### 4) State locality
+### State locality
 - Keep transient UI state local
 - Lift only shared/derived state
 - Use URL state for shareable filters/tabs/pagination
@@ -64,7 +180,6 @@ Prefer slot/compound APIs over huge prop matrices.
 
 ### Tokenize decisions
 Use theme tokens for color, spacing, typography, radius, shadow.
-Avoid scattered arbitrary values.
 
 ```css
 @theme {
@@ -75,14 +190,13 @@ Avoid scattered arbitrary values.
 ```
 
 ### Deterministic class generation
-- Avoid dynamic class strings purge tools can’t statically detect
+- Avoid dynamic class strings purge tools can't statically detect
 - Use `cva`/`clsx` with explicit variant maps
 
 ### Layout discipline
 - Grid for page-level structure
 - Flex for one-dimensional alignment
 - Consistent spacing scale (`gap-*`, `space-y-*`)
-- Avoid one-off dimensions unless design requires them
 
 ### Dark mode parity
 Every themed component must preserve hierarchy and contrast in dark mode.
@@ -91,19 +205,14 @@ Every themed component must preserve hierarchy and contrast in dark mode.
 
 ## Responsive Design Checklist
 - [ ] Mobile-first base styles
-- [ ] Progressive breakpoints (`sm`→`2xl`)
-- [ ] Touch targets at least 44×44px
+- [ ] Progressive breakpoints (`sm` > `2xl`)
+- [ ] Touch targets at least 44x44px
 - [ ] Navigation works without hover
 - [ ] Dense tables reflow for narrow screens
 - [ ] Long text wraps without clipping
 - [ ] Safe-area support where relevant
 - [ ] Container queries for component-level adaptation
 
-Practical defaults:
-- Collapse multi-column layouts below `md`
-- Convert large tables to cards on small screens
-- Keep primary CTA visible early in scroll
-
 ---
 
 ## Accessibility Requirements
@@ -130,39 +239,11 @@ Practical defaults:
 
 ---
 
-## Animation Guidelines
-
-### Motion hierarchy
-1. Micro-interactions: 120–180ms
-2. State transitions: 180–260ms
-3. Section/page transitions: 220–320ms
-
-### Tool selection
-- Tailwind transitions for simple state feedback
-- Motion for layout, gestures, enter/exit choreography
+## Implementation Principles
 
-```tsx
-<motion.div
-  initial={{ opacity: 0, y: 8 }}
-  animate={{ opacity: 1, y: 0 }}
-  exit={{ opacity: 0, y: -6 }}
-  transition={{ duration: 0.22 }}
-/>
-```
-
-### Performance rules
-- Prefer transform/opacity animations
-- Avoid expensive paint/layout animations on large surfaces
-- Test on low-end devices for jank
-
----
+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.
 
-## Common UI Anti-Patterns
-- Generic gradient-heavy hero with weak hierarchy
-- Inconsistent spacing/radius across components
-- Too many accent colors without semantic mapping
-- Decorative animation that slows core tasks
-- Copied components with drifted behavior/naming
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.
 
 ## Pre-Ship QA Pass
 1. Visual check at mobile/tablet/desktop widths
@@ -171,6 +252,7 @@ Practical defaults:
 4. Reduced-motion behavior pass
 5. Empty/loading/error state pass
 6. Performance smoke for interaction smoothness
+7. **AI Slop check** — run through the 12 anti-patterns above
 
 ## Bottom Line
 Build interfaces with clear intent, strong visual character, accessible interaction, and production-grade responsiveness/performance from the first iteration.