qualia-framework 3.2.0 → 3.3.0

package/skills/qualia-plan/SKILL.md

@@ -1,101 +1,206 @@
 ---
 name: qualia-plan
-description: "Plan the current phase — spawns planner agent in fresh context. Use when ready to plan a phase."
+description: "Plan the current phase — spawns planner, validates with plan-checker in a revision loop (max 3), optionally runs discuss/research first. Use when ready to plan a phase."
 ---
 
 # /qualia-plan — Plan a Phase
 
-Spawn a planner agent to break the current phase into executable tasks.
+Spawn a planner agent to break the current phase into executable tasks, then validate the plan with a checker (up to 3 revision cycles) before routing to build.
 
 ## Usage
+
 `/qualia-plan` — plan the next unplanned phase
-`/qualia-plan {N}` — plan specific phase
+`/qualia-plan {N}` — plan specific phase N
 `/qualia-plan {N} --gaps` — plan fixes for verification failures
+`/qualia-plan {N} --skip-check` — skip the plan-checker validation loop (not recommended)
 
 ## Process
 
-### 1. Determine Phase & Load Knowledge
+### 1. Determine Phase & Load Context
 
 ```bash
 cat .planning/STATE.md 2>/dev/null
+cat .planning/ROADMAP.md 2>/dev/null
+cat .planning/PROJECT.md 2>/dev/null
 cat ~/.claude/knowledge/learned-patterns.md 2>/dev/null
 cat ~/.claude/knowledge/client-prefs.md 2>/dev/null
 ```
 
 If no phase number given, use the current phase from STATE.md.
-If any learned patterns apply to this phase's work, pass them to the planner in the spawn prompt under a `## Relevant Learnings` section.
-If this is a client project and `client-prefs.md` has an entry for the client, include those preferences in the planner context.
 
-### 2. Spawn Planner (Fresh Context)
+**Read phase-specific context if it exists:**
+```bash
+cat .planning/phase-{N}-context.md 2>/dev/null   # from /qualia-discuss
+cat .planning/phase-{N}-research.md 2>/dev/null  # from /qualia-research
+```
+
+### 2. Optional: Suggest Deeper Prep
+
+**If ROADMAP.md marked this phase as a "research flag" AND no phase-{N}-research.md exists:**
+
+- header: "Research first?"
+- question: "This phase was flagged for deeper research. Run /qualia-research {N} first?"
+- options:
+  - "Yes, research first" — Run /qualia-research {N} inline, then continue
+  - "Skip, plan directly" — I know enough
+
+**If phase involves compliance/regulatory/architectural stakes AND no phase-{N}-context.md exists:**
+
+Briefly suggest: *"Want to run /qualia-discuss {N} first to lock decisions? Optional."*
+
+Don't force it. Some phases don't need it.
+
+### 3. Spawn Planner (Fresh Context)
 
 ```bash
-node ~/.claude/bin/qualia-ui.js banner plan {N} "{phase name from STATE.md}"
+node ~/.claude/bin/qualia-ui.js banner plan {N} "{phase name from ROADMAP.md}"
 node ~/.claude/bin/qualia-ui.js spawn planner "Breaking phase into tasks..."
 ```
 
-Spawn a subagent with `agents/planner.md` instructions:
+Spawn the planner:
 
 ```
 Agent(prompt="
-Read your role: @agents/planner.md
+Read your role: @~/.claude/agents/qualia-planner.md
 
-Project context:
+<project_context>
 @.planning/PROJECT.md
+</project_context>
 
-Current state:
+<current_state>
 @.planning/STATE.md
+</current_state>
+
+<phase_details>
+Phase {N} from ROADMAP.md:
+@.planning/ROADMAP.md
 
-Phase {N} goal: {goal from STATE.md roadmap}
-Phase {N} success criteria: {criteria from STATE.md}
+Goal: {goal from ROADMAP.md}
+Requirements: {REQ-IDs from ROADMAP.md}
+Success criteria: {success criteria from ROADMAP.md}
+</phase_details>
 
-{If --gaps: Also read @.planning/phase-{N}-verification.md for failures to fix}
+<locked_decisions>
+{if phase-{N}-context.md exists, inline its Locked Decisions section; else 'none'}
+</locked_decisions>
 
-Create the plan file at .planning/phase-{N}-plan.md
+<research_findings>
+{if phase-{N}-research.md exists, inline its recommendation; else 'none'}
+</research_findings>
+
+{If --gaps: Also read @.planning/phase-{N}-verification.md for failures to fix. Create gap-closure plan.}
+
+<relevant_learnings>
+{inline any applicable patterns from knowledge/learned-patterns.md}
+</relevant_learnings>
+
+Create the plan at .planning/phase-{N}-plan.md (or .planning/phase-{N}-gaps-plan.md for --gaps).
 ", subagent_type="qualia-planner", description="Plan phase {N}")
 ```
 
