Loading...
Loading...
Found 3,151 Skills
Search and interpret bitdrift documentation for product behavior, SDK setup, API and service docs, and best practices. Use whenever the user asks how bitdrift works, how to set up the SDK, how to configure a feature, what an API or service does, or for conceptual guidance about bitdrift — even if they do not explicitly mention documentation. Also trigger when the user mentions /bd-docs or asks about bitdrift concepts, architecture, or integration guides.
A documentation page — left nav, scrollable article body, right-rail table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
Helps maintain documentation pages based on the Diataxis method. Analyzes existing docs, classifies pages into tutorials/how-to/explanation/reference categories, identifies gaps, and helps create or restructure documentation following Diataxis principles. Use when user mentions documentation structure, Diataxis, doc categories, tutorials vs how-to guides, or reorganizing docs.
Maintain and author Editframe's skills-as-docs system. Covers file structure, frontmatter schemas, rendering conventions (html live demos, callouts, API metadata), the generation pipeline, and build/push workflow. Use when creating or editing skill files, reference documentation, frontmatter, html live blocks, API metadata, or working on the skills web renderer.
Write user-facing documentation for a new or changed feature, in the project's docs site. Use when user says 'document this feature', 'write user docs', 'create feature page', 'add to the docs site', or 'write the end-user guide'. Do NOT use for internal architecture docs (use arc42 or write-doc), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Sync documentation with code changes. Scans for README, CLAUDE.md, docs/ pages, and skills that reference behavior the current branch modifies, and updates or flags them. Use when user says 'update docs', 'sync documentation', 'is our documentation current', 'docs are stale', or 'update READMEs after this refactor'. Do NOT use for writing a fresh feature doc (use document-feature) or a new ADR (use document-decision).
Find the right Deepgram documentation for any task. Use whenever someone needs help locating docs, understanding which API to use, or wants to ask questions about Deepgram. Covers all product areas: speech-to-text, text-to-speech, voice agents, audio intelligence, and self-hosted deployments.
Use when Hermes reviews Claude-authored writeups, public docs, skill changes, README/agent/issue-template changes, or upstream speed-match documentation before syncing or publishing.
Expert technical writer specializing in clear, accurate documentation and content creation. Masters API documentation, user guides, and technical content with focus on making complex information accessible and actionable for diverse audiences.
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
Use when user-facing code changes need documentation, user says "update docs"/"document this"/"add to jamdesk docs", or after implementing APIs, CLI commands, or UI components.