Loading...
Loading...
Found 728 Skills
Transform vague product or feature ideas into concrete, detailed specification documents through an interactive interview process. Use when the user wants to flesh out an idea, create a spec, write requirements, plan a product/feature/prototype, or go from "I have this idea..." to a concrete document. Works for software products, physical products, services, or any concept that needs specification.
ActivityPub protocol specification and federation concepts. Use when working with ActivityPub activities, understanding federation mechanics, implementing protocol features, or debugging federation issues.
Generate client SDKs in multiple languages from OpenAPI specifications. Use when generating client libraries for API consumption. Trigger with phrases like "generate SDK", "create client library", or "build API SDK".
Write, review, and validate commit messages following the Conventional Commits v1.0.0 specification. Use when: (1) crafting a git commit message for any change, (2) reviewing or correcting an existing commit message, (3) choosing the right commit type for a change, (4) deciding how to mark a breaking change, (5) writing multi-line commits with body and footers, or (6) understanding how commits map to SemVer bumps (PATCH/MINOR/MAJOR). Covers all standard types: feat, fix, docs, chore, refactor, perf, test, build, ci, style, revert.
Create a living specification (Spec) or plan for a feature by analyzing requirements and codebase
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
Use when creating OpenCode plugins that hook into command, file, LSP, message, permission, server, session, todo, tool, or TUI events - provides plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript event-driven modules
Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/
Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.
Generates a 6-step frontend planning document pipeline (requirements → user flows → page spec → use cases → component tree → state/API integration) into docs/en/specifications/<domain>/, with domain analysis, tech stack detection, and user review gates at each step.
WeChat Sticker Maker. Automatically crop and convert original images in 6-grid, 9-grid, or 12-grid layouts into formats that comply with WeChat sticker specifications (main sticker image 240x240, chat page icon 50x50).
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.