adobe-xd
Guides creation of UI/UX designs, interactive prototypes, reusable components, and design specs in Adobe XD. Use when the user asks about Adobe XD artboards, prototype links, repeat grids, component states, design tokens export, or developer handoff.
documentation-builder
Generates structured technical documentation including API docs (OpenAPI/Swagger), README files, user guides, developer guides, and changelogs. Use when the user needs to create or improve project documentation, generate API reference docs, write onboarding guides, or structure documentation for a codebase.
java-code-comments
Adds JavaDoc comments to Java code following industry standards. Covers class-level, method-level, and field-level comments for Controller, Service, ServiceImpl, Mapper, Entity, BO, DTO, VO, and other component types. Use when the user wants to add comments to Java code, generate JavaDoc documentation, or systematically document a Java codebase.
docker
Provides comprehensive guidance for Docker including container creation, images, Dockerfile, docker-compose, and container management. Use when the user asks about Docker, needs to create Docker containers, build Docker images, or manage containerized applications.
api-doc-generator
Generate API documentation by scanning Controller classes, extracting endpoint URLs, HTTP methods, parameters, and response structures, then producing standardized docs from templates. Use when the user explicitly mentions generating API documentation, creating API docs, scanning interfaces, or documenting REST APIs. Do not trigger for generic documentation requests without explicit API mention.
doc-coauthoring
Guide users through a structured three-stage workflow for co-authoring documentation: context gathering, iterative refinement, and reader testing. Use when the user wants to write documentation, proposals, technical specs, decision docs, PRDs, or RFCs. Trigger when user mentions writing docs, creating proposals, drafting specs, or collaborative document creation.
pencil-mcp-open-document
Open or create a design document. Use when you need to initialize design tasks, create new files, or switch to specific designs.
speckit-baseline
Generate a technology-agnostic feature specification by analyzing existing source code, extracting user stories, functional requirements, and acceptance criteria from code patterns. Use when the user needs to document an existing or legacy codebase, create a spec before refactoring, or reverse-engineer requirements from source files.
speckit-plan
Generate a technical implementation plan from a feature spec by filling the plan template, resolving unknowns via research, producing data-model.md, API contracts, and quickstart.md artifacts. Use when the feature spec is ready and the user needs architecture decisions, data models, API schemas, or a structured plan before task generation.
uniapp-mini
Guides uni-app mini program development including configuration, component usage, API compatibility, and conditional compilation for WeChat, Alipay, Baidu, and other mini program platforms. Use when the user wants to build uni-app mini programs, configure mini program settings, or handle platform-specific differences.
vue-router-v3
Guidance for Vue Router v3 using the official Installation, Guide, and API docs. Use when users need routing setup, navigation patterns, or API details for Vue 2 projects.
python-lib-analyzer
Analyze any Python library structure, explore modules, classes, and functions with signatures and documentation.
example-skill
A template skill to demonstrate the structure of skills.
document-ai-hero-api
Generate or update documentation for the AI Hero API by reading the source code at ~/repos/ai/course-builder. Use when user wants to document, update docs for, or understand the AI Hero API endpoints.
software-design-philosophy
Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.
compiledeck
Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy. Use when making slides, creating decks, or compiling .tex presentation files.
spec-writer
中規模以上の仕様追加・変更時に、要件を明確化して `specs/` に技術仕様書を作るためのガイド。
pr-and-documentation-standards
Standards for pull requests, documentation, and code review in this Terraform provider. Use when creating PRs, writing or editing documentation (schema descriptions, docs markdown, examples), reviewing code, or adding changelog entries. Covers PR structure, docs style guide, example conventions, and changelog practices.
documentation-writer
Create or update user-facing technical documentation from implementation details and existing docs. Use when asked to write markdown wiki/module docs, follow a documentation template, preserve legacy pages, fact-check claims against code, and report inconsistencies or migration gaps.
memstack-development-mentor
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.
