palskills 1.0.8 → 1.0.9

package/README.md

@@ -9,9 +9,10 @@
 | Skill | Role | Key Trait |
 |-------|------|-----------|
 | **Astralym** | Orchestrator | Runs the full pipeline, tracks progress in `state.md` |
+| **Elphidran** | Design Architect | Generates `.palbox/design.md` — colors, typography, spacing |
 | **Lyleen** | Knowledge Graph | Bootstraps `.palbox/` or traverses `[[wikilinks]]` for context |
 | **Jetdragon** | Planner | Asks clarifying questions, generates detailed plans |
-| **Anubis** | Developer | SOLID + SRP enforced, English only |
+| **Anubis** | Developer | SOLID + SRP enforced, English only, reads design tokens |
 | **Panthalus** | Archivist | Records every session with bi-directional `[[wikilinks]]` |
 
 ## Prerequisites
@@ -75,8 +76,9 @@ Astralym runs all 5 steps: learns the codebase → plans with your input → exe
 | Prompt | What happens |
 |--------|-------------|
 | `Lyleen: learn the auth module` | Reads or bootstraps `.palbox/`, returns relevant context |
+| `Elphidran: design the app` | Asks about vibe/industry → generates `.palbox/design.md` |
 | `Jetdragon: plan a forgot-password feature` | Creates `.palbox/plans/` plan, asks clarifying questions. Say **"Gas"** when ready |
-| `Anubis: implement the approved plan` | Executes the plan with SOLID + SRP, all code in English |
+| `Anubis: implement the approved plan` | Executes the plan with SOLID + SRP + design tokens, all code in English |
 | `Panthalus: record this session` | Saves to `.palbox/history/` with bi-directional `[[wikilinks]]` |
 
 ### Flow
@@ -94,6 +96,7 @@ The `.palbox/` knowledge graph grows with every session:
 ├── state.md            # Pipeline progress tracker
 ├── README.md           # Project identity & tech stack
 ├── architecture.md     # Folder map & design patterns
+├── design.md           # Design system (colors, typography, spacing)
 ├── methods.md          # Conventions & standards
 ├── flows/              # Feature workflow docs
 ├── plans/              # Active plans

package/bin/palskills.js

@@ -43,7 +43,6 @@ async function main() {
 
   if (choice === '1') {
     bootstrapPalbox();
-    installSkills();
     console.log(`\n  ${GREEN}✅ Done!${NC} .palbox/ created. Run again to generate agent configs.\n`);
     process.exit(0);
   }
@@ -59,9 +58,6 @@ async function main() {
     generate(agent);
   }
 
-  // Also install Hermes skills
-  installSkills();
-
   console.log(`\n  ${GREEN}✅ Done!${NC} Restart your Agent Tools to load skills.\n`);
 }
 
