All authors
Claude Skills by rizukirr
github.com/rizukirr11 skills0 installs0 views
- BrainstormUse before any creative or implementation work: features, components, behavior changes. Hard gate, no code before an approved design.Votes: 0GitHub stars: 20
- DebugUse when a check fails: a red test, a broken build, a failed clause, or a bug you can point at. Finds a root cause and gets it refuted before anything is fixed. Diagnosis is the product. This skill never edits.Votes: 0GitHub stars: 20
- ExecUse when a plan is approved and implementation has not started: dispatches one fresh subagent per task, runs each task's verify clause, and routes failures back instead of repairing them. One task, one commit.Votes: 0GitHub stars: 20
- LazyUse at the start of any coding work: writing, adding, refactoring, fixing, designing. The laziness ladder, stdlib and native features before new code, one line before fifty. Stays on after.Votes: 0GitHub stars: 20
- PlainUse before writing any text, in chat or into a file. Thirteen rules that hold in every string you emit, including code comments, commit messages, PR bodies and docs. No em dash, no semicolon, no hard wrapping inside a paragraph, no curly quotes, no decorative emoji, no title case in headings, no bold label lists, no heading echo, no fragment runs, no padded triads, no rejected straw options, no unraised objections, no writing about the previous version. Stays on after.Votes: 0GitHub stars: 20
- PlanUse when a spec is approved and implementation has not started: turns it into a task-by-task plan with exact paths and checkable verification. No code here.Votes: 0GitHub stars: 20
- QuickUse when the user types /vibekit:quick: writes the change immediately under lazy's ladder, no spec, no plan, no subagents. Reports what it skipped.Votes: 0GitHub stars: 20
- TerseUse at the start of every session. Compress narration, never artifacts. Questions, evidence, specs, plans and warnings stay verbatim. Stays on after.Votes: 0GitHub stars: 20
- Using VibekitUse when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.Votes: 0GitHub stars: 20
- VerifyUse before claiming a change is done, fixed or passing: checks the whole change against its spec, runs the checks no single task could, hunts for the bugs the change produced, and returns ready or not ready. Evidence or it did not happen.Votes: 0GitHub stars: 20
- VibeRun a short intent through the pipeline. Invoked as /vibekit:vibe. Hands off to brainstorm and does nothing else.Votes: 0GitHub stars: 20