All authors
Claude Skills by shaderera
github.com/shaderera35 skills0 installs46 views
- Ask MattAsk which skill or flow fits your situation. A router over the skills in this repo.Votes: 0GitHub stars: 3
- Code ReviewReview 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 issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".Votes: 0GitHub stars: 3
- Codebase DesignShared 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.Votes: 0GitHub stars: 3
- Diagnosing BugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Votes: 0GitHub stars: 3
- Domain ModelingBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.Votes: 0GitHub stars: 3
- Grill MeA relentless interview to sharpen a plan or design.Votes: 0GitHub stars: 3
- Grill With DocsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.Votes: 0GitHub stars: 3
- GrillingGrill 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.Votes: 0GitHub stars: 3
- HandoffCompact the current conversation into a handoff document for another agent to pick up.Votes: 0GitHub stars: 3
- Implement SpecImplement the result of /to-spec and /to-tickets in code.Votes: 0GitHub stars: 3
- ImplementImplement a piece of work based on a spec or set of tickets.Votes: 0GitHub stars: 3
- Improve Codebase ArchitectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Votes: 0GitHub stars: 3
- Ponytail AuditQuality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.Votes: 0GitHub stars: 3
- Ponytail DebtList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Votes: 0GitHub stars: 3
- Ponytail GainShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact".Votes: 0GitHub stars: 3
- Ponytail HelpQuick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".Votes: 0GitHub stars: 3
- Ponytail ReviewQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.Votes: 0GitHub stars: 3
- PonytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.Votes: 0GitHub stars: 3
- PrUse when writing a PR body.Votes: 0GitHub stars: 3
- PrototypeBuild 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.Votes: 0GitHub stars: 3
- ResearchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.Votes: 0GitHub stars: 3
- RetroConduct a retrospective on a coding session.Votes: 0GitHub stars: 3
- Setup Matt Pocock SkillsConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.Votes: 0GitHub stars: 3
- TddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Votes: 0GitHub stars: 3
- TeachTeach the user a new skill or concept, within this workspace.Votes: 0GitHub stars: 3
- To QuestionnaireTurn a decision you can't fully answer into a questionnaire for someone else to fill in.Votes: 0GitHub stars: 3
- To SpecTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.Votes: 0GitHub stars: 3
- To TicketsBreak 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).Votes: 0GitHub stars: 3
- TriageMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.Votes: 0GitHub stars: 3
- Wait WhatStop. That last message did not land: re-pitch it.Votes: 0GitHub stars: 3
- WayfinderPlan 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.Votes: 0GitHub stars: 3
- WizardGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.Votes: 0GitHub stars: 3
- Writing For AgentsWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.Votes: 0GitHub stars: 3
- Shaderera AddonsUse when the person asks for Shaderera add-ons or the catalog by name or by what they do (search, add, remove or publish an add-on), names an add-on, when adding one of the plumbing add-ons AUTHORING.md lists instead of writing the same plumbing again, or when a render or check fails because a required package add-on is missing. Do not use it to look for ready-made looks or motion while making a clip unless the person asked for that.Votes: 0GitHub stars: 3
- ShadereraUse when the person asks to make, revise, check, render or deliver a video, ad, motion graphic or animated film in code with Shaderera, or when the working directory (or a parent) has a shaderera.json. Covers starting a project, the edit, check and look loop, giving yourself eyes through MCP, and rendering and delivery. For searching, adding, removing or publishing add-ons, use the shaderera-addons skill.Votes: 0GitHub stars: 3