NeVibe · 17
Skills and MCP tagged “engineering”
improve-codebase-architectureskill This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review.
tddskill Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details.
setup-matt-pocock-skillsskill Sets up a repository for Matt Pocock engineering skills with issue tracking, triage labels, and domain-document rules. Run it before using the other engineering skills.
triageskill This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue.
prototypeskill Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase.
domain-modelingskill This skill sharpens project terminology, maintains GLOSSARY.md, and records selected architecture decisions in ADRs. Use it while the domain model is changing.
codebase-designskill This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write.
diagnosing-bugsskill This skill guides an agent through reproducible diagnosis of hard bugs and performance regressions. Use it when code fails, produces wrong results, or becomes slow.
code-reviewskill Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress.
implementskill Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine.
ask-mattskill Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug.
wayfinderskill Maps large, uncertain work as decision tickets in an issue tracker. Use it when the route to a goal needs more than one agent session to clarify.
to-specskill Turns the current conversation and repository context into a spec, then publishes it to the project issue tracker. Use it when a feature discussion is ready to hand off to an agent.
researchskill Researches a question through primary sources and saves the findings as a Markdown file in the repository. Use it for API facts, documentation checks, and delegated reading.
to-ticketsskill Turns a plan, spec, or conversation into linked tickets with blocking dependencies. Use it when work needs to be handed to agents or published to a tracker.
wizardskill This skill creates an interactive bash wizard for manual setup steps, CI secrets, third-party dashboards, and one-off migrations.
implement-specskill Implements a prepared spec from its ticket graph on one integration branch, using parallel subagents. Use it when tickets have blocking dependencies.
