Read CONTRIBUTING.md for conventions and delivery requirements.
See code conventions for naming and comments and the
documentation index for current guides and proposals.
Use Node.js 24 and pnpm. Routes live in apps/web/app/, shared product components in
apps/web/ui/common/, feature components in apps/web/ui/<area>/, domain logic in
apps/web/lib/ and the vendored design system in packages/ui/. Dependency versions live
only in the catalog: block of pnpm-workspace.yaml. See architecture
for boundaries.
Load the skills relevant to the task:
- coursemap-conventions: house style, naming, comments and file placement.
- coursemap-workspace: dependencies, scripts, packages and build configuration.
- nextjs-development: routes, React state and data flow.
- coursemap-ui: pages, components and accessibility. Also read UI conventions.
- coursemap-testing: regression coverage and test implementation.
- supabase-change: schema, permissions, auth and generated types.
- catalogue-import: ANU ingestion and publication.
- verify-coursemap: checks before hand-off.
- Inspect the working tree and preserve unrelated changes. Use an isolated worktree when another task is active.
- Keep durable catalogue and plan data in the database. Regenerate database types rather than editing generated output.
- Keep secrets out of Git and browser bundles. Document configuration requirements in
apps/web/.env.example. - Follow the user's delivery scope. Local work does not authorise hosted mutations, deployment or destructive Git operations.
- Run
pnpm verifybefore hand-off and report blocked checks explicitly. Keep local, browser, CI and production evidence distinct.