All authors
Claude Skills by ruverd
github.com/ruverd37 skills1 installs7 views
- ArchitectSketch types, signatures, and module structure before code, then stay in the loop while implementation fills it in. Use for /architect, 'design this', or non-trivial work where jumping to code would lock in the wrong shape.Votes: 0GitHub stars: 2
- Before And AfterUse when a GitHub PR needs before/after UI stills on the body, or when bulma-qa / the shipper captures those stills with agent-browser.Votes: 0GitHub stars: 2
- Blast RadiusFind what a change could break outside the diff before it ships, and prove it safe by running real code rather than writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.Votes: 0GitHub stars: 2
- Bulma BusShared bus for the bulma agent graphs (developer, qa, triage, reviewer, lstm). Use when switching graphs, writing or reading a .bulma-bus envelope, or resuming a stacked handoff between those agents.Votes: 0GitHub stars: 2
- Bulma Code ReviewAdaptive PR review via gh: one PR on the main thread, one fresh subagent per extra PR, one verdict artifact each (REQUEST_CHANGES / APPROVE / DEFER). Use when /bulma-code-review with PR URLs, numbers, or the current branch.Votes: 0GitHub stars: 2
- Bulma DeveloperGraph: deliver a ticket or a local goal via grill -> spec -> tickets -> TDD (bulma-feature-delivery), then MERGEABLE + bot_review + bulma-qa over the bus. Use when /developer, /bulma-developer, a ticket, or a QA_RESULT FAIL+PR_BUG. ASK the user only as a last resort.Votes: 0GitHub stars: 2
- Bulma FdAlias for bulma-feature-delivery. Use when /bulma-fd or $bulma-fd starts or resumes ticket, bug, or chore delivery through draft PR and green CI.Votes: 0GitHub stars: 2
- Bulma Feature DeliveryUse when delivering a ticket, bug, or chore end-to-end (implementation through draft PR with CI green) via /bulma-feature-delivery or /bulma-fd, or when resuming a run whose HANDOFF.md exists. Spine: grill -> spec -> tickets -> implement(tdd) -> review.Votes: 0GitHub stars: 2
- Bulma GoalDrive developer → CI green → QA comment+evidence across turns with schedule_wake. Use when /goal or /bulma-goal, or after a draft PR is opened and CI is still pending.Votes: 0GitHub stars: 2
- Bulma HostHost contract: maps the primitives graphs name (load_skill, spawn_worker, worktree, schedule_wake, session_model) onto this harness, with fallbacks for the optional MCP capabilities. Load when a node names a primitive or a new harness needs wiring.Votes: 0GitHub stars: 2
- Bulma LstmGraph: author-side of review. Ingest a PR, review, inline thread, or issue-comment URL, verify with receiving-code-review, patch should-fix on the same branch, and reply on every comment. Use when /lstm, /bulma-lstm, CHANGES_REQUESTED, or LSTM_REQUEST.Votes: 0GitHub stars: 2
- Bulma MemoryUse when /memory, /bulma-memory, a bulma graph or engine starts, the first run in a repo, CODEOWNERS or AGENTS.md list no reviewers, or the user states a durable preference (chat language, reviewers, project notes, open questions).Votes: 0GitHub stars: 2
- Bulma QaGraph: QA a PR. One slot (queue extras). Plan happy and user-break from the diff, then agent-browser or HTTP. Bus TRIAGE_REQUEST on product errors. Use when /qa, /bulma-qa, or a QA_REQUEST arrives.Votes: 0GitHub stars: 2
- Bulma ReviewerGraph: review a PR/branch via /bulma-code-review, classify CI/test failures, optionally bus a REVIEW_RESULT. Use when /reviewer, /bulma-reviewer, or a REVIEW_REQUEST envelope arrives.Votes: 0GitHub stars: 2
- Bulma TriageGraph: investigate a QA failure, classify PR_BUG / EXISTING_BUG / NEW_BUG / NOT_A_BUG / BLOCKED, route via the bus. Use when /bulma-triage, or a TRIAGE_REQUEST envelope arrives.Votes: 0GitHub stars: 2
- BulmaJev-gated router and overlay for bulma graphs. Use when /bulma.Votes: 0GitHub stars: 2
- DiagnoseDisciplined diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose this" or "debug this", reports a bug, says something is broken or failing, or describes a performance regression.Votes: 0GitHub stars: 2
- Figure It OutDesign an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Use for /figure-it-out or 'figure it out'.Votes: 0GitHub stars: 2
- Grill MeInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".Votes: 0GitHub stars: 2
- Grill With DocsGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline. Use when the user wants to stress-test a plan against the project's documented decisions.Votes: 0GitHub stars: 2
- HowUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this"). Explains subsystem architecture and runtime flow. Use why for motivation.Votes: 0GitHub stars: 2
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 2
- No CommentsSpawn a comment auditor over the diff, fix the findings you accept, and offer to encode any constraint a comment only claims. Use for /no-comments, or when a review flags comment noise or stale comments.Votes: 0GitHub stars: 2
- Principle Fix Root CausesApply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.Votes: 0GitHub stars: 2
- Principle Prove It WorksApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'Votes: 0GitHub stars: 2
- Principle Redesign From First PrinciplesApply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.Votes: 0GitHub stars: 2
- Principle Sequence Verifiable UnitsApply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, and check each before starting the next.Votes: 0GitHub stars: 2
- Receiving Code ReviewUse when receiving code review feedback, before implementing any suggestion, especially when the feedback is unclear or technically questionable. Verify before agreeing; no performative agreement, no blind implementation.Votes: 0GitHub stars: 2
- Show Me Your WorkKeep a reviewable decision trail for unattended or long-running work: a TSV log with one row per decision (what, why, evidence, result). Use for /show-me-your-work, autonomous runs, or work a human reviews after stepping away.Votes: 0GitHub stars: 2
- TddUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.Votes: 0GitHub stars: 2
- Technical WritingLayered technical-writing standard: Diataxis structure, Google developer style, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, or PR descriptions.Votes: 0GitHub stars: 2
- Thermo Nuclear Code Quality ReviewRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear or thermonuclear code quality review, or a deep maintainability audit.Votes: 0GitHub stars: 2
- To IssuesBreak a plan, spec, or PRD into independently-grabbable issues on the project tracker using tracer-bullet vertical slices. Use when the user wants to turn a plan into issues or implementation tickets.Votes: 0GitHub stars: 2
- To PrdTurn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.Votes: 0GitHub stars: 2
- Typescript Best PracticesTypeScript best practices. Use when reading or editing any .ts or .tsx file.Votes: 0GitHub stars: 2
- UnslopCut AI tells from any writing. Must always apply.Votes: 0GitHub stars: 2
- WhyUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Queries every available evidence MCP in parallel and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.Votes: 0GitHub stars: 2