Axidify Implement
Not this skill: unexplained errors, regressions, or “why does X fail?” with no
clear fix yet → debug. New features with unclear design →
plan first. Multi-phase work from docs/plans/*.md → plan-driven-implementation.
Checklist
- Discover — if needed, run discover-project; read relevant agent rules
- Inspect — find current behavior and all affected files
- Report — summarize state, gaps, and planned diff before large edits
- Implement — minimal change that meets the request; match existing style
- Verify — run lint, typecheck, and tests the project defines (discover from
package.json, Makefile, CI, or linter configs — eslint, ruff, clippy, etc.) - Report — files changed, what changed, limitations, anything not done
For large multi-area work, explore with subagents/Task first, then implement in focused passes.
Error rules
| Situation | Action |
|---|---|
| Build / typecheck fails from your changes | Fix before finishing |
| Tests fail from your changes | Fix |
| Tests fail unrelated | Report; do not “fix” opportunistically |
| Runtime error while verifying | Use debug, then return here |
Scope
- No drive-by refactors or unrelated files
- No commits unless the user asked to commit
- Questions (
?, “how does”, “should we”) → answer only; do not implement until approved
Related skills
- test — run after verify when tests apply
- review — three-pass review before commit or PR
- security / performance — deep pass when those risks dominate
- debug — unexplained failures during verify
- plan-driven-implementation — phased work tracked in
docs/plans/ - web-design-engineer — design-led UI in-repo (then return here for minimal diff)