Code Quality Templates

Artifact Templates — improve-code-quality

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

Artifact Templates — improve-code-quality cover

Skeletons this metaskill creates in the user's docs/ folder.

# Artifact Templates — improve-code-quality

Skeletons this metaskill creates in the user's `docs/` folder. Extend-only artifacts (ARCHITECTURE.md) are governed by the section headings named in each phase, not duplicated here. Copy a skeleton verbatim the first time you create its file; on later phases, extend the existing file — add or update your own sections, preserve everyone else's.

## docs/IMPROVE-CODE-QUALITY-PLAN.md (tracker)

Created on first run; never shared with other journeys. The Phase Status table is pre-filled with this journey's real phases.

```markdown
# Improve Code Quality Plan

## Context
Intake answers, date started, project specifics (stack, starting module, production status, load).

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 — Build the safety net | working-with-legacy-code | pending | TESTING.md + TECH-DEBT.md (GATE) | |

Overview

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (ARCHITECTURE.md) are governed by the section headings named in each phase, not duplicated here. Copy a skeleton verbatim the first time you create its file; on later phases, extend the existing file — add or update your own sections, preserve everyone else's.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill artifact-templates-improve-code-quality -g -a claude-code
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • artifact-templates.md3.3 KB
Read artifact-templates.md here
wondelai/main1 file
artifact-templates.md
Show the full text102 lines

Artifact Templates — improve-code-quality

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (ARCHITECTURE.md) are governed by the section headings named in each phase, not duplicated here. Copy a skeleton verbatim the first time you create its file; on later phases, extend the existing file — add or update your own sections, preserve everyone else's.

docs/IMPROVE-CODE-QUALITY-PLAN.md (tracker)

Created on first run; never shared with other journeys. The Phase Status table is pre-filled with this journey's real phases.

# Improve Code Quality Plan

## Context
Intake answers, date started, project specifics (stack, starting module, production status, load).

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 — Build the safety net | working-with-legacy-code | pending | TESTING.md + TECH-DEBT.md (GATE) | |
| 2 — Make the code readable | clean-code | pending | TECH-DEBT.md | |
| 3 — Apply named refactorings | refactoring-patterns | pending | TECH-DEBT.md | |
| 4 — Reduce complexity | software-design-philosophy | pending | TECH-DEBT.md | |
| 5 — Draw the architecture boundary | clean-architecture | pending | ARCHITECTURE.md | |
| 6 — Lock in the habits | pragmatic-programmer | pending | TECH-DEBT.md | |
| 7 — Make it survive production | release-it | pending | RELIABILITY.md | |
| 8 — Size for real load | system-design | pending | ARCHITECTURE.md + RELIABILITY.md | |
| 9 — Get the data layer right | ddia-systems | pending | ARCHITECTURE.md | |
| Optional — Domain language | domain-driven-design | pending | ARCHITECTURE.md | |
Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>

## Key Decisions
| Date | Phase | Decision | Rationale |
|---|---|---|---|

## Next Actions
- [ ] action (owner, due)

docs/TESTING.md

Created in Phase 1. The safety net — what behavior is pinned, where the gaps are.

# Testing

## Test Strategy
Pyramid, tooling, what "green" gates.

## Safety Net Map
| Module | Pinned behaviors | Test files | Gaps |
|---|---|---|---|

## Characterization Backlog
- [ ] module (risk, priority)

## CI Gates

docs/TECH-DEBT.md

Created in Phase 1; extended in Phases 2, 3, 4, and 6. The debt ledger — single queue for all code-quality work.

# Technical Debt

## Debt Ledger
| Item | Location | Type | Risk | Effort | Priority | Status |
|---|---|---|---|---|---|---|

## Smell Inventory
| Smell | Location | Refactoring | Status |
|---|---|---|---|

## Sprout / Wrap Register
Code added beside legacy (to fold back in later).

## Debt Budget & Broken-Windows Policy
Time per iteration; what gets fixed now vs boarded up with a ticket.

## Adopted Conventions

docs/RELIABILITY.md

Created in Phase 7; extended in Phase 8. Production hardening status.

# Reliability

## Integration-Point Audit
| Dependency | Timeout | Circuit breaker | Bulkhead | Retry policy | Status |
|---|---|---|---|---|---|

## Query & Resource Findings
Unbounded result sets, missing LIMITs/pagination, blocked threads.

## Health Checks & Metrics
Deep health checks · RED metrics · symptom-based alerts.

## Deploy vs Release
Feature flags, expand-contract migrations, rollback plan.
1# Artifact Templates — improve-code-quality
2 
3Skeletons this metaskill creates in the user's `docs/` folder. Extend-only artifacts (ARCHITECTURE.md) are governed by the section headings named in each phase, not duplicated here. Copy a skeleton verbatim the first time you create its file; on later phases, extend the existing file — add or update your own sections, preserve everyone else's.
4 
5## docs/IMPROVE-CODE-QUALITY-PLAN.md (tracker)
6 
7Created on first run; never shared with other journeys. The Phase Status table is pre-filled with this journey's real phases.
8 
9```markdown
10# Improve Code Quality Plan
11 
12## Context
13Intake answers, date started, project specifics (stack, starting module, production status, load).
14 
15## Phase Status
16| Phase | Skill | Status | Artifact | Date |
17|---|---|---|---|---|
18| 1 — Build the safety net | working-with-legacy-code | pending | TESTING.md + TECH-DEBT.md (GATE) | |
19| 2 — Make the code readable | clean-code | pending | TECH-DEBT.md | |
20| 3 — Apply named refactorings | refactoring-patterns | pending | TECH-DEBT.md | |
21| 4 — Reduce complexity | software-design-philosophy | pending | TECH-DEBT.md | |
22| 5 — Draw the architecture boundary | clean-architecture | pending | ARCHITECTURE.md | |
23| 6 — Lock in the habits | pragmatic-programmer | pending | TECH-DEBT.md | |
24| 7 — Make it survive production | release-it | pending | RELIABILITY.md | |
25| 8 — Size for real load | system-design | pending | ARCHITECTURE.md + RELIABILITY.md | |
26| 9 — Get the data layer right | ddia-systems | pending | ARCHITECTURE.md | |
27| Optional — Domain language | domain-driven-design | pending | ARCHITECTURE.md | |
28Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>
29 
30## Key Decisions
31| Date | Phase | Decision | Rationale |
32|---|---|---|---|
33 
34## Next Actions
35- [ ] action (owner, due)
36```
37 
38## docs/TESTING.md
39 
40Created in Phase 1. The safety net — what behavior is pinned, where the gaps are.
41 
42```markdown
43# Testing
44 
45## Test Strategy
46Pyramid, tooling, what "green" gates.
47 
48## Safety Net Map
49| Module | Pinned behaviors | Test files | Gaps |
50|---|---|---|---|
51 
52## Characterization Backlog
53- [ ] module (risk, priority)
54 
55## CI Gates
56```
57 
58## docs/TECH-DEBT.md
59 
60Created in Phase 1; extended in Phases 2, 3, 4, and 6. The debt ledger — single queue for all code-quality work.
61 
62```markdown
63# Technical Debt
64 
65## Debt Ledger
66| Item | Location | Type | Risk | Effort | Priority | Status |
67|---|---|---|---|---|---|---|
68 
69## Smell Inventory
70| Smell | Location | Refactoring | Status |
71|---|---|---|---|
72 
73## Sprout / Wrap Register
74Code added beside legacy (to fold back in later).
75 
76## Debt Budget & Broken-Windows Policy
77Time per iteration; what gets fixed now vs boarded up with a ticket.
78 
79## Adopted Conventions
80```
81 
82## docs/RELIABILITY.md
83 
84Created in Phase 7; extended in Phase 8. Production hardening status.
85 
86```markdown
87# Reliability
88 
89## Integration-Point Audit
90| Dependency | Timeout | Circuit breaker | Bulkhead | Retry policy | Status |
91|---|---|---|---|---|---|
92 
93## Query & Resource Findings
94Unbounded result sets, missing LIMITs/pagination, blocked threads.
95 
96## Health Checks & Metrics
97Deep health checks · RED metrics · symptom-based alerts.
98 
99## Deploy vs Release
100Feature flags, expand-contract migrations, rollback plan.
101```
102 
View all files on GitHub →

Details

Updated
Sep 10, 2026
License
MIT
Stars on the repo
★ 2,235
Checked
Source
wondelai/skills ↗
Creator
wondelai · 319 listings
View creator

Similar skills

See all →

More from wondelai

SkillSoftware Design Philosophywondelai/skills · by wondelaiManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.★ 2.2k GitHub starsSkillActionable Metrics Guidewondelai/skills · by wondelaiMetrics are the language of validated learning. The wrong metrics create the illusion of progress while the startup drifts toward failure.…★ 2.2k GitHub starsSkillAdvertising Mediawondelai/skills · by wondelaiAdvertising media is the vehicle that carries your message to your target market. Choosing the right media is not about what is trendy — it…★ 2.2k GitHub starsSkillAffordance Designwondelai/skills · by wondelaiAn affordance is a relationship between an object and a person that determines how the object could possibly be used. A chair affords…★ 2.2k GitHub starsSkillLean UX in Agile Teamswondelai/skills · by wondelaiLean UX was designed to work inside Agile development teams, not alongside them. The central mechanism is dual-track agile, where a…★ 2.2k GitHub starsSkillAMP Framework Practitionerwondelai/skills · by wondelaiThis reference translates the AMP framework from theory into practice across six domains: product gamification, team management,…★ 2.2k GitHub stars