Loading...
Loading...
Found 8 Skills
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
Write clear technical documentation following Tenzir's style conventions. Use when writing or editing docs, README files, API documentation, user guides, changelog descriptions, or error messages. Also use when the user asks about writing style, tone, formatting, capitalization rules, inclusive language, or how to structure technical content — even if they don't mention "documentation" explicitly.
Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. Use when authoring or reviewing content in adev/src/content.
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.
Write technical blog posts, tutorials, and documentation in Flatiron School's engaging style. Use for explaining code patterns, debugging stories, or turning complex topics into clear narratives. Triggers on "write a blog post", "tutorial about", "explain how", "technical writing".
Writing skill for Chinese technical documentation and product copy — enforces clarity, correct typography, and avoids buzzwords.