@@ -239,7 +235,7 @@ ${gitContributors ? `\n**Top Contributors:**\n\`\`\`\n${gitContributors}\n\`\`\`
 
 function generate(agent) {
   const cwd = process.cwd();
-  const skillNames = ['lyleen', 'jetdragon', 'anubis', 'panthalus', 'astralym'];
+  const skillNames = ['elphidran', 'lyleen', 'jetdragon', 'anubis', 'panthalus', 'astralym'];
 
   let dir;
   if (agent === 'codex') dir = path.join(cwd, '.codex', 'skills');
@@ -249,14 +245,55 @@ function generate(agent) {
   fs.mkdirSync(dir, { recursive: true });
 
   for (const name of skillNames) {
-    const file = path.join(dir, `${name}.md`);
+    const skillDir = path.join(dir, name);
+    fs.mkdirSync(skillDir, { recursive: true });
+    const file = path.join(skillDir, 'SKILL.md');
     fs.writeFileSync(file, skillContent(agent, name));
-    console.log(`  ${GREEN}✓${NC} ${dir}/${name}.md`);
+    console.log(`  ${GREEN}✓${NC} ${dir}/${name}/SKILL.md`);
   }
 }
 
 function skillContent(agent, skill) {
   const skills = {
+    elphidran: `# Elphidran — Design System Recommender
+**Agent:** ${agent === 'codex' ? 'Codex' : agent === 'cursor' ? 'Cursor' : 'Claude Code'}
+
+## Role
+Analyze the project and generate a complete design system specification.
+
+## Process
+1. Read .palbox/README.md for project identity
+2. Check package.json for UI libraries (tailwind, mui, shadcn, etc.)
+3. ASK the user (use clarifying questions):
+   - "What's the app's personality? (professional, playful, minimal, dark)"
+   - "What industry? (healthcare, finance, education, gaming, e-commerce)"
+   - "Any brand color already?"
+   - "Need dark mode?"
+4. Generate .palbox/design.md with:
+   - Color palette (light + dark if enabled): primary, surface, text, status colors
+   - Typography tokens: font family, sizes, weights, line heights
+   - Spacing scale: 0 to 64px in consistent steps
+   - Border radius: sm(4), md(8), lg(12), full(9999)
+   - Shadows: sm, md, lg, xl
+   - Component patterns: buttons (primary/secondary/ghost/danger), inputs, cards
+   - Layout: max-width, breakpoints, sidebar width
+   - Implementation notes for Anubis — never hardcode values, use tokens
+
+## Design Recommendations by Industry
+- Healthcare → teal, Inter, trustworthy
+- Finance → deep blue, IBM Plex Sans, professional
+- Education → violet, Inter, engaging
+- Gaming → red, Poppins, bold
+- E-commerce → blue, Inter, action-oriented
+- Dev Tools → slate, JetBrains Mono, dark-first
+- Enterprise → dark teal, Inter, corporate
+
+## Rules
+- Always ask questions before generating
+- Use design tokens — never raw values
+- Include implementation notes for Anubis
+- One design.md per project
+`,
     lyleen: `# Lyleen — Palbox Knowledge Graph
 **Agent:** ${agent === 'codex' ? 'Codex' : agent === 'cursor' ? 'Cursor' : 'Claude Code'}
 
@@ -301,6 +338,23 @@ Create detailed implementation plans. Ask questions until clear.
 ## Role
 Execute approved plans. SOLID + SRP enforced. English only.
 
+## PONYTAIL — Token Efficiency (MUST follow)
+Before every action, climb the ladder. Stop at first rung that holds:
+1. Needs building at all? Skip. (YAGNI)
+2. Already in codebase? Reuse.
+3. Stdlib does it? Use it.
+4. Native platform? Use it.
+5. Already-installed dep? Use it.
+6. One line? Do it.
+7. Only then: write minimum code.
+
+Ponytail rules:
+- Fewest files possible, shortest working diff.
+- No unrequested abstractions, no avoidable dependencies, no speculative scaffolding.
+- Prefer deletion over addition. Boring > clever.
+- Complex request? Ship lazy version + ask: "X covers it. Need full?"
+- NEVER cut: validation, error handling, security, accessibility, data-loss protection.
+
 ## SOLID (Strict)
 - **S**: One class, one reason to change
 - **O**: Extend, never modify existing
@@ -319,7 +373,7 @@ Execute approved plans. SOLID + SRP enforced. English only.
 - One commit per logical change (conventional commits)
 - Read existing files before modifying
 - Write tests if project has testing patterns
-`,
+- Non-trivial logic leaves one runnable check behind`,
     panthalus: `# Panthalus — Archivist
 **Agent:** ${agent === 'codex' ? 'Codex' : agent === 'cursor' ? 'Cursor' : 'Claude Code'}
 
@@ -347,10 +401,11 @@ Run the full development pipeline. Track every step in .palbox/state.md.
 
 ## Pipeline
 1. **CHECK_GRAPH** → Lyleen: bootstrap or retrieve context
-2. **PLANNING** → Jetdragon: create plan, ask questions, wait for "Gas"
-3. **DEVELOPING** → Anubis: execute with SOLID + SRP
-4. **RECORDING** → Panthalus: record with backlinks
-5. **DONE** → Summary with graph stats
+2. **DESIGN** → Elphidran: generate .palbox/design.md (skip if exists)
+3. **PLANNING** → Jetdragon: create plan, ask questions, wait for "Gas"
+4. **DEVELOPING** → Anubis: execute with SOLID + SRP + design tokens
+5. **RECORDING** → Panthalus: record with backlinks
+6. **DONE** → Summary with graph stats
 
 ## CRITICAL: state.md
 
@@ -366,6 +421,7 @@ Create this file IMMEDIATELY when Astralym is activated:
 **Last Updated:** [current datetime]
 
 ## Progress
+- [ ] DESIGN — Elphidran: generate design system
 - [ ] CHECK_GRAPH — Lyleen: bootstrap or retrieve context
 - [ ] PLANNING — Jetdragon: create plan, ask questions
 - [ ] DEVELOPING — Anubis: execute with SOLID + SRP

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "palskills",
-  "version": "1.0.8",
+  "version": "1.0.9",
   "description": "AI-powered development pipeline — 5 Hermes Agent skills orchestrated as a knowledge graph",
   "keywords": [
     "hermes-agent",

package/skills/anubis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: anubis
 description: "Development execution via Codex CLI — receives approved plans, formats them as Codex prompts, and runs codex exec following SOLID + SRP. All output in English."
-version: 2.0.0
+version: 2.1.0
 author: Palskills
 license: MIT
 platforms: [linux, macos, windows]
@@ -15,11 +15,65 @@ metadata:
 
 Anubis is the **execution arm** of the palskills system. It receives an approved plan from **Jetdragon** and delegates the actual coding to **OpenAI Codex CLI**. Anubis acts as the bridge — translating plans into effective Codex prompts, monitoring execution, and verifying results.
 
+## Relationship with the Knowledge Graph
+
+Anubis receives context from **Lyleen** as a **wikilink subgraph** — not a flat list. The plan from Jetdragon contains `[[wikilinks]]` to relevant palbox nodes (flows, architecture, methods, past history). Anubis must:
+- **Resolve wikilinks** in the plan to pull actual content into the Codex prompt
+- **Prioritize linked nodes** — if the plan links to `[[flows/auth]]` and `[[history/2026-07-10-jwt]]`, include their key content
+- **Don't repeat** — if `.codex.md` already has SOLID/SRP rules, focus the prompt on task-specific context
+
+## `.codex.md` Awareness
+
+If the project has a `.codex.md` file (generated by `palskills` CLI), Codex already has the base rules loaded:
+- SOLID principles + SRP enforcement → **skip repeating these in the prompt**
+- Palbox conventions → **skip the "check palbox" instructions**
+- Language rules → **skip**
+
+Only include in the prompt what `.codex.md` does NOT already provide:
+- Task-specific context (the actual feature to build)
+- Linked palbox content (relevant flows, past work, architecture snippets)
+- Deliverables (exact files to touch)
+- Acceptance criteria
+
+**Pitfall:** Repeating rules that are already in `.codex.md` bloats the prompt and dilutes the task-specific instructions. Anubis must check for `.codex.md` before building the prompt.
+
 ## Why Codex?
 
 - Anubis doesn't write code directly — it **directs** Codex to write code
 - Codex runs autonomously in a sandbox, making file changes and commits
-- Anubis ensures Codex follows SOLID + SRP principles via explicit prompt instructions
+- Anubis ensures Codex follows SOLID + SRP principles — either via `.codex.md` (auto-loaded) or explicit prompt instructions (fallback)
+
+## Ponytail: Token-Efficient Development
+
+Anubis embeds the **Ponytail philosophy** (lazy senior dev) into every Codex prompt to minimize token burn. Without it, Codex reads too many files, explores the entire codebase, and over-engineers solutions — burning thousands of tokens per task.
+
+### The Ladder of Laziness
+
+Before writing ANY code, climb this ladder from bottom to top. Stop at the first rung that holds:
+
+1. **Does this need to be built at all?** No? Skip it. (YAGNI)
+2. **Already exist?** Reuse the helper, util, or pattern in the codebase.
+3. **Stdlib?** Use standard library — no dependencies.
+4. **Native platform?** Use built-in browser/OS/DB features.
+5. **Already-installed dep?** Use it — no new packages.
+6. **One line?** Write the one-liner.
+7. **Only then:** write the minimum code that works.
+
+### Ponytail Rules (in every prompt)
+
+- No unrequested abstractions
+- No avoidable dependencies
+- No speculative scaffolding
+- Prefer deletion over addition
+- Boring over clever
+- Fewest files possible
+- Shortest working diff wins
+- Complex request? Ship the lazy version and ASK: "X covers it. Need full version?"
+
+### Guardrails (do NOT skip)
+- Do NOT cut validation, error handling, security, accessibility, or data-loss protection
+- Do NOT skip understanding — read the code, trace the real flow, THEN climb the ladder
+- Non-trivial logic leaves one runnable check behind
 
 ## Core Principles (Enforced via Prompting)
 
@@ -38,21 +92,71 @@ Anubis is the **execution arm** of the palskills system. It receives an approved
 Read the plan from `.palbox/plans/` (handed off by Jetdragon). Verify:
 - Plan status is `APPROVED`
 - All tasks have clear acceptance criteria
+- Plan contains `[[wikilinks]]` to relevant palbox context
+
+### Step 1.5: Check for `.codex.md`
+
+```bash
+cat .codex.md 2>/dev/null && echo "EXISTS" || echo "NOT_FOUND"
+```
+
+If `.codex.md` exists: Codex already has SOLID, SRP, language, and palbox conventions loaded. **Skip those sections** in the prompt — focus only on task-specific context, deliverables, and acceptance criteria.
+
+If `.codex.md` is missing: include the full prompt template with all rules inline.
 
 ### Step 2: Build the Codex Prompt
 
-Transform the plan into a Codex-optimized prompt. The prompt MUST include:
+Resolve wikilinks from the plan into actual content, then build the prompt.
+
+**When `.codex.md` EXISTS (lean prompt — skip rules, focus on task):**
 
 ```markdown
+## Ponytail: Lazy Senior Dev
+Before every action, climb the ladder. Stop at first rung that holds:
+1. Needs building at all? Skip.
+2. Already in codebase? Reuse.
+3. Stdlib does it? Use it.
+4. Native platform covers it? Use it.
+5. Already-installed dep? Use it.
+6. One line? Do it.
+7. Only then: write minimum code.
+Rules: fewest files, shortest diff, no unrequested abstractions, boring > clever.
+Do NOT cut: validation, error handling, security, accessibility, data loss.
+Non-trivial logic = one runnable check behind.
+
 ## Task
-[what to build — from the plan]
+[what to build]
+
+## Knowledge Graph Context
+[Content resolved from plan's [[wikilinks]]]
+- [[flows/auth]] → Auth flow uses JWT with refresh rotation
+- [[history/2026-07-10-jwt]] → Previous session added token blacklisting
 
-## Context
+## Deliverables
+[files to create/modify]
+
+## Verification
+[acceptance criteria]
+```
+
+**When `.codex.md` is MISSING (full prompt with SOLID/SRP inline):**
 - **Project:** [from .palbox/README.md]
 - **Architecture:** [from .palbox/architecture.md]
 - **Conventions:** [from .palbox/methods.md]
 - **Relevant history:** [from .palbox/history/ — linked entries]
 
+## Ponytail: Token Efficiency (Lazy Senior Dev)
+Before writing ANY code, climb the ladder:
+1. Does this need to be built at all? Skip.
+2. Already exist in codebase? Reuse.
+3. Stdlib does it? Use it.
+4. Native platform? Use it.
+5. Already-installed dep? Use it.
+6. One line? Do it.
+7. Only then: minimum code.
+Rules: fewest files, shortest diff, no unrequested abstractions, boring > clever.
+Never cut: validation, error handling, security, accessibility.
+
 ## SOLID Requirements
 1. **Single Responsibility:** Every class/module does exactly ONE thing
 2. **Open/Closed:** Extend via inheritance/composition, never modify existing code
@@ -143,6 +247,23 @@ Return to Astralym with:
 ```
 You are implementing a feature in this project. Follow these rules strictly.
 
+## PONYTAIL — Lazy Senior Dev (TOKEN EFFICIENCY)
+Before every action, stop at the first rung that holds:
+1. Does this need to be built at all? No? Skip it. (YAGNI)
+2. Does it already exist? Reuse the helper, util, or pattern.
+3. Does the standard library do it? Use it.
+4. Does a native platform feature cover it? Use it.
+5. Does an already-installed dependency solve it? Use it.
+6. Can this be one line? Do it.
+7. Only then: write the minimum code that works.
+
+Ponytail Rules:
+- No unrequested abstractions. No avoidable dependencies. No speculative scaffolding.
+- Prefer deletion over addition. Boring over clever.
+- Fewest files possible. Shortest working diff wins.
+- Complex request? Ship the lazy version and ASK: "X covers it. Need full version?"
+- Do NOT cut: validation, error handling, security, accessibility, data-loss protection.
+
 ## PROJECT CONTEXT
 {palbox_context}
 
@@ -184,9 +305,11 @@ When done, commit each logical change separately with descriptive English commit
 ## Rules
 
 1. **Codex runs the code** — Anubis directs, Codex executes
-2. **SOLID + SRP in every prompt** — never assume Codex will follow them otherwise
-3. **Always use `pty=true`** — Codex is interactive, hangs without PTY
-4. **Background for non-trivial tasks** — use `background=true` + `notify_on_complete=true`
-5. **Verify after execution** — don't trust Codex blindly; check git diff
-6. **English only** — prompts, expectations, verification. All in English.
-7. **Respect palbox context** — always include relevant architecture/methods/history in the prompt
+2. **Check `.codex.md` first** — if it exists, skip repeating SOLID/SRP/palbox in the prompt
+3. **Resolve wikilinks** — pull actual content from linked palbox nodes, don't just pass link names
+4. **Lean prompts with `.codex.md`** — task context + deliverables + verification only
+5. **Always use `pty=true`** — Codex is interactive, hangs without PTY
+6. **Background for non-trivial tasks** — use `background=true` + `notify_on_complete=true`
+7. **Verify after execution** — don't trust Codex blindly; check git diff
+8. **English only** — prompts, expectations, verification. All in English.
+9. **Respect the graph** — palbox context comes from Lyleen's wikilink traversal, not flat search

package/skills/astralym/SKILL.md

@@ -81,6 +81,7 @@ Astralym is the central orchestrator of the palskills development system. It rou
 | State | Skill | Action |
 |-------|-------|--------|
 | `CHECK_GRAPH` | Lyleen | Bootstrap if missing; traverse `[[wikilinks]]` → context subgraph |
+| `DESIGN` | Elphidran | Generate `.palbox/design.md` with colors, typography, spacing (skip if exists) |
 | `PLANNING` | Jetdragon | Study subgraph → generate plan with `[[wikilinks]]` → ask questions |
 | `DEVELOPING` | Anubis → Codex | Build Codex prompt from plan → `codex exec` → verify |
 | `RECORDING` | Panthalus | Create history node → add `[[wikilinks]]` → create backlinks → enrich graph |
@@ -99,6 +100,7 @@ ON LOAD: Astralym MUST create or read `.palbox/state.md`. This file tracks pipel
 **Last Updated:** [current datetime]
 
 ## Progress
+- [ ] DESIGN — Elphidran: generate design system
 - [ ] CHECK_GRAPH — Lyleen: bootstrap or retrieve context
 - [ ] PLANNING — Jetdragon: create plan, ask questions
 - [ ] DEVELOPING — Anubis → Codex: execute with SOLID + SRP

package/skills/elphidran/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: elphidran
+description: "Design system recommender — analyzes the project and generates a design.md with base colors, typography, spacing, and UI patterns for Anubis to apply during development."
+version: 1.0.0
+author: Palskills
+license: MIT
+platforms: [linux, macos, windows]
+metadata:
+  hermes:
+    tags: [palskills, design-system, ui, theming, colors, typography]
+    related_skills: [astralym, anubis, panthalus]
+---
+
+# Elphidran — Design System Recommender
+
+Elphidran is the **design architect** of the palskills system. When loaded, it analyzes the project's nature and generates a `design.md` file — a complete design system specification that **Anubis** reads when implementing any UI component. This ensures visual consistency across the entire application.
+
+## When Elphidran Runs
+
+- User says: "Elphidran: generate design system" or "Elphidran: analyze my app"
+- Or as part of Astralym pipeline (optional DESIGN step before DEVELOPMENT)
+
+## How It Works
+
+### Step 1: Analyze the Project
+
+Elphidran examines what the project IS to recommend appropriate design:
+
+```bash
+# Read project identity
+cat .palbox/README.md
+
+# Detect tech stack (React, Vue, Flutter, etc.)
+cat package.json 2>/dev/null | grep -E "react|vue|angular|svelte|next"
+cat pubspec.yaml 2>/dev/null  # Flutter
+
+# Check if any UI library is already in use
+cat package.json 2>/dev/null | grep -E "tailwind|mui|chakra|shadcn|antd|bootstrap"
+```
+
+### Step 2: Ask Insight Questions
+
+Elphidran asks the user design-oriented questions to tailor the system:
+
+1. **Vibe:** "What's the app's personality? (professional/corporate, playful/creative, minimal/clean, dark/serious)"
+2. **Industry:** "What domain? (healthcare, finance, education, gaming, e-commerce, social media)"
+3. **Primary color:** "Any brand color already? Or should I suggest one?"
+4. **Dark mode:** "Need dark mode support? (yes / light-only / dark-first)"
+5. **Audience:** "Who uses this? (internal team, public consumers, enterprise clients)"
+
+### Step 3: Generate design.md
+
+Based on analysis + user answers, create `.palbox/design.md`:
+
+```markdown
+# Design System
+**Generated:** YYYY-MM-DD
+**Architect:** Elphidran (Palskills)
+**Vibe:** [chosen vibe]
+**Dark Mode:** [yes/no]
+
+## Color Palette
+
+### Light Theme
+| Token | Hex | Usage |
+|-------|-----|-------|
+| `primary` | #2563EB | Primary buttons, links, active states |
+| `primary-hover` | #1D4ED8 | Button hover, link hover |
+| `primary-light` | #DBEAFE | Selected backgrounds, badges |
+| `secondary` | #7C3AED | Secondary actions, accents |
+| `surface` | #FFFFFF | Card backgrounds, modals |
+| `background` | #F8FAFC | Page background |
+| `text-primary` | #0F172A | Headings, body text |
+| `text-secondary` | #475569 | Captions, metadata |
+| `border` | #E2E8F0 | Dividers, input borders |
+| `success` | #16A34A | Success states, confirmations |
+| `warning` | #F59E0B | Warnings, pending states |
+| `error` | #DC2626 | Errors, destructive actions |
+| `info` | #0EA5E9 | Info alerts, tooltips |
+
+### Dark Theme (if enabled)
+| Token | Hex |
+|-------|-----|
+| `surface` | #1E293B |
+| `background` | #0F172A |
+| `text-primary` | #F1F5F9 |
+| `text-secondary` | #94A3B8 |
+| `border` | #334155 |
+
+## Typography
+
+| Token | Font | Size | Weight | Line Height | Usage |
+|-------|------|------|--------|-------------|-------|
+| `text-xs` | Inter | 12px | 400 | 16px | Captions, badges |
+| `text-sm` | Inter | 14px | 400 | 20px | Body small, metadata |
+| `text-base` | Inter | 16px | 400 | 24px | Body text |
+| `text-lg` | Inter | 18px | 500 | 28px | Subheadings |
+| `text-xl` | Inter | 20px | 600 | 28px | Card titles |
+| `text-2xl` | Inter | 24px | 700 | 32px | Section headers |
+| `text-3xl` | Inter | 30px | 800 | 36px | Page titles |
+| `text-4xl` | Inter | 36px | 800 | 40px | Hero headings |
+
+**Font Family:** Inter (primary), system-ui (fallback)
+**Monospace:** JetBrains Mono (code blocks)
+
+## Spacing Scale
+
+| Token | Value | Usage |
+|-------|-------|-------|
+| `space-0` | 0px | No spacing |
+| `space-1` | 4px | Icon-text gap, tight |
+| `space-2` | 8px | Inline element gap |
+| `space-3` | 12px | List item gap |
+| `space-4` | 16px | Standard padding, card padding |
+| `space-5` | 20px | Large padding |
+| `space-6` | 24px | Section gap |
+| `space-8` | 32px | Section margin |
+| `space-10` | 40px | Page section gap |
+| `space-12` | 48px | Major section divider |
+| `space-16` | 64px | Hero spacing |
+
+## Border Radius
+
+| Token | Value | Usage |
+|-------|-------|-------|
+| `radius-sm` | 4px | Inputs, small elements |
+| `radius-md` | 8px | Cards, modals, buttons |
+| `radius-lg` | 12px | Large cards, panels |
+| `radius-full` | 9999px | Pills, badges, avatars |
+
+## Shadows
+
+| Token | Value | Usage |
+|-------|-------|-------|
+| `shadow-sm` | 0 1px 2px rgba(0,0,0,0.05) | Subtle cards |
+| `shadow-md` | 0 4px 6px rgba(0,0,0,0.07) | Dropdowns, elevated cards |
+| `shadow-lg` | 0 10px 15px rgba(0,0,0,0.1) | Modals |
+| `shadow-xl` | 0 20px 25px rgba(0,0,0,0.15) | Drawers, slideovers |
+
+## Component Patterns
+
+### Buttons
+- **Primary:** `bg-primary text-white rounded-md px-4 py-2 hover:bg-primary-hover`
+- **Secondary:** `bg-transparent border border-primary text-primary rounded-md px-4 py-2`
+- **Ghost:** `bg-transparent text-primary hover:bg-primary-light rounded-md px-4 py-2`
+- **Danger:** `bg-error text-white rounded-md px-4 py-2`
+- **Sizes:** sm (32px h), md (40px h), lg (48px h)
+
+### Inputs
+- **Default:** `border border-border rounded-sm bg-surface text-text-primary px-3 py-2`
+- **Focus:** `border-primary ring-2 ring-primary-light outline-none`
+- **Error:** `border-error ring-2 ring-red-100`
+- **Disabled:** `bg-gray-50 text-text-secondary cursor-not-allowed`
+
+### Cards
+- `bg-surface rounded-md shadow-sm border border-border p-4`
+- Card header: `text-lg font-semibold mb-2`
+- Card body: `text-sm text-text-secondary`
+
+### Layout
+- Max content width: 1200px
+- Sidebar (if applicable): 256px
+- Responsive breakpoints: sm(640), md(768), lg(1024), xl(1280)
+
+## Implementation Notes for Anubis
+
+When implementing UI with this design system:
+1. **Never hardcode colors.** Use CSS variables or design tokens.
+2. **Use the spacing scale.** No arbitrary px values.
+3. **All text must use typography tokens.** No raw font-size declarations.
+4. **Dark mode (if enabled):** Every component must support both themes via CSS variables.
+5. **Responsive first.** Mobile → tablet → desktop.
+6. **Consistent patterns.** Buttons always look like buttons. Inputs always look like inputs.
+```
+
+### Step 4: Report
+
+```
+## Design System Generated
+
+**File:** .palbox/design.md
+**Palette:** [primary color] based on [vibe/industry]
+**Font:** [font family]
+**Dark mode:** [yes / light-only]
+
+Anubis will now use these tokens when building UI components.
+```
+
+## Design Recommendations by Industry
+
+Elphidran has opinionated defaults per industry:
+
+| Industry | Primary | Vibe | Font |
+|----------|---------|------|------|
+| Healthcare | #0891B2 (teal) | Trustworthy, clean | Inter |
+| Finance | #1E40AF (deep blue) | Professional, serious | IBM Plex Sans |
+| Education | #7C3AED (violet) | Engaging, warm | Inter |
+| Gaming | #DC2626 (red) | Bold, energetic | Poppins |
+| E-commerce | #2563EB (blue) | Action-oriented | Inter |
+| Social Media | #DB2777 (pink) | Vibrant, social | Inter |
+| Developer Tools | #0F172A (slate) | Minimal, dark-first | JetBrains Mono |
+| Enterprise | #0F766E (dark teal) | Corporate, reliable | Inter |
+| Creative Agency | #F59E0B (amber) | Bold, artistic | Playfair Display |
+
+## Rules
+
+1. **Always ask questions** — don't assume colors/vibes
+2. **Generate design.md** — not just verbal recommendations
+3. **Use design tokens** — never raw values in the spec
+4. **Anubis-aware** — every section includes implementation notes
+5. **One design system per project** — update, don't duplicate
+6. **Respect existing** — if the project already has a design system, study and extend it