Loading...
Loading...
Found 553 Skills
Use when work involves Spec Kit and you need to choose the correct `spec-kit-*` sub-skill, enforce artifact-order gates, or route remediation work (for example sequence violations or specification drift at any stage).
Work with Vercel Sandbox — ephemeral Linux microVMs for running untrusted code, AI agent output, and developer experimentation on Vercel. Use this skill when the user mentions "Vercel Sandbox", "@vercel/sandbox", sandbox microVMs, running code in isolated environments on Vercel, or wants to create/manage/snapshot sandboxes via the TypeScript/Python SDK or Vercel CLI. Also trigger when the user asks about sandbox pricing, resource limits, authentication (OIDC tokens, access tokens), system specifications, CLI commands (`vercel sandbox`), or wants to update the local documentation cache for this skill.
Python Coding Standards, including type hints, logging specifications, naming conventions, code structure, etc. Applicable to all Python code files.
Analyzes Figma designs and generates implementation-ready PRDs with detailed visual specifications. Use when user provides Figma link or uploads design screenshots. Requires Figma MCP server connection.
General Architecture Governance Specification, providing layering constraints, impact analysis, interface contracts, and dependency injection baselines. Suitable for architecture review, refactoring, and new module design of any multi-layer system.
API design patterns for REST/GraphQL framework design, versioning strategies, and RFC 9457 error handling. Use when designing API endpoints, choosing versioning schemes, implementing Problem Details errors, or building OpenAPI specifications.
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
Generate frontend page structures based on standardized Anatomy specifications; proactively ask users to select generation modes (Unsupervised/Supervised), and support automatic generation of Wrapper, Content, and Optional Store modules
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Connect the complete AI development workflow through documents. It covers domain modeling and code organization (DDD), behavior verification and automated testing (BDD), as well as AI development specification setting (Agent specifications). Use when (1) the project has .feature files, (2) the user asks to organize code by business features or define naming conventions, (3) creating or updating AGENTS.md / project rule files, (4) writing or implementing Gherkin scenarios, (5) starting a new project from scratch, or (6) the agent needs the full development lifecycle.
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement → Reason → Description → Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: "create requirements", "write requirements document", "USDM", "decompose requirements", "requirements definition", "要件定義", "要件を整理", "要件分解".
Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.