quartier CLAUDE.md

Quartier

Read and follow the instructions in PLAYBOOK.md. That file has the complete workflow.

Testing

Run npm test (Vitest, tests in test/*.test.js). Details in TESTING.md.

• When writing a new function, write a corresponding test
• When fixing a bug, write a regression test that would have caught it
• When adding error handling, write a test that triggers the error
• When adding a conditional, write tests for BOTH paths
• Never commit code that makes existing tests fail

Claude-specific

When generating HTML pages (home, subpages, showcase), use the /business-web-design skill (in .claude/skills/). It enforces the PLAYBOOK design quality bar mechanically: design-lock header, banned AI tells, motion degradation, and scripts/verify_design.py must report 0 FAILs before showing output. (/frontend-design remains available but is superseded for business sites — benchmarked at 62% vs 100% on the quality assertions, see .claude/skills/business-web-design-workspace/iteration-1/benchmark.md.)

Skill routing

When the user's request matches an available skill, invoke it via the Skill tool. The skill has multi-step workflows, checklists, and quality gates that produce better results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is cheaper than a false negative.

Key routing rules:

• Product ideas, "is this worth building", brainstorming → invoke /office-hours
• Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
• Architecture, "does this design make sense" → invoke /plan-eng-review
• Design system, brand, "how should this look" → invoke /design-consultation
• Design review of a plan → invoke /plan-design-review
• Developer experience of a plan → invoke /plan-devex-review
• "Review everything", full review pipeline → invoke /autoplan
• Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
• Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
• Code review, check the diff, "look at my changes" → invoke /review
• Visual polish, design audit, "this looks off" → invoke /design-review
• Developer experience audit, try onboarding → invoke /devex-review
• Ship, deploy, create a PR, "send it" → invoke /ship
• Merge + deploy + verify → invoke /land-and-deploy
• Configure deployment → invoke /setup-deploy
• Post-deploy monitoring → invoke /canary
• Update docs after shipping → invoke /document-release
• Weekly retro, "how'd we do" → invoke /retro
• Second opinion, codex review → invoke /codex
• Safety mode, careful mode, lock it down → invoke /careful or /guard
• Restrict edits to a directory → invoke /freeze or /unfreeze
• Upgrade gstack → invoke /gstack-upgrade
• Save progress, "save my work" → invoke /context-save
• Resume, restore, "where was I" → invoke /context-restore
• Security audit, OWASP, "is this secure" → invoke /cso
• Make a PDF, document, publication → invoke /make-pdf
• Launch real browser for QA → invoke /open-gstack-browser
• Import cookies for authenticated testing → invoke /setup-browser-cookies
• Performance regression, page speed, benchmarks → invoke /benchmark
• Review what gstack has learned → invoke /learn
• Tune question sensitivity → invoke /plan-tune
• Code quality dashboard → invoke /health