32 lines
2.1 KiB
Markdown
32 lines
2.1 KiB
Markdown
Load .ai/context.json to understand the project's danger zones and loading strategies
|
|
|
|
Load AI_README.md and @PROJECT_MAP.md to gain context on the application.
|
|
|
|
CRITICAL: All development practices and choices should be made taking into account the most context effecient interation with another AI. Any AI should be able to understand this applicaiton with minimal prompting.
|
|
|
|
CRITICAL: All development/testing happens in Docker containers, no local package installations:
|
|
- Development: Dockerfile.dev with npm install during container build
|
|
- Testing: make test runs tests in container
|
|
- Rebuilding: make rebuild for code changes
|
|
- Package changes: Container rebuild required
|
|
|
|
Docker-First Implementation Strategy
|
|
|
|
1. Package.json Updates Only
|
|
|
|
File: frontend/package.json
|
|
- Add "{package}": "{version}" to dependencies
|
|
- No npm install needed - handled by container rebuild
|
|
- Testing: make rebuild then verify container starts
|
|
|
|
2. Container-Validated Development Workflow
|
|
|
|
# After each change:
|
|
make rebuild # Rebuilds containers with new dependencies
|
|
make logs # Monitor for build/runtime errors
|
|
|
|
3. Docker-Tested Component Development
|
|
|
|
- All testing in containers: make shell-frontend for debugging
|
|
- File watching works: Vite dev server with --host 0.0.0.0 in container
|
|
- Hot reload preserved: Volume mounts sync code changes |