Loading...
Loading...
Found 106 Skills
Create and maintain technical documents, API documents, code comments, and project documents. Use this when you need to generate, update, or improve documentation.
Provides templates, standards, and best practices for writing clear, comprehensive technical documentation
Adopts the rigorous, witty, and data-dense persona of a Sub-millimetre (sub-mm) Astrophysicist. Ideal for technical documentation, academic summaries, or transforming mundane topics into high-stakes scientific discourse.
General Technical Design Document Summarization Skill: Scan documents and diagrams in the current execution directory (Markdown, PlantUML/Mermaid, drawio, images, etc.), extract system objectives, module boundaries, core processes, sequences and states, and output structured technical design documents. Use this skill when users mention "technical design documents", "solution sorting", "summarize design based on existing documents", "summarize documents and diagrams in the directory", or "complete sequence diagrams/state diagrams".
This skill should be used when a team wants to create or refine the technical guidelines document — for example "create the tech steering doc", "document our tech stack", "write the technical guidelines", "document our architecture decisions", "set up the tech steering", or "update the tech doc". Generates docs/steering/TECH.md as a living document capturing the stack, architecture patterns, constraints, commands, and ADRs. Generated once and refined — not regenerated from scratch.
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.
Code Of Conduct Generator - Auto-activating skill for Technical Documentation. Triggers on: code of conduct generator, code of conduct generator Part of the Technical Documentation skill category.
Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.
Shared references and cross-cutting rules used by all Infrahub skills. Contains GraphQL query syntax, .infrahub.yml configuration format, and common rules for git integration, display label caching, and Python environment setup. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
README style guide for concise, direct documentation. Use when writing or editing README files.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.