| name | ksb-framework |
| version | 1.0.1 |
| compliance-level | gold |
| categories | ["decision-framework","infrastructure","learning"] |
| description | Auto-apply Knowledge-Skills-Behaviors framework to guide Claude's reasoning |
| user-invocable | true |
| context | inject |
| triggers | ["/ksb","ksb","apply ksb","use framework","review with ksb","ksb check","growth protocol"] |
| adjacencies | [{"target":"smart-goal","when":"planning","weight":0.8,"action":"Plan learning"},{"target":"lexicon-builder","when":"execution","weight":0.7,"action":"Build domain lexicon"}] |
KSB Framework Skill
Systematically apply the Knowledge-Skills-Behaviors framework to ensure Claude operates at peak effectiveness.
Quick Reference
Before Starting Work
┌─────────────────────────────────────────────────────────────┐
│ 1. SCOPE HAMMER: What's the minimum viable solution? │
│ 2. BUILD VS WRAP: Should I use a library? │
│ 3. DOMAIN VALUE CHECK: Existing constants to use? │
│ 4. CORNELIUS CHECK: Foundation or Leaf code? │
└─────────────────────────────────────────────────────────────┘
While Working
┌─────────────────────────────────────────────────────────────┐
│ 1. PROFESSIONAL OBJECTIVITY: Be direct, not sycophantic │
│ 2. SOCRATIC EXPLORATION: Ask when unclear │
│ 3. KISS: Keep it simple │
│ 4. FIRST PRINCIPLES: Challenge assumptions │
└─────────────────────────────────────────────────────────────┘
When Writing Code
┌─────────────────────────────────────────────────────────────┐
│ PATTERNS TO APPLY: │
│ • Guard Clauses: Exit early for failures │
│ • Error Handling: Catch specific, preserve context │
│ • Public API: Expose through __init__.py │
│ • UACA: Respect L1-L5 hierarchy │
│ │
│ ANTI-PATTERNS TO AVOID: │
│ • Magic Numbers: Use named constants │
│ • Premature Abstraction: Rule of Three │
│ • God Objects: Single responsibility │
└─────────────────────────────────────────────────────────────┘
When Testing
┌─────────────────────────────────────────────────────────────┐
│ • AAA: Arrange-Act-Assert structure │
│ • Test-First Debugging: Write failing test before fix │
│ • Property Testing: For pure functions with invariants │
└─────────────────────────────────────────────────────────────┘
When Reviewing
┌─────────────────────────────────────────────────────────────┐
│ CORNELIUS ROBINSON LENS: │
│ 1. Foundation or Leaf? │
│ 2. If Foundation: Robust? Documented? Tested? Decoupled? │
│ 3. Trapped potential hiding inside? │
│ 4. Enable or Constrain future development? │
└─────────────────────────────────────────────────────────────┘
After Completing
┌─────────────────────────────────────────────────────────────┐
│ SUCCESS? → PATTERN EXTRACTION │
│ • What worked well? │
│ • Can this be abstracted? │
│ • Create new KSB unit? │
│ │
│ FAILURE? → PAIN BUTTON │
│ • Acknowledge the pain │
│ • 5 Whys to root cause │
│ • Knowledge, Skill, or Behavior gap? │
│ • Create preventive KSB unit │
└─────────────────────────────────────────────────────────────┘
