feat: implement new claude skills and workflow
All checks were successful
Deploy to Staging / Build Images (push) Successful in 23s
Deploy to Staging / Deploy to Staging (push) Successful in 36s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 6s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
All checks were successful
Deploy to Staging / Build Images (push) Successful in 23s
Deploy to Staging / Deploy to Staging (push) Successful in 36s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 6s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
This commit is contained in:
46
CLAUDE.md
46
CLAUDE.md
@@ -45,24 +45,23 @@ private mapRow(row: any): MyType {
|
||||
|
||||
All methods returning data to the API must use these mappers - never return raw database rows.
|
||||
|
||||
## Docker-First Implementation Strategy
|
||||
## Development Workflow (Local + CI/CD)
|
||||
|
||||
### 1. Package.json Updates Only
|
||||
File: `frontend/package.json`
|
||||
- Add `"{package}": "{version}"` to dependencies
|
||||
- No npm install needed - handled by container rebuild
|
||||
- Testing: Instruct user to rebuild the containers and report back build errors
|
||||
|
||||
### 2. Container-Validated Development Workflow (Production-only)
|
||||
### Local Development
|
||||
```bash
|
||||
# After each change:
|
||||
Instruct user to rebuild the containers and report back build errors
|
||||
make logs # Monitor for build/runtime errors
|
||||
npm install # Install dependencies
|
||||
npm run dev # Start dev server
|
||||
npm test # Run tests
|
||||
npm run lint # Linting
|
||||
npm run type-check # TypeScript validation
|
||||
```
|
||||
|
||||
### 3. Docker-Tested Component Development (Production-only)
|
||||
- Use local dev briefly to pinpoint bugs (hook ordering, missing navigation, Suspense fallback behavior)
|
||||
- Validate all fixes in containers.
|
||||
### CI/CD Pipeline (on PR)
|
||||
- Container builds and integration tests
|
||||
- Mobile/desktop viewport validation
|
||||
- Security scanning
|
||||
|
||||
**Flow**: Local dev -> Push to Gitea -> CI/CD runs -> PR review -> Merge
|
||||
|
||||
|
||||
## Quality Standards
|
||||
@@ -133,12 +132,27 @@ Issues are the source of truth. See `.ai/workflow-contract.json` for complete wo
|
||||
**MotoVaultPro uses a simplified architecture:** A single-tenant application with 5 containers - Traefik, Frontend, Backend, PostgreSQL, and Redis. Application features in `backend/src/features/[name]/` are self-contained modules within the backend service, including the platform feature for vehicle data and VIN decoding.
|
||||
|
||||
### Key Principles for AI Understanding
|
||||
- **Production-Only**: All services use production builds and configuration
|
||||
- **Docker-First**: All development in containers, no local installs
|
||||
- **Feature Capsule Organization**: Application features are self-contained modules within the backend
|
||||
- **Single-Tenant**: All data belongs to a single user/tenant
|
||||
- **User-Scoped Data**: All application data isolated by user_id
|
||||
- **Local Dev + CI/CD**: Development locally, container testing in CI/CD pipeline
|
||||
- **Integrated Platform**: Platform capabilities integrated into main backend service
|
||||
|
||||
### Common AI Tasks
|
||||
See `Makefile` for authoritative commands and `docs/README.md` for navigation.
|
||||
|
||||
## Agent System
|
||||
|
||||
| Directory | Contents | When to Read |
|
||||
|-----------|----------|--------------|
|
||||
| `.claude/role-agents/` | Developer, TW, QR, Debugger | Delegating execution |
|
||||
| `.claude/role-agents/quality-reviewer.md` | RULE 0/1/2 definitions | Quality review |
|
||||
| `.claude/skills/planner/` | Planning workflow | Complex features (3+ files) |
|
||||
| `.claude/skills/problem-analysis/` | Problem decomposition | Uncertain approach |
|
||||
| `.claude/agents/` | Domain agents | Feature/Frontend/Platform work |
|
||||
| `.ai/workflow-contract.json` | Sprint process, skill integration | Issue workflow |
|
||||
|
||||
### Quality Rules (see quality-reviewer.md for full definitions)
|
||||
- **RULE 0 (CRITICAL)**: Production reliability - unhandled errors, security, resource exhaustion
|
||||
- **RULE 1 (HIGH)**: Project standards - mobile+desktop, naming, patterns, CI/CD pass
|
||||
- **RULE 2 (SHOULD_FIX)**: Structural quality - god objects, duplication, dead code
|
||||
|
||||
Reference in New Issue
Block a user