Loading...
Loading...
Found 15 Skills
Guides app teams through authoring, structuring, and publishing help documentation (articles, release notes, FAQs) using the fusion-help-cli. USE FOR: write help articles, create release notes, set up help docs, publish documentation, sync articles, configure help config file, maintain app help content. DO NOT USE FOR: building the CLI itself, modifying Fusion.Services.Help internals, or non-documentation tasks.
Creates new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.
Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.
How to work in an OKF starter project (the `okf` starter pack): a knowledge base that is conformant with Google's Open Knowledge Format (OKF) from commit one — `concepts/`, `references/`, `notes/`, a reserved `index.md` navigation hub, and a reserved `log.md` change history. Read when the project has these folders plus reserved files, OR when asked whether a document is OKF-conformant, or to add a document to an OKF knowledge base. Carries the OKF conventions (non-empty `type` on every non-reserved doc; reserved files carry no frontmatter) as guidance, not enforcement. Complements the platform `open-knowledge` skill; does not replace it.
Produce a detailed Markdown explainer of an academic paper. The skill aims for faithful description, not critical review. Section structure mirrors the original paper, equations render as LaTeX with variable tables, citations to the paper under review use position only, and citations to other works use author-short form. Use when the user asks for a detailed paper write-up, a thorough paper explainer, or invokes "paper details". Depends on documenting-with-sources and writing-quotation.
Use when writing or editing files in src/content/blog/. Provides blog post structure and conventions.
Focuses on reviewing, maintaining, and generating project documentation (located in the docs/ directory).
Write node content documents. Read download.txt, integrate local materials for each node and write detailed, accurate, and complete Markdown documents. Each sub-agent processes one node in parallel, outputting a complete node document including overview, directory/mind map, flow chart, online image URL, and reference materials. Suitable for scenarios requiring systematic and structured content creation.
Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.
This skill should be used when writing, modifying, or reorganizing documentation in docs/learned/. Use when creating new documents, updating frontmatter, choosing categories, creating index files, updating routing tables, or moving files between categories. Essential for maintaining consistent documentation structure.
Turn complex explanations into a one-page visual HTML explainer: the model writes only an extended Markdown content draft, while the skill’s bundled CLI handles templates, components, automatic SVG layout, and STE controlled-writing checks to produce a single-file page in one call. Use this skill as well when the user says `/answer-me-with-html config` or wants to change settings (automatically opening the browser, always-on mode, default theme). Proactively use it, without waiting for the user to ask, whenever an answer involves any of the following: ≥3 interrelated concepts; a flow/protocol/architecture with branches or multiple participants; a comparison or trade-off across ≥3 dimensions; a hierarchy (table of contents, modules, taxonomy); an evolutionary history or stages; or the user says "explain the principles / I didn’t get it / draw a diagram / explain this codebase / explain it with HTML / explain visually." Do not use it for: short Q&A that can be answered in under 200 characters, commands that need to be copied and executed immediately, pure code modifications, or when the user explicitly requests plain text.
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.