Automatically loaded by Claude Code for ALL sessions and subagents. Critical rules are in
.claude/rules/(also auto-loaded). Detailed references in.claude/references/— load on-demand, not by default.
@AGENTS.md
React 19 + TypeScript 5.7 + Vite 6 + Zustand 5 + Tone.js + Tailwind CSS v4
npm run dev # Dev server (http://127.0.0.1:5174)
npm test # Vitest unit tests
npm run test:watch # Vitest in watch mode
npm run test:e2e # Playwright E2E tests
npm run test:all # Unit + E2E
npm run test:coverage # Unit tests with coverage report
npm run build # TypeScript check + Vite build
npx tsc --noEmit # Type check only- Done Criteria: Write acceptance criteria checklist in the GitHub Issue body (or PR description) before coding features touching 3+ files. Include edge cases. Each item must be verifiable by test, screenshot, or store assertion.
- External Evaluation: Never self-assess. Run
@testerbefore every commit. - Context Anxiety: If re-reading files, adding defensive checks, duplicating utilities, or skipping tests — STOP and compact.
- Use
@do-todofor individual tasks,@testerafter each task - Record blockers to
.llm/BLOCKERS.md
- Modified files list and paths
- Current GitHub Issue number and progress
- Test results (passed/failed)
- Blockers from
.llm/BLOCKERS.md
src/store/— Zustand stores (projectStore, transportStore, generationStore, uiStore)src/engine/— Audio engine (Tone.js wrappers)src/services/— Business logic (API, generation pipeline, storage)src/components/— React UI componentssrc/hooks/— React hookssrc/utils/— Pure utility functionssrc/types/— TypeScript interfacestests/e2e/— Playwright E2E tests
Full git rules in
.claude/rules/git-conventions.md(auto-loaded).
- Branch:
feat/issue-NUMBER,fix/issue-NUMBER(preferred) orfeat/v0.0.X-xxx - Commits:
feat:,fix:,docs:,refactor:,test:,chore: - Identity:
user.name: ChuxiJ,user.email: junmin@acestudio.ai
- Interaction Design:
.claude/references/interaction-design.md— UI patterns, drag/drop, keyboard, feedback - Design Patterns:
.claude/references/design-patterns.md— Concrete sizing, color, spacing, typography rules for DAW UI - Store API:
.claude/references/store-api.md—window.__storeAPI, CLI-first mandate, testing standard - Skills:
.claude/references/skills.md— Recommended Claude Code skills by development step
Before coding any non-trivial feature, create a formal spec:
/opsx:propose "feature-name" # Create proposal + specs + design + tasks
/opsx:explore # Browse existing specs
/opsx:apply # Implement tasks from a change
/opsx:archive # Archive completed change into specs/- Specs live in
openspec/specs/(tracked in git — living behavior contracts) - Change proposals live in
openspec/changes/(gitignored — working directory) - Specs use Given/When/Then scenarios and RFC 2119 keywords (MUST, SHALL)
- Agents read specs before TDD Red phase for test generation
Standalone monitoring UI for the agent orchestration system (pm-auto.sh, sprint-runner, registry).
npm run dashboard # Start at http://127.0.0.1:5175
npm run dashboard:build # Build static assets- Reads
.pm/files (activity.log, agent-registry.json) + GitHub API - Real-time updates via WebSocket (push on file change + 30s GitHub poll)
- Shows: agent capacity, pipeline kanban, activity feed, PR status cards
Use /browse for all web browsing. Never use mcp__Claude_in_Chrome__* tools.
Available: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /review, /ship, /browse, /qa, /qa-only, /design-review, /setup-browser-cookies, /retro, /investigate, /document-release, /codex, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade