-
Notifications
You must be signed in to change notification settings - Fork 16
Home
rtd edited this page Jan 14, 2026
·
16 revisions
Code Complete-based software engineering skills for Claude Code.
User: "X isn't working, use foundations to debug it"
→ code-foundations classifies as DEBUG
→ cc-developer-character checks mindset
→ cc-quality-practices: hypothesis → verify → fix
User: "Build feature X with foundations"
→ code-foundations classifies as WRITE
→ cc-construction-prerequisites: requirements check
→ cc-pseudocode-programming: design first
→ CHECKER gates before done
User: "Use foundations to review this code"
→ cc-quality-practices (CHECKER mode)
→ cc-routine-and-class-design (CHECKER mode)
→ Output: violations, warnings, fixes
User: "Clean this up with foundations"
→ cc-refactoring-guidance: plan steps
→ Execute one change at a time
→ CHECKER gates verify quality preserved
| Skill | Purpose | Example |
|---|---|---|
| code-foundations | Master dispatcher | "use foundations to [anything]" |
| cc-developer-character | Mindset and discipline | "use dev character to check my approach" |
| cc-construction-prerequisites | Requirements and planning | "use prereqs to review this plan" |
| cc-pseudocode-programming | Design routines first | "use pseudocode to design this feature" |
| cc-quality-practices | Reviews, testing, debugging | "use quality practices to review this code" |
| cc-routine-and-class-design | High-quality interfaces | "use routine design to review this code" |
| cc-control-flow-quality | Clean control structures | "use control flow to review this code" |
| cc-data-organization | Variables, naming, types | "use data org to review this code" |
| cc-defensive-programming | Error handling | "use defensive programming to review this code" |
| cc-code-layout-and-style | Formatting and comments | "use layout style to review this code" |
| cc-refactoring-guidance | Safe refactoring | "use refactoring to clean this up" |
| cc-integration-practices | Integration and builds | "use integration to review this merge" |
| cc-performance-tuning | Measure-first optimization | "use perf tuning, this is slow" |
Question:
"The picker text is overflowing into the icons on the right side"
Result:
Step 1: Task Classification
→ DEBUG (signals: "overflowing", visual bug)
Step 2: Developer Character Check ✓
Step 3: Root Cause Analysis
| Location | Uses maxWidth? |
|-----------------|----------------|
| ResultRow | ✓ maxWidth set |
| PickerTextField | ✗ No maxWidth |
Root cause: PickerTextField missing the pattern already used elsewhere.
Step 4: Surgical Fix
→ Add maxWidth: "calc(100% - iconSpace)" to PickerTextField
→ Done in 57 seconds
The skills chain together based on task type:
code-foundations (dispatcher)
│
├── DEBUG ──→ cc-developer-character ──→ cc-quality-practices
│ │
│ └── Scientific Method
│ (hypothesis → verify → fix)
│
├── WRITE ──→ cc-developer-character ──→ cc-construction-prerequisites
│ │
│ └── cc-pseudocode-programming
│ (design before code)
│
├── REVIEW ─→ cc-quality-practices ──→ cc-routine-and-class-design
│ │
│ └── CHECKER mode
│ (violations, warnings)
│
└── REFACTOR → cc-developer-character ──→ cc-refactoring-guidance
│
└── cc-control-flow-quality (CHECKER)
cc-routine-and-class-design (CHECKER)
# Add marketplace
/plugin marketplace add ryanthedev/rtd-claude-inn
# Install plugin
/plugin install code-foundations@rtd
# Update to latest
/plugin update code-foundations@rtd| I want to... | Guide | See it in action |
|---|---|---|
| Fix a bug | Debugging Guide | Picker Focus Bug |
| Write new code | Writing Guide | Window Picker Plan |
| Review code | Reviewing Guide | Picker History Review |
| Plan a feature | Planning Guide | Window Picker Plan |
| Refactor code | Refactoring Guide | Tab Indicator Removal |
Ranked by how well they demonstrate the skills:
| # | Example | Type | Shows |
|---|---|---|---|
| 1 | Picker History Review ⭐ | REVIEW | Multi-skill chaining, 4 violations, 3 warnings |
| 2 | Comment Renumbering | REFACTOR | Most concise—systematic table, one change at a time |
| 3 | Critical Path Review | OPTIMIZE | Measure-first—correctly decides NOT to optimize |
| 4 | Border Cleanup | REFACTOR | CHECKER gates, McCabe complexity |
| 5 | Picker Text Overflow | DEBUG | Root cause analysis, pattern matching |
| 6 | Tab Indicator Removal | REFACTOR | Discipline recovery, systematic removal |
| 7 | Picker Focus Bug | DEBUG | Scientific debugging method |
| 8 | Window Picker Plan | PLAN | Phased plan with checkpoints |
Based on Code Complete, 2nd Edition by Steve McConnell.
Task Guides
Case Studies
- Picker History Review ⭐
- Comment Renumbering
- Critical Path Review
- Border Cleanup
- Picker Text Overflow
- Tab Indicator Removal
- Picker Focus Bug
- Window Picker Plan
Reference