Loading...
Loading...
Found 49 Skills
Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.
Write, audit, and improve AGENTS.md files for AI coding agents. Use when creating or improving agent context for a codebase.
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.
Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, tests, formatting, and builds.
Add a linked resource (external file reference) to a ***plain spec. Use when the user wants to reference a JSON schema, API spec, data file, or other external file from within a functional spec, definition, or implementation requirement.
README style guide for concise, direct documentation. Use when writing or editing README files.
Write clear, emotionally resonant, and well-structured content that readers remember and act upon. Use when writing or editing any text—Twitter posts, articles, documentation, emails, comments, updates—for maximum clarity, engagement, and impact.
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
Guidelines for writing and editing Plain package READMEs. Use this when creating or updating README files.
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
Write and revamp product documentation to a high editorial standard using Mintlify, with strong information architecture, precise titles/descriptions, parameter-level clarity, cross-linking, and maintainable examples. Use when creating new docs pages, refactoring existing docs, improving docs structure/navigation, or standardizing docs quality across a repository.