Loading...
Loading...
Found 653 Skills
Generate comprehensive AGENTS.md documentation for backend projects with complete API specifications, business rules, data models, and data flows. Use when (1) Creating AGENTS.md from existing CLAUDE.md, (2) Documenting backend API modules with FastAPI routes, (3) Migrating documentation to AGENTS.md/CLAUDE.md symlink structure, (4) Adding complete API interface documentation to existing specs, (5) Creating module-level AGENTS.md for specific features (mcp, teamo_code, file_system, etc.)
Amend architectural specifications through formal protocol.
Strict JSON:API v1.1 specification compliance. Trigger: When creating or modifying API endpoints, reviewing API responses, or validating JSON:API compliance.
Design new APIs or review existing ones using debate-driven multi-agent workshop. Agents propose designs and challenge each other on consumer UX, domain modeling, security, performance, and standards compliance. Use when the user wants to design a new API, review an existing API, decide between REST/GraphQL, or improve API architecture. Keywords: api design, api review, rest api, graphql, openapi, api architecture, api specification, endpoint design, api standards.
Generate OpenAPI specification from ALPS profile. Converts ALPS semantic descriptors to RESTful API definitions with automatic validation.
Automated SPEC generation from REQ/CTR - generates implementation-ready YAML specifications with TASKS-Ready scoring
Create detailed feature specifications with user stories, acceptance criteria, and edge cases. Use when starting a new feature or initializing a new project.
Generate structured PRD documents for n8n automation workflows. Use when planning n8n workflows, creating automation requirements, starting a new n8n project, or preparing workflow specifications before building.
Write unambiguous specifications using EARS (Easy Approach to Requirements Syntax) patterns. Provides 6 sentence templates that eliminate ambiguity: Ubiquitous, Event-driven, State-driven, Unwanted behavior, Optional feature, and Complex. Use when: "EARS", "specification writing", "write specs", "仕様を書く", "EARS記法", "仕様を明確化", "requirements specification", "unambiguous specification".
Product Requirements Document creation and feature specification writing. Use when writing PRDs, technical specs, feature documentation, or requirements. Triggers on "PRD", "product requirements", "feature spec", "technical requirements", "functional spec".
In-repo planning and specification system for software projects. Use when asked to "create a plan", "write a spec", "document a proposal", "blueprint a feature", or when doing architectural planning work.
Guidance on **generation** and **implementation** of TinyVue component library code, used when analyzing, planning or generating components. This skill provides strict API constraints, search processes for documents and examples, as well as code specifications.