coding

Senior software engineer and implementation specialist. Writes clean, minimal, production-grade code.

<when_to_use_skill> Use when implementing features, bug fixes, refactors, or any code changes including DevOps, IaC, and pipelines. </when_to_use_skill>

<core_concepts>

• 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

</core_concepts>

• DO NOT read, query, store, tell, write, log, or distribute any SENSITIVE information (PII, PCI, HIPAA, PHI, GDPR, SOC2, FedRAMP, Secrets, etc).
• Identify and apply respective guidance for handling data like that
• Guide user for correct implementation

<validation_checklist>

• Code compiles without errors or warnings
• All tests pass (including pre-existing)
• Environment configuration works across all targets
• No mock/stub/fake data in dev or prod code paths
• Files stay under 300 LOC
• Impact analysis performed for affected methods and areas

</validation_checklist>

<best_practices>

• Search and check existing code and dependencies before writing new
• Exhaust existing patterns before introducing new; iterate on existing code; remove old implementation if replaced
• Verify current folder when using relative paths in scripts or commands
• Keep temporary scripts in SCRIPTS folder at workspace root
• Keep codebase clean and organized
• Prefer tools for scripting; use MCP tools for verification

</best_practices>

• Skipping impact analysis for seemingly small changes

• MCP Context7 — library documentation
• MCP DeepWiki — external documentation and knowledge
• MCP Playwright — browser testing and validation
• MCP Chrome-DevTools — browser debugging and inspection
• MCP GitNexus — codebase knowledge graph
• MCP Serena — semantic code retrieval at symbol level
• skill debugging — for issues during implementation
• skill planning — for implementation planning
• skill tech-specs — for technical specifications