-### 3. Review Plan
+### 4. Validate the Plan (unless --skip-check)
+
+Read the generated plan. Spawn the plan-checker:
+
+```
+Agent(prompt="
+Read your role: @~/.claude/agents/qualia-plan-checker.md
+
+<plan_path>.planning/phase-{N}-plan.md</plan_path>
+<phase_goal>{goal from ROADMAP.md}</phase_goal>
+<success_criteria>{criteria from ROADMAP.md}</success_criteria>
+<project_context>@.planning/PROJECT.md</project_context>
+
+Validate against the 7 rules. Return PASS or REVISE with structured issues.
+", subagent_type="qualia-plan-checker", description="Check plan phase {N}")
+```
 
-Read the generated plan. Present the summary using the UI helpers:
+**Revision loop (max 3 iterations):**
+
+- Iteration 1: Check → if REVISE, re-spawn planner with checker issues
+- Iteration 2: Re-check → if REVISE, re-spawn planner with new issues
+- Iteration 3: Final check → if REVISE or BLOCKED, escalate to user
+
+For each revision:
+
+```
+Agent(prompt="
+Read your role: @~/.claude/agents/qualia-planner.md
+
+<revision_mode>true</revision_mode>
+<current_plan>@.planning/phase-{N}-plan.md</current_plan>
+<checker_feedback>
+{inline REVISE output from plan-checker}
+</checker_feedback>
+
+Revise the plan in place. Address every issue. Do NOT add new tasks or change scope
+— only fix what the checker flagged.
+", subagent_type="qualia-planner", description="Revise plan phase {N}")
+```
+
+After revision, spawn the checker again. Max 3 total revision cycles.
+
+**If checker returns BLOCKED after 3 cycles:**
+
+```bash
+node ~/.claude/bin/qualia-ui.js fail "Plan failed validation after 3 revisions"
+```
+
+Show the remaining issues. Ask:
+- "Skip validation and proceed anyway" (use `--skip-check`)
+- "Adjust the roadmap" (phase scope may be wrong)
+- "Adjust the phase goal" (success criteria may be under-specified)
+
+### 5. Present Final Plan
 
 ```bash
 node ~/.claude/bin/qualia-ui.js divider
 node ~/.claude/bin/qualia-ui.js ok "Plan ready: {count} tasks across {count} waves"
 ```
 
-Then, for each wave, print:
-
+For each wave:
 ```bash
-node ~/.claude/bin/qualia-ui.js wave {wave_num} {wave_total} {task_count_in_wave}
+node ~/.claude/bin/qualia-ui.js wave {wave_num} {wave_total} {task_count}
 node ~/.claude/bin/qualia-ui.js task 1 "{task title}"
 node ~/.claude/bin/qualia-ui.js task 2 "{task title}"
 ```
 
-End with an approval prompt (plain text, no UI helper): *"Approve? (yes / adjust)"*
+End with plain text: *"Approve? (yes / adjust)"*
 
-If "adjust" — get feedback, re-spawn planner with revision context.
+If "adjust" — get feedback, re-spawn planner with revision context, re-validate.
 
-### 4. Update State
+### 6. Update State
 
 ```bash
 node ~/.claude/bin/state.js transition --to planned --phase {N}
 ```
-If state.js returns an error, show it to the employee and stop.
-Do NOT manually edit STATE.md or tracking.json — state.js handles both.
+
+If state.js returns an error, show it and stop. Do NOT manually edit STATE.md or tracking.json.
+
+### 7. Route
 
 ```bash
 node ~/.claude/bin/qualia-ui.js end "PHASE {N} PLANNED" "/qualia-build {N}"
 ```
 
