Development
AI Collaboration
Rule ownership, eight repo skills, layered implementation, and verification.
Rules and Documentation
AGENTS.md: source of truth for architecture, boundaries, routing, and verification defaults.README.md: human-facing positioning, setup, commands, and deployment entry points..agents/skills/*/SKILL.md: task workflows, real entry points, and done criteria.CLAUDE.md: tool/runtime preferences, not another copy of architecture rules.tests/README.mdandtests/e2e/SCENARIOS.md: test setup and browser acceptance map.
Task Routing
| Skill | Scope |
|---|---|
musemvp-decide-next-step | Broad/mixed tasks and phase ordering |
musemvp-configure-public-surface | Public copy, pages, navigation, pricing presentation, content |
musemvp-configure-saas-layout | Signed-in sidebar/header/profile shell |
musemvp-configure-saas-page-route | Only the /app home route |
musemvp-build-product-behavior | Behavior, data, auth, billing, API |
musemvp-testing-guidance | Test layers and coverage |
musemvp-review-risks | Merge/launch risk review |
musemvp-generate-changelog | Bilingual changelog from commits |
Compatible tools read skills; automatic loading is not guaranteed in every IDE. Do not assume old docs prove a bundled general-purpose skill library or automatic deployment workflows.
Delivery Loop
- Inspect the owning route/module/config/query and
AGENTS.md. - Define acceptance; update
SCENARIOS.mdfor browser journeys. - Write failing tests first for package behavior, schemas, and bug fixes.
- Implement
queries → modules/lib → routes → api-client → UI. Drivers belong in appsrc/server; auth/API wiring stays insrc/backend. - Manually verify the real app before fixing automated assertions, then run the narrowest useful tests.
- Report passed, failed, unrun, and deferred paths. Types/rendering alone are not acceptance.
Packages cannot use app @/; modules do not access DB directly. Derivative messages go only into packages/i18n/src/translations/{en,zh}/mvp.json. Check pnpm apps:parity for page/content changes. Before Next.js 16 edits, read the relevant installed node_modules/next/dist/docs/ guide rather than relying on old API assumptions.
Reusable Prompt
Goal: implement concrete behavior in src/modules/<feature>.
Inspect AGENTS.md, the owning entry points, and the relevant Skill first.
Define acceptance and write a failing test for new behavior or a bug.
Preserve package/app boundaries and synchronize en/zh mvp.json and page copies.
Manually verify errors, empty states, and permissions, then add minimal unit/API/E2E coverage.
Run relevant checks and report actual results and unverified paths.See Testing and Acceptance and Release Checklist. Fast-moving tool tips/community content does not replace repository rules.