Skills
98,284 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Canonical Claude Code authoring kit covering Skills, sub-agents, plugins, slash commands, hooks, memory, settings, sandboxing, headless mode, and advanced agent patterns. Use when creating Claude Code extensions or configuring Claude Code features.
Use when the user asks to build iOS screens, SwiftUI views, UIKit layouts, mobile components, or any iOS app UI. Also use when styling, redesigning, or beautifying any iOS interface. Covers iOS 26 Liquid Glass design language, hierarchy, motion, and platform-native patterns.
Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.
NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.
Build Next.js 16 apps with App Router, Server Components/Actions, Cache Components ("use cache"), and async route params. Includes proxy.ts (replaces middleware.ts) and React 19.2. Use when: building Next.js 16 projects, or troubleshooting async params (Promise types), "use cache" directives, parallel route 404s (missing default.js), or proxy.ts CORS.
Comprehensive guide for building Progressive Web Apps (PWA) with Next.js using modern 2025 approaches. Use when users need to implement PWA features in Next.js applications including installability, offline support, service workers, web app manifests, caching strategies, push notifications, or converting existing Next.js apps to PWA. Covers both native Next.js PWA support (zero dependencies, App Router) and Serwist package (advanced offline capabilities, service worker management). Also use when troubleshooting PWA issues, optimizing PWA performance, or migrating from deprecated packages like next-pwa.
Use when setting up Node 24+ built-in `node:sqlite` with the loadable `sqlite-vec` extension for vector / RAG storage in TypeScript without `better-sqlite3`, or when debugging vec0 BigInt rowids, vitest hanging on sqlite-vec, `.ts` import errors under `node:sqlite`, or "sqlite extension not loadable". Covers extension loading, vitest incompatibility (use `node --test`), tsconfig flags, and CLI shebang. Trigger on `node:sqlite`, `sqlite-vec`, vec0 / vector storage even when the user does not name better-sqlite3.
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
Use proactively when a task requires implementing, modifying, refactoring, or reviewing a product's frontend visible interface, interaction behavior, frontend state and data flow, component or style organization — no need for the user to name it. Also for testing and validation strategies for these frontend behaviors. Applies to pages, forms, lists, modals, responsiveness, styling and motion implementation, and frontend code ownership adjustments. Not for design judgments such as visual style, color scheme, typography, and design direction, nor for purely backend work, build and deployment, dependency upgrades, mechanical changes that only fix import paths, merely operating an existing website, only generating design images, or discussing this skill; not triggered when the user explicitly asks not to use it.
Build with OpenAI's stateless APIs - Chat Completions (GPT-5, GPT-4o), Embeddings, Images (DALL-E 3), Audio (Whisper + TTS), and Moderation. Includes Node.js SDK and fetch-based approaches for Cloudflare Workers. Use when: implementing chat completions with GPT-5/GPT-4o, streaming responses with SSE, using function calling/tools, creating structured outputs with JSON schemas, generating embeddings for RAG (text-embedding-3-small/large), generating images with DALL-E 3, editing images with GPT-Image-1, transcribing audio with Whisper, synthesizing speech with TTS (11 voices), moderating content (11 safety categories), or troubleshooting rate limits (429), invalid API keys (401), function calling failures, streaming parse errors, embeddings dimension mismatches, or token limit exceeded.
Guide to using the OpenDesign build script tools. Use this skill when you need to use the @opensig/open-scripts CLI to generate icons, clean SVG, build components, compile styles, or generate design tokens. Supports 5 commands: gen:icon (SVG to Vue icon components), clean:svg (SVG cleaning and optimization), build:component (Vue component library build), build:style (SCSS style compilation), gen:token (design token CSS variable generation). Use cases: (1) configuring and running build scripts, (2) writing icon/token configuration files, (3) understanding the build process and command usage
Proactively convert approved OpenSpec specs into Beads issues when the user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains an audit trail between planning and execution.
Triggers when the user says "opsx batch fix", "batch opsx-jira-fix", "opsx-jira-fix-batch", "batch OpenSpec Jira fix". Thin trigger shell: parse Jira IDs/URLs and enqueue them into goal-driven-batch with Engine opsx-jira-fix-workflow. Does not run fixes or merge. Do NOT use for a single issue (opsx-jira-fix-workflow) or a non-Jira queue (goal-driven-batch).
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca-np` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do
Specialist in generating print-only pages. Triggered by the keywords "인쇄 페이지 만들어줘", "프린트 페이지 생성", "출력 페이지". Generates refined print-only Vue components and route configuration that output content only, without layout. Uses Context7 MCP to reference the latest TailwindCSS v4/Vue docs and Sequential Thinking to analyze print design.
Use when optimizing, auditing, or preparing to ship web animations or rendering performance work: frame loops, scroll/viewport reveals, mount/unmount transitions, canvas/WebGL lifecycles, reduced motion, lazy rendering, and deferred off-screen work. Use for jank, per-frame allocations, forced reflows, render loops, animations that do not pause off-screen, content-visibility, requestIdleCallback, analyzing Chrome DevTools performance traces for animation or rendering issues, or choosing between browser-driven CSS/WAAPI, minimal JS, phase, and Motion/GSAP. Use when the user explicitly asks about phase APIs or behavior. Do not use during exploratory animation ideation, prototyping, visual iteration, or trying variants, even when the code already imports phase; wait until the user asks for performance guidance, an audit, production implementation, ship-readiness review, or about phase itself.
How to write, test, and deploy an app with Prisma Composer (`@prisma/composer`): declare services with `compute()` and typed dependencies, define RPC contracts, compose Modules, declare the service input (config and secrets as one schema, read back with `input()`), compose the ready-made cron/storage/streams Modules, provision a raw S3-compatible object-store bucket with `bucket()`, find extensions (npm packages named `prisma-composer-*`), test with `mockService`/`bootstrapService`, run the whole app locally with `prisma-composer dev` and tail its logs with `prisma-composer log`, and deploy with `prisma-composer deploy` (stages, destroy). Use when building a Prisma App, wiring a service dependency, adding a Postgres database, adding scheduled jobs / blob storage / event streams / a raw bucket, writing tests for composed services, running an app locally, reading its logs, or deploying/tearing down an environment. Triggers on "prisma composer", "@prisma/composer", "prisma app", "compute()", "service.load()", "module()", "contract()", "mockService", "bootstrapService", "prisma-composer dev", "prisma-composer log", "prisma-composer deploy", "--stage", "--fresh", "--tail", "prisma-composer destroy", "prisma-composer-", "bucket()".
Profile Dart command-line applications using the VM Service protocol to capture CPU samples and identify performance bottlenecks. Helps agents automate CPU profiling, generate function call breakdown summaries, and export JSON profiles without a browser or DevTools.
Maintain `*-skills` README standards and checklist-style roadmap docs through one canonical maintenance entrypoint. Use when a repo needs profile-aware README maintenance, checklist roadmap validation or migration, or a bounded audit-first doc workflow with Markdown and JSON reporting.
Generates project context and codebase documentation for AI agents. Creates `.agents/` directory with project overview and deep codebase analysis (architecture, conventions, testing, integrations, checklist, workflows, features when vertical slicing detected, review). Use when starting work on a project, onboarding to an existing codebase, generating project documentation for agents, mapping codebase patterns, or incrementally refreshing the index from recent git changes. Triggers: "initialize .agents", "setup project index", "index project", "map codebase", "analyze codebase", "project overview", "codebase summary", "onboarding to this repo", "integrate feedback", "sync knowledge", "refresh codebase", "sync codebase", "patch index". Not for feature work, Obsidian session notes, or dev tooling setup like prettier or eslint.
Generates comprehensive planning documentation for web application projects, structuring work into context-safe phases with built-in verification criteria. Creates IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, and other planning docs based on project needs. Optimized for Cloudflare Workers + Vite + React stack. Use when starting new projects, adding major features, or restructuring existing work into manageable phases. Keywords: project planning, planning documentation, IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, UI_COMPONENTS.md, TESTING.md, AGENTS_CONFIG.md, phased development, context-safe phases, verification criteria, exit criteria, planning docs generator, web app planning, Cloudflare Workers planning, Vite React planning, project structure, project phases, major features planning, new project setup
Convert code projects into an Obsidian knowledge base. Activates when the user mentions obsidian, project documentation, knowledge base, analyzing a project, or converting a project. [After activation, you must]: 1. First read this SKILL.md file in full 2. Understand the AI writing rules (default to 00_Inbox/AI/, append-only, unified Schema) 3. Execute STEP 0: use AskUserQuestion to ask the user for confirmation 4. Start STEP 1 project scanning only after user confirmation 5. Strictly follow the order STEP 0 → 1 → 2 → 3 → 4 [Prohibited actions]: - Do not start analyzing a project without reading SKILL.md - Do not skip STEP 0 user confirmation - Do not create directly in 30_Resources (go to 00_Inbox/AI/ first) - Do not decide the output location on your own
Manage interactive terminal sessions (SSH, REPLs, databases, TUI apps) via the pty-bridge CLI. Use whenever the standard Bash tool can't handle a program that needs a real PTY — SSH logins, interactive REPLs (python, psql, mysql, node), commands that prompt for a password or confirmation, or TUI apps (vim, htop, less). Reach for this skill any time a command hangs, ignores piped input, or misbehaves under plain Bash.
React 19 + TypeScript for FMC TanStack Start apps: typed components, events, generics, ref-as-prop, Compiler-first memoization, and useEffect discipline (naming, when not to use Effect, alternatives). Use when typing React components/hooks/events, or writing/reviewing useEffect, useEffectEvent, derived state, data-fetch effects, or oxlint React Compiler / Rules of React effect rules. Not for routing/server boundaries (see tanstack-start-* skills).
Expert in the React Bits UI component framework. When developing front-end pages, always prefer components from the react-bits framework to produce standardized code. Supports describing requirements in natural language and automatically matches the best component combinations. Trigger words: react-bits, reactbits, animated component, landing page, hero section, front-end page development, make a page.
Build a standalone multi-page Markdown wiki package for a large software repository after reading and analyzing the whole codebase. Use when the agent is asked to create repository wiki documentation, onboarding docs, architecture guides, codebase tours, maintainer handbooks, or deep explanations of modules, core code paths, algorithms, design decisions, tradeoffs, tests, tooling, and operations for code learners or new maintainers. Optimized for large repositories with hundreds of thousands of lines of code where maintainers need broad coverage and deep subsystem documentation. The generated wiki must live in an independent package, usually `wiki/` or `maintainer-wiki/`, and must not be mixed into existing `docs/`, `website/`, or product documentation apps unless the user explicitly overrides this. Also supports optional Rspress/static documentation site setup when the user explicitly asks to publish or deploy the generated wiki. Supports Markdown output with Mermaid, Graphviz, and KaTeX where useful.
Use when a pull request or merge request has review comments to inspect, address, or answer, whether from a person or an automated reviewer on GitHub, GitLab, or Bitbucket. This skill handles feedback already received; it does not perform a new code review.
Migrate Riverpod from 2.0 to 3.0; automatic retry, paused listeners, legacy providers import, Ref simplification, FamilyNotifier removal, ProviderException, updateShouldNotify. Use when the user asks about Riverpod 3 migration, upgrading to Riverpod 3, or breaking changes in 3.0.
Use for Roblox multiplayer communication across the client-server boundary: designing RemoteEvent, UnreliableRemoteEvent, and RemoteFunction flows; validating client requests; handling replication-aware gameplay; applying rate limits and anti-exploit checks; reasoning about network ownership, server-authority patterns, Input Action System use in authoritative gameplay, and streaming-sensitive multiplayer correctness
Plan and, after explicit approval, execute runtime-behavior probes for local or live integrations. Use only when explicitly invoked to verify behavior that code review and normal tests cannot settle; define a controlled validation matrix, keep disposable JS probes outside tracked paths, and report observed evidence.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.