-### Gap Closure Mode (`--gaps`)
+## Gap Closure Mode (`--gaps`)
 
 When invoked as `/qualia-plan {N} --gaps`, the planner is in gap-closure mode:
 
 1. Read `.planning/phase-{N}-verification.md` — extract ONLY the FAIL items
 2. For each FAIL item, create a targeted fix task:
-   - **Files:** The specific files that failed verification
-   - **Action:** The specific fix needed (not "fix auth" — "add session persistence check in `src/lib/auth.ts` signIn function")
-   - **Done when:** The exact verification criterion that previously failed, restated
+   - **Files:** specific files that failed verification
+   - **Action:** specific fix (not "fix auth" — "add session persistence check in src/lib/auth.ts signIn function")
+   - **Done when:** the exact verification criterion that previously failed, restated
 3. Do NOT re-plan passing items. Do NOT add new features. Gap plans are surgical.
 4. Write to `.planning/phase-{N}-gaps-plan.md` (separate from original plan)
 5. All gap tasks are Wave 1 (parallel) unless they share files
+6. Plan-checker still validates the gap plan — same 7 rules apply
+
+## Rules
+
+1. **Plan-checker is mandatory by default.** Only skip with `--skip-check`, and only if you know what you're doing.
+2. **Max 3 revision cycles.** After 3 failed checks, escalate — the phase scope is probably wrong.
+3. **Honor locked decisions.** If phase-{N}-context.md exists, its locked decisions are non-negotiable.
+4. **One plan file per phase.** Don't create phase-1-plan.md AND phase-1-plan-v2.md. Edit in place.
+5. **Revision is surgical.** When revising, only fix what the checker flagged — no scope creep.

package/skills/qualia-polish/SKILL.md

@@ -1,11 +1,24 @@
 ---
 name: qualia-polish
-description: "Design and UX pass — critique, polish, harden. Run after all phases are verified."
+description: "Design and UX pass — anti-AI-slop, genuine craft, responsive, accessible. Run after all phases are verified."
 ---
 
 # /qualia-polish — Design Pass
 
-Run after all feature phases are verified. Makes it look production-ready.
+Makes it look like a human designer built it. Kills AI slop. Run after all feature phases are verified.
+
+## The Standard
+
+Every site Qualia ships must feel **designed, not generated.** AI-generated sites have tells:
+- Identical card grids with rounded corners and soft shadows
+- Blue-purple gradients on everything
+- Inter/system-ui font with no hierarchy
+- Generic hero with centered text and a stock gradient background
+- Fixed-width containers leaving dead space on wide screens
+- No motion, no personality, no opinion
+- Perfect symmetry everywhere (real design has tension)
+
+**Kill all of these.** A Qualia site should make someone ask "who designed this?" — not "which template is this?"
 
 ## Process
 
