tech-spec-writer
Create comprehensive technical specification documents through interactive Q&A. Use when (1) user asks to write a Tech Spec, (2) user wants to plan a new feature, (3) user needs to create technical documentatio...
Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Create comprehensive technical specification documents through interactive Q&A. Use when (1) user asks to write a Tech Spec, (2) user wants to plan a new feature, (3) user needs to create technical documentatio...
Code review guidelines covering code quality, security, and best practices.
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
Use when answering LangGraph questions. Prefer reading local project code/specs; fetch docs only if needed.
Creates, updates, and maintains documentation for projects following best practices for clarity, accessibility, and inclusivity. Use when creating new docs, improving existing documentation, checking documentat...
Analyze code changes and recommend appropriate documentation. Evaluates git diffs to determine if changes warrant README updates, inline doc additions, or dedicated documentation files. Triggers on: document ch...
Standards for API development, documentation, and maintenance using OpenAPI 3.0.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Provides context about the TireOps codebase architecture, database schema, and project structure. Use when starting work, asking about how things work, or needing to understand the system.
Retrieves up-to-date documentation and code examples for any programming library. Use when implementing features with external libraries, troubleshooting library errors, or when unsure about correct API usage.
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns.
Create, expand, and validate a “docs-as-code” documentation set for any software project (not domain-specific). Use when asked to scaffold a full project documentation structure (docs/, specs/, epics/, prototyp...
根据 leaf Spec 或 design.md 自动生成代码。当用户说"生成代码"、"实现功能"、"写代码"时自动触发。支持 CAF v0.6.5 直接从 Spec 生成。
从 L2 需求和接口定义生成架构设计文档。 当用户说"生成架构"、"技术设计"、"数据库设计"时自动触发。 输出 docs/architecture/ 目录下的设计文档。
Convert a draft document into an executable spec.json with trackable stories
Convert a draft document into an executable spec.json with trackable stories
Guidelines for using the Context7 MCP server to fetch real-time documentation and code examples.
Creates technical documentation including READMEs, API references, user guides, architecture docs, ADRs, and runbooks. Use for requests to create, write, generate, or draft documentation. Trigger phrases includ...
Reorganize project documentation with bilingual (English/Japanese) structure. Use when asked to "reorganize docs", "update documentation", or "sync documentation".
Comprehensive code documentation standards and guidelines for maintaining up-to-date documentation across Python, HTML, CSS, and JavaScript codebases. Use when creating or modifying code to ensure proper docume...
Generate and update technical documentation
Dutch Government API design rules, OpenAPI specifications, and API architecture guidelines. Use when building REST APIs for Dutch government projects, creating OpenAPI specs, or implementing API design patterns...
Expert in codebase archaeology and documentation retrieval. Use this when starting new project phases, refactoring large modules, or integrating new frameworks.
Generate and maintain comprehensive documentation. Use when writing README, API docs, code comments, or technical documentation.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.