kardebadas
UserPersonal skills for Codex and Claude Code, invoked as superb:*. craft turns a vague product idea into a decision-rich brief; pipeline takes a settled idea to a finished branch.
Categories
Indexed Skills (5)
craft
Use 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.
bug-fix
Use 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.
bug-investigate
Use 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.
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
setup
Use 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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.