Software Development AI agent skills

13,359 skills in the archive. Read a skill’s instructions or open its original repository.

• Plannotator

  by @backnotprop

  Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided…

• Plannotator Review

  by @backnotprop

  Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.

• Plannotator Review

  by @backnotprop

  Open Plannotator's browser-based code review UI and address the returned feedback.

• Worktrunk

  by @max-sixty

  Guidance for Worktrunk (the `wt` CLI) — git worktree management, hooks, and config. Load when working out which worktree a `wt` command will act on, or reaching for the global `-C <path>` to target one; editing .config/wt.toml…

• Running Tend

  by @max-sixty

  Worktrunk-specific guidance for tend CI workflows. Adds codecov polling, Rust test commands, labels, and review criteria on top of the bundled tend-ci-runner skills. Use when operating in CI.

• Wt Switch Create

  by @max-sixty

  Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it. Use when launching a session that should work in its own worktree.

• Release

  by @max-sixty

  Worktrunk release workflow. Use when user asks to "do a release", "release a new version", "cut a release", or wants to publish a new version to crates.io and GitHub.

• Writing User Outputs

  by @max-sixty

  CLI output formatting standards for worktrunk. Load before editing any code that calls warning_message, hint_message, error_message, info_message, eprintln, or println, or that produces strings the user will see (CLI help,…

• Material Component Dev

  by @bytedance

  FlowGram 物料组件开发指南 - 用于在 form-materials 包中创建新的物料组件

• Ccpm

  by @automazeio

  CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this…

• Shadcn Ui

  by @google-labs-code

  Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

• Stitch::Manage Design System

  by @google-labs-code

  Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.

• Stitch::Upload To Stitch

  by @google-labs-code

  Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool…

• React Vite Dashboard

  by @google-labs-code

  Convert Stitch designs into production React + Vite dashboards with TanStack Query, accessible tokens from DESIGN.md, and Web3-ready patterns (ethers/viem).

• Templates

  by @vudovn

  Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 13 templates for various tech stacks.

• Nextjs React Expert

  by @vudovn

  React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing…

• Lint And Validate

  by @vudovn

  Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.

• Performance Profiling

  by @vudovn

  Performance profiling principles. Measurement, analysis, and optimization techniques.

• Brainstorming

  by @vudovn

  Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

• I18n Localization

  by @vudovn

  Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

• Webapp Testing

  by @vudovn

  Web application testing principles. E2E, Playwright, deep audit strategies.

• Rust Pro

  by @vudovn

  Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for…

• Code Review Graph

  by @vudovn

  Token-efficient code review using Tree-sitter AST graphs and MCP. Cuts AI token usage on large codebases by computing the blast radius of changes instead of reading entire codebases. Uses a SQLite graph database for structural…

• Coordinator Mode

  by @vudovn

  Advanced multi-agent orchestration with parallel workers, synthesis protocols, and coordinator lifecycle. Use when complex tasks require multiple agents working in parallel with intelligent result synthesis.

• Memory System

  by @vudovn

  Persistent cross-session memory management. Enables agents to remember user preferences, project conventions, and past decisions across different sessions using a structured MEMORY.md index and topic files.

• Verify Changes

  by @vudovn

  Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.

• Intelligent Routing

  by @vudovn

  Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

• Batch Operations

  by @vudovn

  Apply operations across multiple files simultaneously. Pattern-based bulk modifications, search-and-replace across codebases, consistent changes to many files at once.

• Simplify Code

  by @vudovn

  Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.

• Deployment Procedures

  by @vudovn

  Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

• Python Patterns

  by @vudovn

  Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

• Nodejs Best Practices

  by @vudovn

  Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

• Systematic Debugging

  by @vudovn

  4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

• Bash Linux

  by @vudovn

  Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

• Tailwind Patterns

  by @vudovn

  Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

• Pc Games

  by @vudovn

  PC and console game development principles. Engine selection, platform features, optimization strategies.

• Clean Code

  by @vudovn

  Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

• Multiplayer

  by @vudovn

  Multiplayer game development principles. Architecture, networking, synchronization.

• Mobile Games

  by @vudovn

  Mobile game development principles. Touch input, battery, performance, app stores.

• Game Design

  by @vudovn

  Game design principles. GDD structure, balancing, player psychology, progression.

• Code Review Checklist

  by @vudovn

  Code review guidelines covering code quality, security, and best practices.

• Tdd Workflow

  by @vudovn

  Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

• 3d Games

  by @vudovn

  3D game development principles. Rendering, shaders, physics, cameras.

• Systematic Debugging

  by @jnMetaCode

  遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行

• Brainstorming

  by @jnMetaCode

  在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能或修改行为。在实现之前先探索用户意图、需求和设计。

• Using Superpowers

  by @jnMetaCode

  在开始任何对话时使用——确立如何查找和使用技能，要求在任何响应（包括澄清性问题）之前调用 Skill 工具

• Writing Skills

  by @jnMetaCode

  当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用

• Requesting Code Review

  by @jnMetaCode

  完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求

• Writing Plans

  by @jnMetaCode

  当你有规格说明或需求用于多步骤任务时使用，在动手写代码之前

• Test Driven Development

  by @jnMetaCode

  在实现任何功能或修复 bug 时使用，在编写实现代码之前

• Chinese Commit Conventions

  by @jnMetaCode

  中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。

• Workflow Runner

  by @jnMetaCode

  在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key，使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。

• Chinese Git Workflow

  by @jnMetaCode

  国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。

• Chinese Code Review

  by @jnMetaCode

  中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。

• Chinese Documentation

  by @jnMetaCode

  中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。

• Mcp Builder

  by @jnMetaCode

  在构建 MCP 服务器或 MCP 工具时使用 —— 系统化的生产级 MCP 构建方法论，覆盖工具设计、错误处理、传输层选择与测试，让 AI 助手连接外部能力

• Using Git Worktrees

  by @jnMetaCode

  当需要开始与当前工作区隔离的功能开发，或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在

• Verification Before Completion

  by @jnMetaCode

  在宣称工作完成、已修复或测试通过之前使用，在提交或创建 PR 之前——必须运行验证命令并确认输出后才能声称成功；始终用证据支撑断言

• Executing Plans

  by @jnMetaCode

  当你有一份书面实现计划需要在单独的会话中执行，并设有审查检查点时使用

• Dispatching Parallel Agents

  by @jnMetaCode

  当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用

• Finishing A Development Branch

  by @jnMetaCode

  当实现完成、所有测试通过、需要决定如何集成这份工作时使用

• Orchestrate

  by @cursor

  Use only when the user explicitly types `/orchestrate <goal>` to decompose a large task, spawn a tree of parallel cloud-agent workers/subplanners/verifiers via the Cursor SDK, and collect structured handoffs; do not invoke…

• Poteto Mode

  by @cursor

  poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

• Cursor Sdk

  by @cursor

  Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor TypeScript SDK (`@cursor/sdk`). Use this skill whenever the user mentions integrating, installing, or writing code against the Cursor SDK;…

• Interrogate

  by @cursor

  Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

• Architect

  by @cursor

  Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the…

• Reproduce And Fix Issues

  by @cursor

  Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.

• How

  by @cursor

  Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem…

• Create Verification Skill

  by @cursor

  Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no…

• Advisor

  by @cursor

  Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an error, and before declaring a task done. Use when the user types /advisor, asks to turn the advisor on or off,…

• Triage Issue Reports

  by @cursor

  Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

• Add Voice

  by @cursor

  Use when the user runs /add-voice, types Voice Mode, or asks to add Grok realtime voice to an app, including replacing an STT-LLM-TTS cascade or OpenAI Realtime. Wire speech-to-speech, safe auth, and app mic. Composer: waveform…

• Debug Voice

  by @cursor

  Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture what happened in a Grok realtime voice session, or a voice integration has no debug logging yet. Proposes a plan, then installs a dev-only…

• Docs Canvas

  by @cursor

  Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for…

• Figure It Out

  by @cursor

  Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via…

• Cli For Agents

  by @cursor

  Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a…

• Pr Review Canvas

  by @cursor

  Render a PR diff review as a Cursor Canvas that groups changes by reviewer importance, separates boilerplate from core logic, and highlights tricky or unexpected code. Use when reviewing a pull request, summarizing a diff for…

• Automate Me

  by @cursor

  Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via…

• Blast Radius

  by @cursor

  Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or…

• Principle Build The Lever

  by @cursor

  Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool…

• Thermo Nuclear Code Quality Review

  by @cursor

  Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially…

• Arena

  by @cursor

  Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the…

• Make Pr Easy To Review

  by @cursor

  Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the…

• Control Ui

  by @cursor

  Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.

• Principle Boundary Discipline

  by @cursor

  Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

• Principle Foundational Thinking

  by @cursor

  Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

• Make Bot UI

  by @cursor

  Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

• Principle Make Operations Idempotent

  by @cursor

  Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

• Principle Exhaust The Design Space

  by @cursor

  Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

• Principle Laziness Protocol

  by @cursor

  Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

• Setup Benny

  by @cursor

  Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

• Principle Migrate Callers Then Delete Legacy Apis

  by @cursor

  Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

• Verify This

  by @cursor

  Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

• Principle Fix Root Causes

  by @cursor

  Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

• Principle Experience First

  by @cursor

  Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

• Review And Ship

  by @cursor

  Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

• Loop On Ci

  by @cursor

  Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.

• Fix Merge Conflicts

  by @cursor

  Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

• Weekly Review

  by @cursor

  Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work

• No Comments

  by @cursor

  Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.