Loading...
Loading...
Found 491 Skills
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.
Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.
Craft elegant technical specifications with ASCII artistry, flow diagrams, and the Grove voice. The swan glides with purpose—vision first, then form, then perfection. Use when creating specs, reviewing documents, or transforming technical plans into storybook entries.
Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and find security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing grammar, configures authentication, runs test/fuzz-lean/fuzz modes, and analyzes results for 500 errors, authentication bypasses, resource leaks, and payload injection vulnerabilities. Activates for requests involving API fuzzing, RESTler testing, stateful API testing, or automated API security scanning.
Conducts comprehensive backend design reviews covering API design quality, database architecture validation, microservices patterns assessment, integration strategies evaluation, security design review, and scalability analysis. Evaluates API specifications (REST, GraphQL, gRPC), database schemas, service boundaries, authentication/authorization flows, caching strategies, message queues, and deployment architectures. Identifies design flaws, security vulnerabilities, performance bottlenecks, and scalability issues. Produces detailed design review reports with severity-rated findings, architecture diagrams, and implementation recommendations. Use when reviewing backend system designs, validating API specifications, assessing database schemas, evaluating microservices architectures, reviewing integration patterns, or when users mention backend design review, API design validation, database design review, microservices assessment, or backend architecture evaluation.
Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.
Trigger Scenarios: (1) Explicit memory requests – remember, record, don't forget, pay attention next time, form rules, generate summaries/record documents; (2) Correction and modification – note, incorrect, wrong, it should be, change to, replace with, don't, also need, missing; (3) Preference expression – I prefer, in the future, it's better, suggest, my habit, I usually; (4) Global specifications – unified, all, every, any, each, every time, all, uniformly; (5) Conversation end settlement – when the conversation ends naturally or the topic switches. Convert users' corrections, preferences and rules into structured memory files to improve the output quality of subsequent conversations.
Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Paperclip.
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Execute and implement approved specification proposals in sequence with testing and verification as the priority. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "openspec development", "development", "implementation", "implement proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation"
Chinese functional specification creation tool used to convert natural language feature descriptions into structured functional specification documents. Supports automatic branch name generation, Git branch creation, specification file initialization, and quality verification. Trigger words include: "speckit specification", "functional specification", "create specification", "feature description conversion", "speckit-specify". Use this skill when users need to convert feature ideas into structured specifications.
Execute and implement approved specification proposals in sequence using a test-and-validation-first approach. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "speckit-implement", "speckit-develop", "develop", "implement", "realize proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation".