Loading...
Loading...
Found 532 Skills
Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.
Manages persistent Knowledge Graph for specifications. Caches agent discoveries and codebase analysis to remember findings across sessions. Validates task dependencies, stores patterns, components, and APIs to avoid redundant exploration. Use when: you need to cache analysis results, remember findings, reuse previous discoveries, look up what we found, spec-to-tasks needs to persist codebase analysis, task-implementation needs to validate contracts, or any command needs to query existing patterns/components/APIs.
Generates Tzatziki-based Cucumber BDD tests (.feature files) from a functional specification. Use this skill whenever a user wants to write Cucumber tests, add BDD scenarios, create feature files, generate tests, or test application behaviors with Gherkin — especially in Java/Spring projects using Tzatziki step definitions for HTTP, JPA, Kafka, MongoDB, OpenSearch, logging, or MCP. Also use when the user mentions writing integration tests, acceptance tests, or end-to-end tests in a project that already has Tzatziki/Cucumber dependencies, including TestNG-based setups.
AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology
Generates semantic commit messages following the Conventional Commits specification with proper types, scopes, breaking changes, and footers. Use when users request "write commit message", "conventional commit", "semantic commit", or "format commit".
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
Embedded C Code Style Assistant, based on the code specifications of 51 MCU teaching projects. Uses snake_case as the default naming convention, with camelCase as an option. It is used to create project structures that comply with embedded development specifications, optimize code style, and provide hardware driver templates. Suitable for embedded C project development such as 51 MCU and STM32.
Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
Batch check whether Skills comply with best practice specifications; automatically verify dimensions such as naming, preface section, structure, file cleanup, and dependencies; support single or batch checks; generate detailed inspection reports; suitable for quality verification after Skill development is completed
Generate frontend page structures based on standardized Anatomy specifications; proactively ask users to select generation modes (Unsupervised/Supervised), and support automatic generation of Wrapper, Content, and Optional Store modules
Supports automatic generation/optimization/fixation/checking of index files to ensure all index files (index.ts / index.js) comply with the barrel export specification. Core principle: All index files must follow the barrel export specification.