All authors

Claude Skills by fusebase-dev
github.com/fusebase-dev56 skills0 installs78 views
- Skill AuthoringUse when the operator asks to create, update, import, analyze, or preserve a reusable skill or recurring instruction pattern. Do NOT use for one-off ticket work, ordinary code implementation, problem-catalog incidents, or copying external skill text verbatim.Votes: 0GitHub stars: 9
- Smoke TestingUse when Product Owner defines smoke prompts or deploy handoffs, and when AI Developer / Deploy phase executes post-deploy smoke. Do NOT use for pre-deploy unit/integration/source gates alone; smoke means proving the operator-visible outcome on the deployed surface with ground-truth diagnostics.Votes: 0GitHub stars: 9
- Task DelegationUse when the operator explicitly asks for delegation, subagents, parallel agents, or when an AI Developer has independent T-task slices that can safely run in parallel. ALSO load on an explicit absence/unattended instruction ("I'm stepping out", "run this unattended", "I'll be away") and route to /step-out first, even when the work is one simple edit. Do NOT use for simple edits, immediate blocking work, deploy commands, production side effects, or Product Owner code-writing; ordinary attende...Votes: 0GitHub stars: 9
- Token EconomyUse when implementing, debugging, or running long tool-using work sessions, or when the operator asks about "token waste", "session cost", "why is this so expensive", or runs "/token-waste-audit" — delivers FR-26's execution-time economy rules (scoped reads, no re-reads of unchanged in-context files, two-strike retry rule, targeted edits) with their quality guards, plus the measurement path. Do NOT use for app-decomposition token economy (product-apps-decomposition owns that), verification po...Votes: 0GitHub stars: 9
- Validation And QaUse when code changes need a gate report, operator asks "is this ready?", or a single observed failure needs reproducibility check; runs lint/typecheck/tests, smoke, probes, reproducibility-before-fix. Do NOT approve deploy (that's release-deploy-reporting).Votes: 0GitHub stars: 9
- Zoom OutUse before committing a bug fix or improvement, when a fix is non-trivial, or when the same area has been patched before. Operationalizes FR-20 — zoom out to root cause before applying a narrow patch. Do NOT use for trivial typo/format edits, for net-new feature work with no prior code (nothing to zoom out from), or as a substitute for reproduce-before-fix (FR-10 / validation-and-qa).Votes: 0GitHub stars: 9