C
Create Skill (TDD Method)
TDD methodology for skill creation — test with subagents first, write skill to address failures, iterate until bulletproof against rationalization
ByNeoLabHQ
WhatIsIt
What is this? Core principle in 1-2 sentences.
HowToUse
digraph when_flowchart {
"Need to show information?" [shape=diamond];
"Decision where I might go wrong?" [shape=diamond];
"Use markdown" [shape=box];
"Small inline flowchart" [shape=box];
"Need to show information?" -> "Decision where I might go wrong?" [label="yes"];
"Decision where I might go wrong?" -> "Small inline flowchart" [label="yes"];
"Decision where I might go wrong?" -> "Use markdown" [label="no"];
}
Use flowcharts ONLY for:
- Non-obvious decision points
- Process loops where you might stop too early
- "When to use A vs B" decisions
Never use flowcharts for:
- Reference material → Tables, lists
- Code examples → Markdown blocks
- Linear instructions → Numbered lists
- Labels without semantic meaning (step1, helper2)
See graphviz-conventions.dot for graphviz style rules.
KeyFeatures
- TDD methodology for skill creation — test with subagents first, write skill to address failures, iterate until bulletproof against rationalization
- Automated documentation generation
- Seamless integration with Claude's development workflow