mkdevelopment

Solid

Use when implementing features or writing code. TDD enforcement is opt-in via --tdd / MEOWKIT_TDD=1. Provides code patterns, skill loading, and coding standards.

AI & Automation 15 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
78
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Development Toolkit Reference guides for implementation: code patterns, TDD enforcement (opt-in), and skill lazy-loading. ## When to Use - During Phase 3 (Build) for implementation guidance - When the `developer` agent needs coding pattern references - For TDD enforcement rules during red/green/refactor cycle (TDD mode only) ## Workflow Integration Operates 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`. ## References | Reference | When to load | Content | |-----------|-------------|---------| | **[code-patterns.md](./references/code-patterns.md)** | During implementation | Coding patterns, architecture patterns, file organization | | **[tdd-enforcement.md](./references/tdd-enforcement.md)** | Phase 2-3 | RED/GREEN/REFACTOR cycle, test-first rules, coverage requirements | | **[skill-loader.md](./references/skill-loader.md)** | Skill activation | How to load skills on-demand, lazy loading patterns | ## Gotchas - **TDD enforcement blocking exploratory prototyping**: Strict red-green cycle slows rapid iteration → Default mode (TDD off) is now the right choice for prototypes; opt into `--tdd` only when shipping production-quality work - **200-line file rule on generated code**: Auto-generated files (migrations, schemas) exceed limit by design → ...

Details

Author
ngocsangyem
Repository
ngocsangyem/MeowKit
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

cf-tdd

Use when writing new production code, adding features, implementing changes, or refactoring existing code — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "clean up this code", "extract into a module", "simplify this function", "scaffold", "write a test", "add tests", "create a component", "implement the API", "add a route", "write a service", "create the handler". Also auto-invoke when the conversation transitions from planning/discussion to actual code writing — any time production code is about to be written, this skill MUST be loaded first. By default uses direct implementation (no new tests written). TDD is enabled when `--add-tests` is present or config `tdd: true`. This is the gate for all code writing in the project. Do NOT auto-invoke for documentation-only changes, config edits, non-code file updates, or when the user is only asking questions about code without requesting changes.

3 Updated today
dinhanhthi
Testing & QA Solid

tdd

Use when writing production code that needs tests - new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR cycle before any implementation.

22 Updated 2 days ago
fusengine
Code & Development Listed

tdd

Use when the plan-review verdict is PROCEED (or plan-review is disabled) and code has not yet been written. Writes RED tests first, defining the contract Builder must satisfy. The mandatory hop before any implementation.

4 Updated today
mickeyyaya