14 skills published by rengwu across 1 repository. Together they weigh 30 939 tokens — that is what loading all of them at once would cost you in context. 3 of them have been repackaged into other people's repositories.
14 skills 30 939 tokens total 3 copies elsewhere
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
A relentless interview to sharpen a plan or design — one question at a time until every branch of the decision tree is resolved.
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
Compact the current conversation into a handoff document so a fresh agent can continue the work.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating spec/PRD asked for?). Use when the user wants to review a branch, work-in-progress changes, or asks to "review since X".
Turn the current conversation into a spec, saved to `.plan/` — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, saved to `.plan/`.
Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.