codexkit 1.0.2 → 1.0.4

package/.codex/skills/context-management/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: context-management
-description: Unified protocol for context health and session lifecycle management using DCP tools, thresholds, handoff, and resume workflows
-version: 2.0.0
+description: Unified protocol for context health and session lifecycle management using Codex-native /compact, repo-visible memory files, thresholds, handoff, and resume workflows
+version: 3.0.0
 tags: [context, workflow, session]
 dependencies: []
 ---
 
 # Context Management
 
-> **Replaces** manual context tracking and ad-hoc session management — unified protocol for context health across a session lifecycle
+> Unified protocol for context health across a session lifecycle using Codex-native primitives.
 
 Use this skill to keep context useful from first turn to final handoff.
 
@@ -17,7 +17,7 @@ Use this skill to keep context useful from first turn to final handoff.
 - Context size is growing and you need to reduce noise without losing critical details
 - You are finishing a work phase and want to compress completed exploration/implementation
 - You are preparing `/handoff` or resuming a prior session
-- You need to recover relevant prior context with `find_sessions`, `read_session`, and memory files
+- You need to recover relevant prior context from repo files or session history
 
 ## When NOT to Use
 
@@ -29,61 +29,69 @@ Use this skill to keep context useful from first turn to final handoff.
 Prefer **phase-level compression** over reactive cleanup.
 
 ```text
-compress > sweep > handoff
+/compact > persist to files > handoff
 ```
 
-- **compress**: Best default when a phase is complete
-- **sweep**: Use `/dcp sweep` to clean stale/noisy content after completion
-- **handoff**: Use when context pressure remains high even after compression
+- **/compact**: Use the Codex-native command when a phase is complete
+- **persist**: Write durable findings to repo files before they leave the context window
+- **handoff**: Use when context pressure remains high even after compaction
 
-## DCP Command Usage
+## Codex-Native Compaction
 
-### `/dcp compress`
+### `/compact`
 
-Use for completed chapters of work (research, implementation wave, review sweep).
+The built-in Codex CLI command that summarizes conversation history server-side.
+
+Use for completed chapters of work (research, implementation wave, review sweep):
+
+```
+/compact focus on the authentication refactor
+```
 
 - Best for large ranges of now-stable outputs
 - Lowest cognitive overhead on later turns
+- Accepts optional focus instructions to guide what it preserves
 - Usually lowest risk of deleting needed details
 
-### `/dcp sweep`
-
-Use after a phase is complete to let DCP remove stale/noisy content automatically.
+### `codex resume`
 
-Good candidates for sweep-driven cleanup:
+Resume a previous Codex session by thread ID:
 
-- wrong-target searches
-- failed dead-end exploration no longer needed
-- duplicate or superseded junk output
+```bash
+codex resume
+```
 
-Do **not** sweep because output is merely "long". Length alone is not noise.
+This restores the session transcript from `~/.codex/sessions/`. Useful for short interruptions where the full session context is still relevant.
 
 ## Session Lifecycle Protocol
 
 ### 1) Start Session
 
 1. Load task spec and essential policy docs only
-2. Check context health (`/dcp context`)
-3. Pull prior work only if needed:
-   - `find_sessions({ query })`
-   - `read_session({ session_id, focus })`
-   - `memory-read({ file })` or `memory-search({ query })`
+2. Pull prior work only if needed:
+   - Read `.codex/context/session-context.md` for the last stop point
+   - Read `.codex/memory/project/state.md` for durable state
+   - Search repo memory: `bash .codex/scripts/memory_search.sh "query"`
+   - Use `codex resume` if continuing from the same thread
 
 ### 2) During Active Work
 
 - Keep active files readable until edits are done
-- At each natural boundary, evaluate compress candidates
-- Compress completed phases before starting the next chapter
+- At each natural boundary, evaluate `/compact` candidates
+- Persist durable findings to repo files before compacting
 
 ### 3) Pre-Handoff / Closeout
 