@@ -19,139 +32,176 @@ node ~/.claude/bin/qualia-ui.js banner polish
 cat .planning/DESIGN.md 2>/dev/null || echo "NO_DESIGN"
 ```
 
-If DESIGN.md exists → use it as the standard. If not → use Qualia defaults from `rules/frontend.md`.
+If DESIGN.md exists → it's the standard. Read ALL 12 sections. Key sections for polish:
+- §1 Visual Theme — the feel and signature details
+- §2 Color Palette — exact hex values, CSS variables, contrast ratios
+- §3 Typography — hierarchy table with exact sizes/weights/spacing
+- §4 Components — exact button/card/input/badge specs
+- §5 Layout — spacing scale, grid strategy
+- §6 Depth & Elevation — shadow levels with exact rgba values
+- §7 Do's/Don'ts — brand-specific guardrails
+- §9 Agent Prompt Guide — quick reference for common patterns
+- §10 Accessibility — WCAG checklist
+- §11 Hardening — stress-test criteria
+- §12 Anti-Slop Detection — grep patterns for automated checks
+
+If no DESIGN.md → use `rules/frontend.md` defaults.
 
 Read EVERY frontend file before modifying. No blind edits.
 
-### 1. Critique (Structured Audit)
-
-Review the entire UI against this checklist. Check each item, note violations with file:line.
-
-**Typography:**
-- [ ] No generic fonts (Inter, Roboto, Arial, system-ui, Space Grotesk)
-- [ ] Proper type scale with clear hierarchy (display → heading → body → caption)
-- [ ] Body text: 16px+, line-height 1.5–1.7
-- [ ] Headings: tighter line-height (1.1–1.3), negative letter-spacing for large sizes
-- [ ] Prose max-width: 65ch
-- [ ] Font weights used for hierarchy (Regular, Medium, Semibold, Bold)
-
-**Color & Contrast:**
-- [ ] Cohesive palette via CSS variables (not scattered hex values)
-- [ ] All text passes WCAG AA contrast (4.5:1 normal, 3:1 large)
-- [ ] CTA buttons use accent color — stand out from the page
-- [ ] No blue-purple gradients, no rainbow palettes
-- [ ] Dark mode: rethought surfaces (not just inverted)
-- [ ] Semantic colors used consistently (success=green, error=red, warning=amber)
-
-**Layout & Spacing:**
-- [ ] Full-width fluid layouts — no hardcoded max-width caps
-- [ ] 8px spacing grid followed consistently
-- [ ] Tight spacing within groups, generous between sections
-- [ ] Fluid padding: `clamp(1rem, 5vw, 4rem)` horizontal
-- [ ] No identical card grids — varied visual hierarchy
-- [ ] No generic heroes — purposeful, distinctive
-
-**Interactive States:**
-- [ ] Every button/link: hover (color shift, 150ms), focus (visible ring), active (press feedback), disabled
-- [ ] Loading: skeleton or spinner on all async operations
-- [ ] Empty: helpful message + action on empty lists/data
-- [ ] Error: user-friendly message + recovery action on failed fetches
-- [ ] Form validation: inline errors with `aria-describedby`
-
-**Motion:**
-- [ ] Hover/focus: 150–200ms transitions
-- [ ] Page load: staggered entrance animations (50–80ms delay)
-- [ ] Expand/collapse: 250ms ease-in-out
-- [ ] `prefers-reduced-motion` respected (no animation for users who opt out)
-- [ ] No jank: transforms and opacity only for animated properties
-
-**Accessibility:**
-- [ ] Semantic HTML: `nav`, `main`, `section`, `article`, `header`, `footer`
-- [ ] One `h1` per page, sequential heading hierarchy
-- [ ] All images: descriptive `alt` (or `alt=""` + `aria-hidden` if decorative)
-- [ ] All form inputs: visible `<label>` with `htmlFor` — not placeholder-only
-- [ ] All interactive elements: keyboard accessible (Tab/Enter/Escape)
-- [ ] Touch targets: 44px minimum
-- [ ] Skip link: `<a href="#main">` as first focusable element
-- [ ] No `outline: none` without focus replacement
-- [ ] `<html lang="en">` set
-- [ ] Color not sole information carrier — icons/text as supplements
-
-**Responsive:**
-- [ ] Mobile-first approach (base styles for mobile, min-width breakpoints for larger)
-- [ ] No horizontal scroll at 320px
-- [ ] Navigation: hamburger on mobile, expanded on desktop
-- [ ] Touch targets adequate on mobile (44px min)
-- [ ] Fluid typography with `clamp()`
-- [ ] Images: `max-width: 100%`, responsive srcset where needed
-- [ ] Tables: card view or horizontal scroll on mobile
-
-**Performance:**
-- [ ] Server Components by default — `'use client'` only when needed
-- [ ] Images via `next/image` with width/height
-- [ ] No barrel file imports — direct imports from source
-- [ ] Heavy components lazy-loaded with `next/dynamic`
-- [ ] Data fetched in parallel, not sequentially
-
-### 2. Fix Everything
-
-Work through violations from the critique. Fix each category:
-
-1. Typography first (sets the visual foundation)
-2. Color & contrast (palette coherence)
-3. Layout & spacing (structural fixes)
-4. Interactive states (loading, empty, error, hover, focus)
-5. Motion (transitions, entrance animations, reduced-motion)
-6. Accessibility (semantic HTML, ARIA, keyboard, labels)
-7. Responsive (mobile breakpoints, fluid sizing)
-8. Performance (quick wins — image optimization, dynamic imports)
-
-### 3. Harden
-
-After polish, stress-test edge cases:
-- Long text content (overflow, truncation, word-break)
-- Extremely long usernames or email addresses
-- Empty data everywhere simultaneously
-- Error state on every fetch simultaneously
-- 320px viewport width
-- Keyboard-only navigation through entire flow
-- Screen reader landmarks check (semantic HTML)
-- Right-to-left text (if i18n is planned)
-- Slow network (loading states visible, no flash of empty content)
-
-### 4. Verify
+### 1. AI Slop Detector
+
+Run these checks first. Any hits = mandatory fixes.
 
 ```bash
