Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mk
Provides code patterns, TDD rules (opt-in), and skill-loading guide during feature implementation. Use for Phase 2-3 development work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:developmentWhen to use
Use when implementing features or writing code. TDD opt-in via --tdd. NOT for orchestrated pipelines (see mk:cook).
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reference guides for implementation: code patterns, TDD enforcement (opt-in), and skill lazy-loading.
Reference guides for implementation: code patterns, TDD enforcement (opt-in), and skill lazy-loading.
developer agent needs coding pattern referencesOperates in Phase 2 (Test) and Phase 3 (Build). Output supports the developer and tester agents.
TDD enforcement (tdd-enforcement.md reference) is OPT-IN as of the TDD-optional migration. Default mode skips RED-phase enforcement; enable with --tdd or MEOWKIT_TDD=1.
| Reference | When to load | Content |
|---|---|---|
| code-patterns.md | During implementation | Coding patterns, architecture patterns, file organization |
| tdd-enforcement.md | Phase 2-3 | RED/GREEN/REFACTOR cycle, test-first rules, coverage requirements |
| skill-loader.md | Skill activation | How to load skills on-demand, lazy loading patterns |
--tdd only when shipping production-quality worknpx claudepluginhub ngocsangyem/meowkit --plugin mkEnforces simplicity constraints (functions ≤20 lines, files ≤200 lines), functional core patterns, and TDD workflow for maintainable code.
Guides a TDD-driven iterative feedback loop from brainstorm through plan, execute, and iterate with checkpoint guardrails. Designed for structured feature development in Claude Code.
Enforces Red-Green-Refactor TDD cycle across any language with per-language test idioms (pytest, Jest, JUnit, etc.). Loaded unconditionally at startup — no production code without a failing test first.