// Run build verification and code formatting across all RAPID project components (backend, frontend, CDK). Use after implementing code changes, before committing, after modifying Prisma schema, or before creating a pull request.
Deploy RAPID application AWS infrastructure using CDK, including stack deployment, database migrations, and post-deployment verification. Use when explicitly asked to deploy, when running CDK bootstrap for first-time setup, or when deploying after code or infrastructure changes. Only execute when user says "please deploy".
Add new example use cases to the Examples feature, including file setup, metadata registration, thumbnail generation, and link verification. Use when a contributor provides PDF/PNG/TXT files for a new use case, when adding entries to the Examples page, or when verifying existing example GitHub URLs are accessible.
Modify the review-item-processor agent's prompts, model configuration, confidence thresholds, JSON output schemas, and tool setup. Use when changing document or image review prompts, adjusting model IDs, modifying output format, updating citation settings, or adding new tools to the agent.
Modify CDK Step Functions workflows (ReviewProcessor and ChecklistProcessor) for the RAPID application, including workflow step changes, Map State concurrency, retry/timeout configuration, error handling, and parameter updates. Use when changing workflow step sequences, adjusting concurrency, modifying retry logic, or adding/removing workflow steps.
Create implementation plans for backend API endpoints and frontend features following RAPID layered architecture (domain/usecase/routes pattern, SWR hooks, feature-based organization). Use when adding or modifying backend APIs, frontend components, database schemas, or repository implementations. Also use for refactoring backend/frontend code.
Run repository integration tests against a local MySQL database for the RAPID backend. Use after implementing new repository methods, modifying Prisma database schema, testing use cases that depend on database access, or verifying data access patterns.
| name | build-and-format |
| description | Run build verification and code formatting across all RAPID project components (backend, frontend, CDK). Use after implementing code changes, before committing, after modifying Prisma schema, or before creating a pull request. |
Run builds in dependency order (backend must build before CDK):
# 1. Backend (must be first - CDK depends on it)
cd backend
npm run build
npm run format
# 2. Frontend
cd ../frontend
npm run build
npm run format
# 3. CDK (depends on backend build)
cd ../cdk
npx cdk synth
After modifying backend/prisma/schema.prisma:
cd backend
npm run prisma:generate
npm run build
npm run format
| Error | Solution |
|---|---|
Module not found: @prisma/client | cd backend && npm run prisma:generate |
Cannot find module '../backend/...' (CDK) | Build backend first |
Docker daemon not running (CDK synth) | Start Docker Desktop |
| Task | Command |
|---|---|
| Backend build + format | cd backend && npm run build && npm run format |
| Frontend build + format | cd frontend && npm run build && npm run format |
| CDK synth | cd cdk && npx cdk synth |
| Prisma generate | cd backend && npm run prisma:generate |
After successful build, consider running /test-database-feature if database changes were made.