Loading...
Loading...
Found 198 Skills
Help teams continuously improve skills, automatically identify skill optimization opportunities (such as missing essential information, format issues, version update needs, etc.), execute secure update processes (backup, modification, testing, restoration), and ensure skill quality keeps improving as the project progresses
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.
Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.
James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation. Use when analyzing requirements, epics, or user stories to generate prioritized test ideas across Structure, Function, Data, Interfaces, Platform, Operations, and Time dimensions.
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says "build it", "start building", "execute plan", "implement tasks", "ship it", or references a track ID. Do NOT use for planning (use /plan) or scaffolding (use /scaffold).
Bug-to-test pipeline: reproduce the bug as a failing test first, then fix. The regression test lives forever.
Respond to PR review comments with critical evaluation. Use when addressing code review feedback, responding to bot review comments (Gemini Code Assist, CodeRabbit, etc.), or handling PR suggestions. Fetches comments, evaluates each against project context, applies valid fixes, declines invalid suggestions with reasoning, and posts responses.
Comprehensive content review and quality assurance for PRD documents - validates link integrity, threshold consistency, BRD alignment, and identifies issues requiring manual attention
Fresh-subagent-per-task execution with two-stage review (ADR compliance + code quality). Use when an implementation plan exists with mostly independent tasks and you want quality gates between each. Use for "execute plan", "subagent", "dispatch tasks", or multi-task implementation runs. Do NOT use for single simple tasks, tightly coupled work needing shared context, or when the user wants manual review after each task.
Use when reviewing storyboard outputs at any production stage (beat breakdown, beat board, sequence board, motion prompts), providing quality assurance feedback, or identifying revision requirements for Director agent
Load this skill when the user mentions `ulw` or `ultrawork`.
Watch for the 11 known AI-coding-agent failure modes (fabrication, scope_creep, security_vulnerability, etc.) — consult this skill before edits, dependency adds, completion claims, or anything that could trip a known supervision concern. Quote the snake_case failure-mode ids verbatim when flagging risks.