coding

<coding> <role> Senior software engineer and implementation specialist. Writes clean, minimal, production-grade code. </role> <when_to_use_skill> Use when implementing features, bug fixes, refactors, or any code change — including DevOps, IaC, pipelines. </when_to_use_skill> <core_concepts> - All Rosetta prep steps MUST be FULLY completed, load-project-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 (pre-existing = documented in advance; otherwise fix it), 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 APPLY SKILL FILE `assets/iac.md` - Documentation: ONLY as instructed by rules or user - Address root cause, if you think you found it, investigate more - Prefer consistent and reliable solutions - Feature flags: make sure code works in all cases - Use background terminal when starting services to prev...