Loading...
Loading...
Found 550 Skills
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Authoritative MCU chip specification query Skill. Auto-activates when users work with MCU/embedded development, chip selection, hardware design, or peripheral configuration. Queries chip parameters, pin definitions, TRM registers, and programming guides via the ChipCtx MCP interface. Trigger keywords: chip models (STM32/ESP32/nRF, etc.), pin definitions, peripheral configuration, UART/SPI/I2C/ADC, registers, datasheets.
Audit skill SKILL.md files for compliance with the agentskills.io specification. Checks frontmatter fields (name, description, compatibility, metadata, argument-hint) and metadata sub-fields (author, scope, confirms). Use when adding new skills, reviewing skill quality, or ensuring all skills follow the spec. Triggers: "audit skills", "check skill spec", "skill compliance", "are my skills up to spec", "/claude-skill-spec-audit".
Author or modify Azure TypeSpec API specifications. USE FOR: Any task that creates, modifies, or troubleshoots .tsp files or TypeSpec API specifications — including but not limited to API versioning evolution(add new preview version, add new stable version), ARM resource type(tracked, proxy, extension, child resources) or data-plane resource definitions, resource operations (CRUD, PATCH, custom actions, paging, async/Long Running Operations), models, enums, unions, properties, decorators, constraints, parameters, and swagger-to-TypeSpec conversion. DO NOT USE FOR: SDK generation from TypeSpec, releasing SDK packages, single MCP tool calls that do not require multi-step workflows. TOOLS/COMMANDS: azsdk_typespec_generate_authoring_plan, azsdk_run_typespec_validation
Git Version Control & Collaboration Expert, covering GitHub/Gitee platform operations, Conventional Commits specifications, and PR/MR best practices.
SPARC development workflow: Specification, Pseudocode, Architecture, Refinement, Completion. A structured approach for complex implementations that ensures thorough planning before coding. Use when: new feature implementation, complex implementations, architectural changes, system redesign, integration work, unclear requirements. Skip when: simple bug fixes, documentation updates, configuration changes, well-defined small tasks, routine maintenance.
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
Component development expert for general React projects. Suitable for scenarios that do not rely on KWC project structure and only need to use @kdcloudjs/shoelace and KWC extended components in React projects. Responsible for component code writing, access methods, event binding, style specifications and related API consultation. If the current project is already a KWC React project, please use kwc-react-development instead.
Use when writing specifications for features, projects, or requirements — applies Jobs to Be Done (JTBD) methodology with acceptance criteria focus, no implementation details, and SLC release planning
Rewrites an existing skill's SKILL.md (or any pipeline workflow document) into a high-quality, strict, prompt-enforced FSM (Finite State Machine)-driven specification. Use when user says "refine skill", "rewrite SKILL.md", "规范化 skill", "改写工作流文档", "优化 skill 文档", or mentions "skill-refiner".
Converge ideas of requirements, pages, modules, processes, visuals and experiences into implementable product, interaction, interface and visual design specifications
Get an external patent examiner review of a patent application. Use when user says "专利审查", "patent review", "审查意见", "examiner review", or wants critical feedback on patent claims and specification.