Loading...
Loading...
Found 10,137 Skills
Extract and structure fuzzy product ideas into validated problem statements, target users, and jobs-to-be-done. Use when a user has a raw idea, concept, or solution in mind but hasn't clearly articulated the problem, target user, or assumptions. This skill helps users communicate context to coding agents more effectively, reducing iteration cycles and "that's not what I meant" moments.
Use after the final approved execution scope is complete, or when the user asks whether a feature is done, ready to ship, safe to merge, or needs a quality check. Runs the post-execution quality gate: specialist review, artifact verification, and human UAT against locked decisions and the final exit state. Use for prompts like "review this feature", "is this done?", "can we ship this?", "double-check the implementation", or "run UAT".
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.
Use when creating new skills, commands, or agent definitions for Claude Code, including writing SKILL.md files, defining triggers, and testing skill behavior
Run Codex planning via the CLI and report the planning results.
Wrap up current task — commit, update Linear, optionally create PR, route to next
Post-session retrospective: audits efficiency, proposes skill/memory/CLAUDE.md updates, and generates coaching feedback
Lossless LLM-optimized compression of source documents. Use when the user requests to 'distill documents' or 'create a distillate'.
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Fix a reported bug by first enhancing tests until the bug is reproduced, then fixing the implementation, and finally confirming the enhanced tests pass.
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.