Loading...
Loading...
Found 621 Skills
Use when specification drift is discovered at any stage and existing Spec Kit artifacts (`spec.md`, `plan.md`, `tasks.md`) must be reconciled in-place without creating a new feature branch.
Exclusive skill set for the GoFrame development framework. Provides a complete framework usage guide for Go language developers, covering best practices for core components such as command-line management, configuration management, logging components, error handling, data validation, type conversion, cache management, template engines, database ORM, and I18n internationalization. Includes project engineering structure specifications, development model guidelines, solutions to common problems, and rich practical code examples. Suitable for building various Go projects such as RESTful APIs, gRPC microservices, and web applications, helping developers quickly master the features of the GoFrame framework and improve development efficiency and code quality.
Analyze a GitHub issue and create a detailed technical specification
Create a new track with specification and phased implementation plan
Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
Intelligent agent for interpreting vague ERPNext development requests and producing concrete technical specifications. Use when receiving unclear requirements like 'make invoice auto-calculate', 'add approval workflow', 'sync with external system'. Triggers: user gives vague requirement, need to clarify scope, translate business need to technical spec, determine which ERPNext mechanisms to use, create implementation plan.
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints. Covers contract-first design, resource modeling, error handling, pagination, and security.
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
Create or update a RootSpec specification — interview-driven with built-in validation and derived artifact generation. Use this when a user wants to define, expand, revise, or reinterpret their product specification, add features, or edit any spec level.