Claude Skills by Ze-Norm

github.com/Ze-Norm

20 skillsA× 200 installs1 views

Code ReviewAReview a delivery run's committed change from its base commit along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match the governing spec and tickets?). Runs both reviews in parallel sub-agents and reports them side by side.developmentgotestingVotes: 0GitHub stars: 2
Domain ModelingABuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.developmentVotes: 0GitHub stars: 2
Grill MeAA relentless interview to sharpen a plan or design.developmentVotes: 0GitHub stars: 2
Grill With DocsAA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.developmentgoVotes: 0GitHub stars: 2
GrillingAGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.developmentgoapiVotes: 0GitHub stars: 2
HandoffACompact the current conversation into a handoff document for another agent to pick up.developmentapiVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
High Fidelity DemoABuild a high-fidelity demo of a prototype the user already picked, with simulated functionality, so they can confirm the approach before a spec and tickets. Use when a direction is chosen and the user wants to click through it, or says "build the demo", "high-fidelity demo", "demo it", or "final checkpoint before the spec".developmentgobashVotes: 0GitHub stars: 2
Implement SpecAImplement a specification's ticket set in code, in the run worktree ZeNorm created for a delivery run.developmentgoshellVotes: 0GitHub stars: 2
ImplementAImplement a piece of work based on a spec or set of tickets.developmentgonodeVotes: 0GitHub stars: 2
Planning ReviewAIndependently review a spec against the resolutions of its map (spec review), or a ticket breakdown against its spec (tickets review), before the next step starts. Traces every element to its source and reports contradictions, invented scope, undefined terms, dropped resolutions and uncovered clauses. Use when a spec or a ticket breakdown needs checking by someone other than the agent that wrote it.developmentgotestingVotes: 0GitHub stars: 2
PrAWrite the body of the pull request for one passed delivery run: Why, What, Tests and Risks, short enough to read in a minute, from the run's diff, spec, tickets, implementer reports, checks and verdict, in the project's own terms.developmentgoexpressVotes: 0GitHub stars: 2
Product Planning ReviewAZeNorm's product planning review: the spec review (independently check one spec revision against its map's destination and resolved waypoints before To Tickets starts) and the tickets review (independently check one ticket set version against its approved revision and the code before approval). Read by the planning agent's review runs by absolute path; not for work on ZeNorm's own repository (that is skills/planning-review).developmentgotestingVotes: 0GitHub stars: 2
Product To SpecAZeNorm's product To Spec: write a cleared map's specs, or repair one spec after a failed planning review, a rejection or the person's note, from the map's destination and resolved waypoints. Read by the planning agent's To Spec runs by absolute path; not for work on ZeNorm's own repository (that is skills/to-spec).developmentrustgoVotes: 0GitHub stars: 2
Product To TicketsAZeNorm's product To Tickets: break an approved spec revision into tracer-bullet tickets with blocking edges and a disposition for every criterion. Read by the planning agent's To Tickets runs by absolute path; not for work on ZeNorm's own repository (that is skills/to-tickets).developmentgosqlVotes: 0GitHub stars: 2
PrototypeABuild 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.developmentpythongoVotes: 0GitHub stars: 2
ResearchAInvestigate a question against high-trust primary sources and publish a linked report with cited findings and limitations. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.developmentrustapiVotes: 0GitHub stars: 2
Scope SpecsAChoose and preserve specification boundaries for a cleared Wayfinder map before synthesis. Use when handing off a cleared map, deciding whether it needs one or several specs, or revising its specification scopes. Compose with to-spec when synthesis is requested.developmentgotestingVotes: 0GitHub stars: 2
To SpecATurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.developmentgotestingVotes: 0GitHub stars: 2
To TicketsABreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).developmentgoshellVotes: 0GitHub stars: 2
WayfinderAPlan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.developmentgotestingVotes: 0GitHub stars: 2