All authors
Claude Skills by kardebadas
github.com/kardebadas10 skills2 installs17 views
- Bug FixUse when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.Votes: 0GitHub stars: 2
- Bug InvestigateUse when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing — that is superb:bug-fix.Votes: 0GitHub stars: 2
- CraftUse when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have not been decided. Not for planning, task breakdown, or writing code.Votes: 0GitHub stars: 2
- PipelineUse when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.Votes: 0GitHub stars: 2
- SetupUse when superb's skills need their dependencies installed or checked — "set up superb", "install the dependencies", "why does pipeline say superpowers is missing", after a fresh plugin install, or on a new machine. Also use when a skill fails complaining that a superpowers sub-skill cannot be found.Votes: 0GitHub stars: 2
- Agent OutputVerdict: **all ten findings are STILL OPEN.** Not one line of the two files under review changed. The fix commit `6770d01` does not touch them.Votes: 0GitHub stars: 2
- Agent OutputReviewed `git diff main..HEAD`. Everything below was executed, not reasoned about. Fixtures were built under the session scratchpad; the repo tree is unmodified. ---Votes: 0GitHub stars: 2
- Pipeline AutoUse when the user wants a substantial feature taken from idea through implementation in one run with as little interruption as possible ("just build it", "don't keep asking me"), or when controlling such a run and a worker question, quorum responses, the drift budget, a human decision, a review class or a completeness item needs a decision, especially under deadline pressure. Not for a run where the user is consulted at each decision; that is superb:pipeline.Votes: 0GitHub stars: 2
- Fast PipelineUse when the user wants a feature built quickly with low token cost and few interruptions, approves a spec once, and says no automated tests should be written because they will test it manually — "fast pipeline", "go fast, no tests, I'll test it myself", "don't keep asking me". Not for a run that should write or keep tests (superb:pipeline), nor one where a quorum replaces the human gate (superb:pipeline-auto).Votes: 0GitHub stars: 2
- Turbo PipelineUse when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one that approves plans and keeps durable run state (superb:pipeline), or one that needs resumable run files and a quorum (superb:pipeline-auto).Votes: 0GitHub stars: 2