Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference. Use when user says "debug this", "fix this error", "why is this failing...
Use when designing or architecting Elixir/Phoenix/LiveView applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models, structuring multi-app projects with...
Generate focused documentation for components, functions, APIs, and features
Orchestrates comprehensive codebase research by decomposing user queries into parallel sub-agent tasks and synthesizing findings. This skill should be used when users ask questions about how code works, where f...
Decision guide for when to query Bluera Knowledge stores vs using Grep/Read on current project. Query BK for library/dependency questions and reference material. Use Grep/Read for current project code, debuggin...
Explore open-source repositories, analyze implementation details of libraries/frameworks, and research official documentation. Use when you need to understand how features are implemented in popular open-source...
Fetch up-to-date library documentation via Context7 REST API. Use when needing current API docs, framework patterns, or code examples for any library. Use when user asks about React, Next.js, Prisma, Express, V...
Use when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.
Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing...
Use when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.
Deep Laravel knowledge for code reviews. Provides detailed guidance on Eloquent, controllers, validation, routing, authorization, Blade, events, testing, and collections.
Navigate project documentation efficiently. Use when asked to "read the docs", "check documentation", or before starting unfamiliar tasks. Triggers on read docs, check docs, documentation, unfamiliar codebase.
Expert in technical documentation (README, API docs, guides, tutorials, quickstarts, specs, release notes) that automatically activates when creating, editing, or reviewing .md files in docs/ directories, READM...
Generate comprehensive software architecture documentation (ARCHITECTURE.md) with C4 diagrams, OpenAPI specs, and technology-specific guidance. This skill should be used when creating architecture documentation...
Create detailed technical specifications translating architecture designs into implementation-ready documents, including API specs, database migrations, and testing strategies. Use when starting stage 07 (tech-...
To fetch up-to-date docs and code examples from Context7 for a known library, query by a resolved library ID after running resolve-library-id (max 3 calls).
Updates documentation (README and store descriptions) across multiple languages.
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs",...
Specialized skill for creating, updating, and indexing project documentation.
API 文档生成工具。适用于任何后端技术栈的 API 接口文档生成和维护，确保前后端接口规范统一。
Guide for creating Claude Code skills to document @rytass packages (建立套件文件 skill 指南). Use when creating new package documentation skills, writing SKILL.md files, or designing skill structure.
写 API contract、接口契约、OpenAPI/AsyncAPI/GraphQL/gRPC、WebSocket/SSE、Webhook、SDK/库接口、文件格式规范。用于在 PRD 之后、HLD 之前产出可审查的接口契约/协议文档，作为跨团队协作的单一事实源。
撰写高质量的高层技术设计文档（HLD），基于 PRD 和 API Contract 做出技术架构决策。适用于 PRD 和 API Contract 完成后需要进行系统架构设计、技术选型、或制定技术方案的场景。
GitHub repository skill for ansible/ansible-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.