Claude Skills by Drizzy07x

Creates implementation plans with interfaces, tests, and open decisions. Use when a multi-step change needs planning.

Automates web and desktop UIs while capturing evidence that separates navigation from verified behavior. Use when a task requires site navigation, browser reproduction, or native app operation. For one existing framework-free HTML page, use design-ui instead.

Explores user intent, requirements, and design before implementation. Use when starting a new feature, component, or behavior change whose requirements or design are not yet agreed; skip for trivial single-file changes the user has already specified.

Controls report length while preserving evidence and explains external sources without overstating them. Use when a user requests concise handoffs, set verbosity, or plain-language explanations of dense material.

Builds accessible interfaces and verifies renders. Use when creating or redesigning a page, dashboard, or static HTML file.

Finds root causes through reproduction and falsifiable experiments. Use when a failure, flaky behavior, or regression lacks a demonstrated cause.

Dispatches one subagent per independent problem. Use when two or more investigations or fixes can proceed concurrently without shared state or sequential dependencies.

Builds or audits testable prompt contracts with explicit outcomes, permissions, tools, evidence, and stop conditions. Use when writing reusable agent prompts, system prompts, or prompts with unclear success criteria.

Runs long or interruption-prone work from a durable state file with falsifiable criteria and evidence. Use when work spans turns, risks compaction, or must resume after interruption.

Executes a written implementation plan inline, task by task, stopping only on blockers. Use when a plan exists and subagent dispatch is unavailable, or the user wants the plan executed in a separate session.

Guides integration of a finished branch: verify tests, present merge/PR/keep/discard options to the user, and clean up worktrees. Use when implementation is complete, all tests pass, and the work needs to be integrated.

Handles unavailable named capabilities and destructive filesystem roots. Use when a required tool, command, picker, dialog, gate, or form may be unavailable; apply before acting even if the prompt asks to assume consent.

Audits and safely updates scoped AGENTS.md and CLAUDE.md guidance for Claude Code and Codex. Use for persistent instruction audits, change plans, authorized repairs, or verification of global, project, and nested instruction chains.

Verifies code review feedback before implementation and pushes back with evidence when a claim is wrong. Use when feedback is unclear, risky, or technically questionable.

Refactors working or legacy code without changing observable behavior, using characterization tests when needed. Use when code is messy, nested, duplicated, or uncovered.

Dispatches a bounded reviewer and preserves verified findings. Use when completed work needs read-only review before merge.

Runs source-bound research and version-matched documentation lookup. Use when comparisons, experiments, benchmarks, investigations, or external library, SDK, CLI, and API facts must be verified.

Audits the current ChatGPT, Claude Code, or Codex host for conflicting skills, plugins, and persistent hooks, then offers reversible per-item repairs. Use when skills duplicate, shadow, double-fire, load at the wrong time, or when the user asks to doctor or clean up Skillquiver conflicts.

Routes multi-module work with progressive discovery, matched effort, and context economy. Use when boundaries are unclear, context must stay small, or a durable project map is needed.

Executes an implementation plan by dispatching one subagent per task with per-task review gates, keeping the orchestrator's context small. Use when executing plans with independent tasks in the current session.

Runs a recorded red-green-refactor cycle. Use when implementing a feature, bug fix, or behavior change.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs; requires running verification commands and confirming output before making any success claims. Do not load at task start or separately when design-ui's bounded static-page capture applies.

Independently audits finished work — verifies a delivery or completion claim against real evidence. Use when asked to double-check that something just finished actually works, confirm a completion claim, judge release readiness, or find unsupported claims.

Creates implementation plans with interfaces, tests, and open decisions. Use when a multi-step change needs planning.