-
Notifications
You must be signed in to change notification settings - Fork 21
All Skills
rtd edited this page Jan 12, 2026
·
1 revision
| Skill | Purpose | When to Use |
|---|---|---|
| code-foundations | Master dispatcher - classifies task and routes to appropriate skill | Always start here |
| Skill | Purpose | When to Use |
|---|---|---|
| cc-developer-character | Mindset check - "understand before acting" | Before DEBUG, WRITE, REFACTOR tasks |
| cc-construction-prerequisites | Requirements, planning, phased design | Before writing new features |
| Skill | Purpose | When to Use |
|---|---|---|
| cc-pseudocode-programming | Design routines with pseudocode first | When writing new functions |
| cc-routine-and-class-design | High-quality interfaces, LSP checks | When designing classes/APIs |
| cc-control-flow-quality | Clean control structures, reduce nesting | When logic gets complex |
| cc-data-organization | Variables, naming, types, magic numbers | When working with data |
| Skill | Purpose | When to Use |
|---|---|---|
| cc-quality-practices | Reviews, testing, Scientific Debugging | DEBUG tasks, code review |
| cc-defensive-programming | Error handling, input validation | When handling errors/inputs |
| cc-code-layout-and-style | Formatting, self-documenting code | When cleaning up code |
| Skill | Purpose | When to Use |
|---|---|---|
| cc-refactoring-guidance | Safe refactoring strategies | REFACTOR tasks |
| cc-integration-practices | Integration, builds, daily builds | When integrating components |
| cc-performance-tuning | Measure-first optimization | OPTIMIZE tasks |
Skills invoke other skills as needed:
code-foundations (dispatcher)
│
├── DEBUG → cc-developer-character → cc-quality-practices
│
├── WRITE → cc-developer-character → cc-construction-prerequisites
│ → cc-pseudocode-programming
│
├── REVIEW → cc-quality-practices (CHECKER mode)
│
├── REFACTOR → cc-developer-character → cc-refactoring-guidance
│
└── OPTIMIZE → cc-performance-tuning
Most skills have two modes:
| Mode | Purpose | Output |
|---|---|---|
| CHECKER | Audit existing code against checklists | Table with PASS/WARNING/VIOLATION |
| APPLIER | Guide new implementation | Recommendations, patterns, designs |
Example:
-
cc-routine-and-class-designCHECKER → "Your class has 12 parameters (VIOLATION)" -
cc-routine-and-class-designAPPLIER → "Use Parameter Object pattern to reduce parameters"
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