-npx tsc --noEmit 2>&1 | head -20
+# Generic fonts (the #1 AI tell)
+grep -rn "Inter\|Roboto\|Arial\|Helvetica\|system-ui\|Space.Grotesk" --include="*.tsx" --include="*.css" --include="*.scss" --include="tailwind*" app/ components/ src/ 2>/dev/null | grep -v node_modules
+
+# Hardcoded max-width containers (screams template)
+grep -rn "max-w-7xl\|max-w-\[1200\|max-w-\[1280\|max-width.*1200\|max-width.*1280" --include="*.tsx" --include="*.css" app/ components/ src/ 2>/dev/null
+
+# Blue-purple gradients
+grep -rn "from-blue.*to-purple\|from-purple.*to-blue\|linear-gradient.*blue.*purple\|linear-gradient.*purple.*blue\|from-indigo.*to-violet" --include="*.tsx" --include="*.css" app/ components/ src/ 2>/dev/null
+
+# Card grid monotony (same card component repeated in a grid)
+grep -rn "grid-cols-3\|grid-cols-4" --include="*.tsx" app/ components/ src/ 2>/dev/null | head -5
+
+# Generic hero patterns
+grep -rn "text-center.*mx-auto\|Hero\|hero" --include="*.tsx" app/ components/ src/ 2>/dev/null | head -5
+
+# Scattered hardcoded colors (no design system)
+grep -rn "text-\[#\|bg-\[#\|border-\[#\|color:.*#\|background:.*#" --include="*.tsx" app/ components/ src/ 2>/dev/null | wc -l
 ```
 
-Fix any TypeScript errors before committing.
+**Every hit gets fixed.** Not flagged — fixed.
+
+### 2. Typography Pass
+
+**Goal:** A reader should feel the type was chosen, not defaulted.
+
+- Pick a distinctive display font. Not Inter, not Roboto, not system. Something with character: Clash Display, Cabinet Grotesk, General Sans, Satoshi, Plus Jakarta Sans, Outfit, Sora, Manrope. Pair with a clean body font.
+- Establish clear hierarchy: display (hero text) → h1 → h2 → h3 → body → caption
+- Body: 16px minimum, line-height 1.5-1.7
+- Headings: tighter line-height (1.1-1.3), negative letter-spacing (-0.02em) for display sizes
+- Weight hierarchy: Regular (400) for body, Medium (500) for labels, Semibold (600) for headings, Bold (700) for display
+- Prose content: `max-width: 65ch`. Everything else: fluid full-width.
+- Use `clamp()` for fluid sizing: `clamp(2rem, 1rem + 3vw, 3.75rem)` for h1
+
+### 3. Color & Surfaces
+
+**Goal:** A palette that looks intentional, not random.
+
+- Define all colors as CSS variables or Tailwind config — zero scattered hex values
+- One dominant brand color. One sharp accent for CTAs that pops against the page.
+- Surfaces: layer them. Background → card → elevated card. Use subtle shade differences, not just white-on-white.
+- Dark mode (if present): rethink surfaces, don't just invert. Slightly reduce contrast. Use darker brand colors, not just white→black swap.
+- Semantic colors with non-color indicators: success (green + checkmark), error (red + icon), warning (amber + triangle)
+- Verify WCAG AA: 4.5:1 for normal text, 3:1 for large text (18px+ bold or 24px+)
+
+### 4. Layout & Spacing
+
+**Goal:** Full-width, fluid, generous. No dead space gutters.
+
+- Full-width layouts with fluid padding: `clamp(1rem, 5vw, 4rem)` horizontal
+- 8px spacing grid: 4, 8, 12, 16, 24, 32, 48, 64, 96
+- Tight spacing within groups (related items). Generous spacing between sections.
+- Break symmetry where it serves the design — offset grids, overlapping elements, diagonal flow
+- Varied layouts: not every section should be a centered-text-with-cards-below. Use side-by-side, staggered, asymmetric, full-bleed.
+- Section spacing: `clamp(2rem, 8vw, 6rem)` vertical padding
+
+### 5. Interactive States
 
-### 5. Commit & Transition
+**Goal:** Every clickable thing responds. Every async operation shows progress.
+
+- **Hover:** color shift or underline within 150ms ease-out. `cursor: pointer` on ALL clickables.
+- **Focus:** visible ring (2px+ offset, contrasting color). Never `outline: none` without replacement.
+- **Active/pressed:** subtle scale down (`transform: scale(0.98)`) or color shift.
+- **Disabled:** opacity 0.5 + `cursor: not-allowed` + `aria-disabled="true"`
+- **Loading:** skeleton shimmer or spinner on every async operation. Never a blank void.
+- **Empty:** helpful message + CTA on empty lists/tables. Not just "No results."
+- **Error:** user-friendly message + recovery action. Not raw error text. Use `aria-live="assertive"`.
+
+### 6. Motion & Personality
+
+**Goal:** The site feels alive, not static. But tasteful — not a circus.
+
+- Page load: stagger children entrance (50-80ms delay between items, `fadeUp` animation, 300ms)
+- Hover transitions: 150-200ms ease-out
+- Section transitions: 300-500ms with `cubic-bezier(0.4, 0, 0.2, 1)`
+- One signature motion that gives the site personality (parallax, scroll-triggered reveal, magnetic buttons, morphing shapes)
+- **Always** `prefers-reduced-motion: reduce` — disable non-essential animation
+- CSS-only for static sites, `motion/react` (formerly Framer Motion) for React
+
+### 7. Accessibility (Non-Negotiable)
+
+- Semantic HTML: `nav`, `main`, `section`, `article`, `header`, `footer` — not div soup
+- One `h1` per page, sequential heading order (no h1 → h3 skip)
+- All images: descriptive `alt` (or `alt=""` + `aria-hidden` if decorative)
+- All form inputs: visible `<label>` with `htmlFor` — not placeholder-only
+- All interactive elements: keyboard accessible (Tab, Enter, Escape, Arrow keys)
+- Touch targets: 44x44px minimum
+- Skip link: `<a href="#main" class="sr-only focus:not-sr-only">` as first focusable element
+- `<html lang="en">` set
+- Color never the sole information carrier — icons, text, patterns as supplements
+- `aria-live="polite"` for toast notifications and dynamic content updates
+
+### 8. Responsive (Mobile-First)
+
+- Base styles for mobile (320px), scale up with `min-width` breakpoints
+- Test at: 320px (small phone), 375px (iPhone), 768px (iPad), 1024px (laptop), 1440px (desktop)
+- No horizontal scroll at any viewport
+- Navigation: hamburger/drawer on mobile, full horizontal on desktop
+- Stack on mobile, expand on desktop
+- Fluid typography with `clamp()`
+- Images: `max-width: 100%`, responsive `srcset`, `next/image` with width/height
+- Tables: card layout or horizontal scroll on mobile
+
+### 9. Harden (Edge Cases)
+
+After all visual work, stress-test:
+- Long text: does a 200-character username break the layout?
+- Empty everywhere: all lists empty, all data missing — does it still make sense?
+- Error everywhere: every fetch fails — are error states visible and helpful?
+- 320px viewport: nothing overflows, nothing clips, nothing overlaps
+- Keyboard only: Tab through the entire app — can you reach everything? Is focus visible?
+- Slow network: are loading states visible? Does content stream in or flash?
+
+### 10. Verify & Ship
+
+```bash
+npx tsc --noEmit 2>&1 | head -20
+```
+
+Fix any TypeScript errors.
 
 ```bash
 git add {changed files}
