coding
Implement the approved architecture and plan while following coding standards, guardrails, and review outcomes.
When & Why to Use This Skill
This Claude skill automates the transition from technical design to production-ready code by implementing approved architectural plans. It ensures high-quality software development by strictly adhering to organizational coding standards, security guardrails, and testing policies, providing a streamlined workflow for reliable and maintainable code delivery.
Use Cases
- Feature Implementation: Converting technical specifications and architectural blueprints into functional, well-documented code modules.
- Standardized Refactoring: Updating existing codebases to align with new coding standards or security guardrails without altering the intended scope.
- Test-Driven Development: Automatically generating implementation logic alongside required unit tests to ensure compliance with project testing policies.
- Policy-Compliant Integration: Executing code changes that strictly follow pre-defined PR rules and review outcomes to maintain repository integrity.
| name | coding |
|---|---|
| description | Implement the approved architecture and plan while following coding standards, guardrails, and review outcomes. |
Purpose
Apply code changes aligned with the plan and policies, with concise summaries and test results.
Inputs
- Approved plan and architecture decisions
- Applicable policies (
guardrails,coding_standards,commit_pr_rules,testing_policy) - Selected review outcomes and constraints
Steps
- Load the approved plan, architecture, and policies.
- Implement changes scoped to the plan; avoid scope creep.
- Keep code clear, small, and testable; document non-obvious logic concisely.
- Validate against inputs and expected behavior; prepare tests per policy.
- Summarize changes, files touched, and testing performed.
Outputs
- Code changes aligned with the plan and policies, plus summaries and test results.
Failure modes
- Altering scope or architecture without approval
- Skipping required tests or violating policies
- Introducing nondeterministic or unsafe behavior