Build tracked, runnable pattern codebases from recurring engineering lessons.
npx skills add https://github.com/nmnmcc/skills --skill pattern-nmnmcc
Please help me install this Agent Skill. Skill: pattern Source: https://github.com/nmnmcc/skills/tree/main/skills/pattern Command: npx skills add https://github.com/nmnmcc/skills --skill pattern-nmnmcc
This Skill helps you capture a recurring engineering lesson as a standalone, runnable codebase so it can be taught, tested, and reused instead of remaining an informal rule or one-off example.
patterns/<pattern-name>/ codebase with implementation, tests, fixtures, and learner-facing documentation.Use the pattern skill to turn a recurring engineering lesson into a tracked, standalone codebase under patterns/<pattern-name>/.
High-intent search queries and answers about installing and using this skill.
You capture recurring engineering lessons by distilling them into situation, tensions, response, consequences, and boundary, then organizing them into a tracked patterns/<pattern-name>/ directory with implementation, tests, fixtures, and learner-facing documentation.
A runnable pattern codebase is a standalone project under patterns/<pattern-name>/ that contains a reference implementation, guided experiment, verified commands, and learner-facing documentation to make engineering lessons transferable and reproducible.
Managing engineering pattern lifecycles involves creating, applying, revising, splitting, merging, and retiring patterns as evidence changes, ensuring existing pattern directories stay accurate and verified over time.
Yes, you can maintain existing pattern directories by revising, splitting, merging, or retiring patterns as evidence changes, keeping the reference implementation, verified commands, and tests up to date.
The best way to document engineering patterns for teaching is to structure them as standalone codebases with learner-facing documentation, guided experiments, and verified commands that others can run and reproduce directly.
Yes, each engineering pattern requires a standalone patterns/<pattern-name>/ codebase containing its own reference implementation, tests, fixtures, and documentation to ensure it is independently runnable and verifiable.
hbvg234Extract actionable lessons from git fix commits by analyzing diffs and patterns.
babywormGuide users through RTL Agent Team initialization and 6-Phase pipeline workflows.
anavvanzinTranslate complex engineering concepts into developer-facing documentation.
Hamza123545Generate spec-driven Python and TypeScript code examples with tests.