-git commit -m "polish: design and UX pass — typography, accessibility, responsive, states"
+git commit -m "polish: design pass — typography, color, states, motion, responsive, a11y"
 ```
 
 ```bash
 node ~/.claude/bin/state.js transition --to polished
 ```
-Do NOT manually edit STATE.md or tracking.json — state.js handles both.
-
-### 6. Report
 
 ```bash
 node ~/.claude/bin/qualia-ui.js divider
-node ~/.claude/bin/qualia-ui.js info "Files modified: {N}"
-node ~/.claude/bin/qualia-ui.js ok "Typography — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Color — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Layout — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "States — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Motion — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Accessibility — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Responsive — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Performance — {brief}"
-node ~/.claude/bin/qualia-ui.js ok "Hardening — {brief}"
+node ~/.claude/bin/qualia-ui.js ok "AI slop: killed"
+node ~/.claude/bin/qualia-ui.js ok "Typography: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Color: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Layout: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "States: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Motion: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Accessibility: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Responsive: {brief}"
+node ~/.claude/bin/qualia-ui.js ok "Hardened: {brief}"
 node ~/.claude/bin/qualia-ui.js end "POLISHED" "/qualia-ship"
 ```
+
+## Rules
+
+1. **Read before write.** Understand every file before changing it.
+2. **DESIGN.md is law.** If it exists, follow it. Don't override client decisions.
+3. **Don't break functionality.** Only change styling, never logic.
+4. **AI slop is a bug.** Generic fonts, card grids, blue-purple gradients, centered-everything — treat these as defects, not preferences.
+5. **TypeScript must pass** after every change.
+6. **One commit** at the end — not per category.

package/skills/qualia-report/SKILL.md

@@ -73,26 +73,35 @@ git commit -m "report: session {YYYY-MM-DD}"
 git push
 ```
 
