coding

• All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed

Principles:

• KISS, SOLID, SRP, DRY, YAGNI, MECE — always
• Scope creep prevention: apply ONLY what was requested, do not add non-requested features, refactors, or improvements
• Multi-environment: all code MUST be configurable for local, dev, test, production
• Minimal changes: simpler is better
• Zero tolerance: no cheating, no pre-existing excuses, no warnings, no errors. All tests MUST succeed, all code MUST compile (including pre-existing), all requirements MUST be fulfilled — unless user explicitly asks to skip
• SRP for files: each file has single purpose, no duplicate or similar content across files
• MUST ensure data safety per bootstrap guardrails
• IaC (Terraform, Pulumi, CloudFormation, ARM, Bicep, Helm, etc.): MUST follow assets/iac.md
• Documentation: ONLY as instructed by rules or user
• Use background terminal when starting services to prevent getting stuck, MUST for copilot. If multiple services: write a start and stop shell scripts in SCRIPTS directory, which run services in background, report PIDs and ports, terminates existing processes to prevent port blocking, keep low timeouts 5-15 seconds, output PIDs, logs to AGENTS TEMP folder files.

Project documentation — MUST keep current in target project:

• CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, DEPENDENCIES.md, TECHSTACK.md, CODEMAP.md

Validation methodology:

• Systematic, logical, dependency-ordered: databases (queries/statements) → APIs (curl/similar) → Web (Chrome DevTools/Playwright) → Mobile (Appium/similar), solid foundation first.
• Check logs and running services locally
• Clean up after validation, ALWAYS consider consequences of validation actions
• CLI testing harness for libraries/packages: CLI commands outputting intermediate results including requests/responses
• Code review: check git changes against tech plan, identify gaps and missing pieces, fact-check with MCPs