Skills tagged developer-tools: 164 agent skills for Claude Code, page 2 of 2
planning-and-task-breakdown — Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks.
playwright-expert — Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests.
pr-improver — Runs an autonomous review-and-fix improvement loop over the current branch's changes until a PR review comes back clean.
pr-to-video — Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix.
principle-build-the-lever — Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
project-development — This skill should be used for project-level decisions about LLM-powered systems: whether an LLM is the right primitive for the task at hand.
provision-cloud-agent — Provision an always-on cloud-hosted coding agent: pick a host platform (Railway or AWS EC2; pluggable for Fly.io, …).
reasoning-trace-optimizer — Debug and optimize AI agents by analyzing reasoning traces, context degradation, tool confusion, instruction drift, repeated task failures.
receiving-code-review — Use when receiving code review feedback, before implementing suggestions.
release-notes — Generate user-facing release notes from tickets, PRDs, or changelogs.
remotion-to-hyperframes — Port an existing Remotion (React) composition's source to HyperFrames HTML.
requesting-code-review — Use when completing tasks, implementing major features, or before merging to verify work meets requirements
review-plugin-submission — Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.
rust-engineer — Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions.
rust-review — Performs comprehensive Rust security review for safe/unsafe boundary issues, memory safety in unsafe blocks, concurrency hazards, panic-induced DoS.
sarif-parsing — Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners.
sdf — SDFormat/SDF model and world authoring, validation, and simulator handoff.
seam-craft — Render-correctness doctrine for scene-to-scene seams in HyperFrames launch videos — the prerequisites that make transitions composite correctly on the master.
second-opinion — Gets independent code reviews from Codex or Antigravity for uncommitted changes, branch diffs, and commits.
self-improvement-loops — This skill should be used when the harness, scaffold, workflow, or optimizer itself is the optimization target: recursive self-improvement (RSI) loops.
semgrep-rule-creator — Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns.
semgrep-rule-variant-creator — Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages.
setup-pstack — Configure which models pstack uses per role and at what reasoning budget.
shadcn-ui — Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization.
shipping-and-launch — Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping.
shipping-artifacts — The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping.
skill-creator — Create new skills, modify and improve existing skills, and measure skill performance.
skill-improver — Runs an autonomous review-and-fix improvement loop over a Claude Code skill until a review comes back clean, with a cross-round findings ledger.
skill-inspector — Review AI agent skills before installation using NVIDIA SkillSpector and source-aware semantic review.
skill-template — Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
slicing-code-context — Selects bounded, graph-informed source slices with Trailmark and delegates focused code analysis or patch-proposal work to a smaller subagent.
spec-driven-development — Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet.
sprint-plan — Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification.
sql-queries — Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects.
statusline-generator — Installs, configures, customizes, or troubleshoots the Claude Code statusline (cwd, model, token counts).
stitch-loop — Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
subagent-driven-development — Use when executing implementation plans with independent tasks in the current session
systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
template-skill — Replace with description of the skill and when Claude should use it.
test-driven-development — Use when implementing any feature or bugfix, before writing implementation code
test-driven-development — Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior.
test-scenarios — Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
tool-design — This skill should be used for the tool-interface layer of an agent system specifically: writing tool descriptions agents can route on.
TUI Puppeteering with tmux — Use when automating or testing TUI/CLI applications - provides isolated tmux sessions with scripts for input, output capture, and state verification
urdf — URDF robot description authoring and validation.
using-agent-skills — Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand.
using-git-worktrees — Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via.
using-superpowers — Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
vercel-cli-with-tokens — Deploy and manage projects on Vercel using token-based authentication.
vercel-react-best-practices — React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing.
web-artifacts-builder — Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS.
webapp-testing — Toolkit for interacting with and testing local web applications using Playwright.
writing-plans — Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills — Use when creating new skills, editing existing skills, or verifying skills work before deployment