-### 5. Upload to ERP
+### 5. Upload to ERP (if enabled)
 
-**This step is MANDATORY** — the clock-out modal requires the report to be uploaded.
+Read `~/.claude/.qualia-config.json` and check the `erp` object:
+- If `erp.enabled` is `false`, skip this step and print: "ERP upload skipped (disabled in config)."
+- If `erp.enabled` is `true` (default) or the `erp` field is missing (backward compatibility), proceed with the upload.
 
 ```bash
-ERP_URL="https://portal.qualiasolutions.net"
+# Read ERP config
+ERP_URL=$(node -e "try{const c=JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.claude/.qualia-config.json','utf8'));console.log(c.erp?.url||'https://portal.qualiasolutions.net')}catch{console.log('https://portal.qualiasolutions.net')}")
+ERP_ENABLED=$(node -e "try{const c=JSON.parse(require('fs').readFileSync(require('os').homedir()+'/.claude/.qualia-config.json','utf8'));console.log(c.erp?.enabled!==false)}catch{console.log('true')}")
+
 API_KEY=$(cat ~/.claude/.erp-api-key 2>/dev/null)
 REPORT_FILE=".planning/reports/report-{date}.md"
 EMAIL=$(git config user.email)
 PROJECT=$(basename $(pwd))
 
-curl -s -X POST "$ERP_URL/api/claude/report-upload" \
-  -H "X-API-Key: $API_KEY" \
-  -F "file=@$REPORT_FILE" \
-  -F "employee_email=$EMAIL" \
-  -F "project_name=$PROJECT"
+# Only upload if ERP is enabled
+if [ "$ERP_ENABLED" = "true" ]; then
+  curl -s -X POST "$ERP_URL/api/claude/report-upload" \
+    -H "X-API-Key: $API_KEY" \
+    -F "file=@$REPORT_FILE" \
+    -F "employee_email=$EMAIL" \
+    -F "project_name=$PROJECT"
+fi
 ```
 
 If the upload succeeds, print: "Report uploaded to ERP. You can now clock out."
 If it fails (no API key, network error), print the error and tell the employee to ask Fawzi.
+If ERP is disabled, print: "ERP upload skipped (disabled in config)."
 
 ### 6. Update State