Loading...
Loading...
Found 2,897 Skills
Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.
Maintains persistent codebase knowledge across sessions through a structured knowledge graph stored in a local Obsidian vault (.doctrack/). Use this skill whenever you have just made meaningful code changes (new features, modified components, refactoring, bug fixes) to update the project's documentation. Also use it when the user asks to document code, update docs, sync documentation, initialize documentation for an existing project, or when you want to understand the existing codebase structure at the start of a session. This skill should be used proactively after any significant code modification — don't wait for the user to ask. If you changed code, update the docs. Think of it as your long-term memory system: read before working, write after changing. Also use this when a user says "doctrack init", "doctrack refresh", "refresh docs", "update docs", "sync docs", "initialize docs", "document this project", or wants to bootstrap documentation for a codebase that has no .doctrack/ vault yet.
Progressive Domain Crystallization (PDC) — a skill for building and maintaining a living domain knowledge base for any custom business application. Use this skill whenever the user is developing a business application and wants the AI to accumulate understanding of internal terminology, entities, relationships, and business rules over time — especially when that knowledge is not fully defined upfront and grows across sessions. Trigger on any of: "remember how our system works", "learn our domain", "track business entities", "build domain knowledge", "understand our terminology", "grow AI context over time", "domain model", "business rules documentation", or whenever a user says the AI doesn't understand their business-specific language or data model. Also use at the start of any session where a DOMAIN.md file exists in the project — always read it before doing any work.
Apply Cognitive Load Theory to optimize instructional design by managing intrinsic, extraneous, and germane load within working memory limits. Use this skill when the user needs to diagnose why learners are overwhelmed, redesign training or documentation for better comprehension, evaluate UI/UX information architecture for cognitive burden, or when they ask 'why is this tutorial confusing', 'how to simplify complex instructions', or 'what causes information overload'.
Answer Font Awesome questions using the official documentation
Analyzes project bounded contexts, extracts business rules and domain knowledge, writes ai-context/features/<context>.md files, and produces a teach-report.md with documentation coverage metrics. Trigger: /codebase-teach, teach codebase, extract domain knowledge, update feature docs.
Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
Generate reference documentation entry by entry for the public surface of libraries (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental differences from guidedoc: guidedoc teaches you how to use things, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When users say "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are found after feature-acceptance.
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Product compliance and safety — certifications, labeling requirements, restricted substances, documentation
Write or update external guide documents for the project —— dev-guide (for contributors/integrators/downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push at the end of feature-acceptance.
Phase 3 of the feature workflow – Complete the acceptance closed-loop. Four tasks: 1. Check layer by layer against {slug}-design.md to verify if the implementation deviates from the plan; fix any deviations on the spot instead of just "noting them" in the report. 2. Incorporate this feature into the project's overall architecture documentation. 3. If this feature changes the user story or boundaries of the corresponding requirement, update the requirement doc accordingly. 4. If this feature originated from a roadmap item, change the status of the corresponding entry in roadmap items.yaml to done and sync it with the main document. Finally, produce a {slug}-acceptance.md as the closed-loop proof for the entire workflow. Prerequisite: cs-feat-impl is completed. Trigger scenarios: User says "The feature is done, let's accept it", "Do the final check", "Prepare for merge", "Generate the acceptance report".