-1. Compress completed phase ranges
-2. Persist key decisions/learnings to memory (observation or memory-update)
-3. Create concise handoff summary (what changed, what is pending, known risks)
+1. Run `/compact` on completed phase ranges
+2. Persist key decisions/learnings to durable repo files:
+   - `.codex/context/decision-log.md` for architecture decisions
+   - `.codex/context/worklog.md` for milestone trail
+   - `.codex/memory/project/state.md` for durable state
+3. Create concise handoff in `.codex/context/session-context.md`
 
 ### 4) Resume Session
 
-1. Rehydrate only relevant context (don’t replay everything)
+1. Rehydrate only relevant context (don't replay everything)
 2. Validate assumptions against current files/git state
 3. Continue with fresh context budget, not accumulated clutter
 
@@ -94,8 +102,8 @@ Use these thresholds as operational triggers:
 | Threshold | Interpretation | Required Action |
 | --- | --- | --- |
 | <50k | Healthy start | Keep inputs minimal, avoid unnecessary reads |
-| 50k–100k | Moderate growth | Compress completed phases, keep active files intact |
-| >100k | High pressure | Aggressively compress by phase; run `/dcp sweep` on stale noise |
+| 50k-100k | Moderate growth | `/compact` completed phases, keep active files intact |
+| >100k | High pressure | Aggressively compact by phase; persist findings to repo files |
 | >150k | Near capacity | Perform handoff and resume in a fresh session |
 
 Secondary guardrails:
@@ -106,23 +114,25 @@ Secondary guardrails:
 
 ## Phase Boundary Triggers
 
-Compress at these boundaries:
+Compact at these boundaries:
 
-- Research complete → compress exploration + search outputs
-- Implementation wave complete → compress completed read/edit/test cycles
-- Review complete → compress raw reviewer outputs, keep synthesized findings
-- Before `/handoff` → compress everything non-essential since last checkpoint
+- Research complete -> persist findings to `memory/research/`, then `/compact`
+- Implementation wave complete -> `/compact` completed read/edit/test cycles
+- Review complete -> persist synthesized findings, `/compact` raw outputs
+- Before `/handoff` -> compact everything non-essential since last checkpoint
 
-Rule: **Completed phases should not remain uncompressed for long.**
+Rule: **Completed phases should not remain uncompacted for long.**
 
 ## Context Transfer Sources (Cross-Session)
 
 Use in priority order:
 
-1. Memory artifacts (`memory-search`, `memory-read`, observations)
-2. Session history (`find_sessions`, `read_session`)
-3. Task tracker state (`br show <id>` when applicable)
-4. Git evidence (`git diff`, `git log`, test output)
+1. Repo-visible files: `.codex/context/`, `.codex/memory/project/`, `.codex/memory/research/`
+2. Local retrieval: `bash .codex/scripts/memory_search.sh "query"`
+3. Codex session history: `codex resume` for thread-based recall
+4. Task tracker state: `br show <id>` when applicable
+5. Git evidence: `git diff`, `git log`, test output
+6. Optional MCP memory: only when repo docs are insufficient (requires MCP setup)
 
 Carry forward decisions and constraints, not every intermediate log.
 
@@ -130,31 +140,31 @@ Carry forward decisions and constraints, not every intermediate log.
 
 | Anti-Pattern | Why It Hurts | Correct Pattern |
 | --- | --- | --- |
-| Compressing active work areas (losing precision needed for edits) | Removes exact lines needed for safe edits | Keep active file/tool outputs until edit + verification complete |
-| Sweeping content you still need | Forces rework and increases error risk | Keep active files/tool outputs until phase is complete |
-| Not compressing completed exploration phases | Bloats context and degrades later turns | Compress immediately at phase completion |
-| Session handoff without persisting key decisions to memory | Next session loses rationale and constraints | Write observations/memory updates before handoff |
+| Compacting active work areas | Removes exact lines needed for safe edits | Keep active file/tool outputs until edit + verification complete |
+| Not compacting completed phases | Bloats context and degrades later turns | `/compact` immediately at phase completion |
+| Session handoff without persisting to repo files | Next session loses rationale and constraints | Write to decision-log, state, worklog before handoff |
+| Relying only on session memory for durable facts | Facts are lost when session ends | Persist to `.codex/context/` or `.codex/memory/` |
 
 ## Verification
 
-Check context health: are completed phases compressed? Are active files still readable?
+Check context health: are completed phases compacted? Are active files still readable?
 
 Before claiming cleanup done, confirm:
 
 - Active edit targets are still present in readable form
-- Completed phases are compressed or intentionally kept for active work
-- No critical decision exists only in transient tool output
-- Handoff includes next actions and blockers
+- Completed phases are compacted or intentionally kept for active work
+- No critical decision exists only in transient session output
+- Handoff includes next actions and blockers in repo-visible files
 
 ## Quick Playbook
 
 ```text
-1) Start turn: /dcp context
+1) Start: read session-context.md + state.md
 2) Identify completed phase ranges
-3) /dcp compress completed ranges
-4) /dcp sweep stale/noisy outputs after phase completion
-5) persist key decisions to memory
-6) handoff/resume with focused rehydration
+3) Persist durable findings to repo files
+4) /compact completed ranges
+5) At session end: update session-context.md, state.md, worklog.md
+6) Resume: /prompts:resume or codex resume
 ```
 
 ## See Also

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.

package/.codex/skills/frontend-design/references/color-system.md

@@ -0,0 +1,125 @@
+# Color System
+
+> Reference for the `frontend-design` skill. Covers OKLCH-first color pipeline, tinted neutrals, dark mode, and accessibility.
+> Adapted from [pbakaus/impeccable](https://github.com/pbakaus/impeccable) (Apache 2.0).
+
+## Color Spaces: Use OKLCH
+
+**Stop using HSL.** Use OKLCH (or LCH) instead. It's perceptually uniform, meaning equal steps in lightness *look* equal. In HSL, 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.
+
+## Tinted Neutrals
+
+**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);
+--gray-900: oklch(15% 0.01 60);
+
+/* Cool-tinted grays (tech, professional) */
+--gray-100: oklch(95% 0.01 250);
+--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.
+
+## The 60-30-10 Rule
+
+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.
+
+## Contrast & Accessibility
+
+| 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 |
+
+**Gotcha**: Placeholder text still needs 4.5:1. That light gray placeholder you see everywhere usually fails WCAG.
+
+### Dangerous Color Combinations
+
+- Light gray text on white (the #1 accessibility fail)
+- **Gray text on any colored background** — gray looks washed out on color; use a darker shade of the background color or transparency instead
+- 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. Even a chroma of 0.005-0.01 is enough to feel natural without being obviously tinted.
+
+### Testing
+
+- [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/)
+- Browser DevTools: Rendering > Emulate vision deficiencies
+- [Polypane](https://polypane.app/) for real-time testing
+
+## Dark Mode
+
+### Dark Mode Is Not Inverted Light Mode
+
+| 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: primitive tokens (`--blue-500`) and semantic tokens (`--color-primary: var(--blue-500)`). For dark mode, only redefine the semantic layer — primitives stay the same.
+
+## Alpha Is A Design Smell
+
+Heavy use of transparency (rgba, hsla) usually means an incomplete palette. Alpha creates unpredictable contrast, performance overhead, and inconsistency. Define explicit overlay colors for each context instead. Exception: focus rings and interactive states where see-through is needed.
+
+---
+
+**Avoid**: Relying on color alone to convey information. Creating palettes without clear roles for each color. Using pure black (#000) for large areas. Skipping color blindness testing (8% of men affected).