context-routing
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Discover research technical docs skills, compare source repositories and read the instructions for each workflow.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Generate design system documentation (markdown only, no code) from a Figma component URL. Triggers on "/figma-doc ", requests to "document this component", or when given a Figma design URL to document. Automati...
Create spec documents (spec.md, context.md, tasks.yaml, dependencies.yaml, validation.yaml). Receives validation data from spec-validate.
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Use when bootstrapping C3 documentation for any project - guides through Socratic discovery and delegates to layer skills for document creation
DogCoach 프로젝트의 docs 폴더 내 마크다운 문서를 최신 코드 및 데이터베이스 구조에 맞게 업데이트합니다.
ドキュメント駆動で機能を実装。関連ドキュメントを自動収集し、既存パターンに沿ったコードを生成。 トリガー: 「実装して」「implement」「機能を作って」「コード生成」「ドキュメントから実装」
Senior Staff Engineer guidance for Clean Architecture, SOLID principles, and Domain-Driven Design. Use for refactoring, planning new modules, or reviewing code organization.
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...
Write self-documenting code with minimal, evergreen comments that explain complex logic without documenting changes or temporary fixes. Use this skill when adding comments to any code file. When deciding whethe...
Describes the primary technologies, frameworks, libraries, and language conventions used in this codebase.
Validates documentation consistency and auto-generates documentation stubs. Auto-activates when users ask about docs sync, broken links, stale content, or when code changes need documentation. Checks version co...
Find most up-to-date documentation for relevant tools, libs, etc.
Expert on GigLedger's architecture, app structure, feature modules, and state management. Use when implementing features, creating new modules, or understanding the architectural patterns. References docs/07_ap...
Use when documenting Python research code usage, setup, and experiment reproduction.
コード変更、API変更、新機能追加時にドキュメントを自動更新します。公開APIやインターフェースの変更、新クラス・関数・モジュールの追加、アーキテクチャの重要な変更、ユーザーからの明示的なドキュメント更新依頼時に起動...
Update IBL5 documentation during pull requests and feature development. Use when updating docs, creating README files, or documenting completed work.
Guide for creating and updating README files following autonomous-bits development standards. Use this when asked to create or update README files, ensure documentation completeness, or review README quality.
Expert Python development guidance for this codebase. Use when writing Python code, implementing features, or following project coding standards and patterns.
Create comprehensive spec with diagrams, flows, and thorough documentation. Use when: detailed spec, comprehensive spec, full spec, baldrick spec. Triggers on: detailed, comprehensive, full spec, thorough.
Generate PR documentation from completed spec and git diff. Use when: pr docs, generate docs, pull request docs, baldrick docs. Triggers on: pr docs, generate docs, document changes.
Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript,...
Document the reasoning behind implementation decisions as markdown files. Creates decision records that future developers can reference.
Best practices for creating clear, comprehensive, and maintainable documentation for code, APIs, and systems
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.