Loading...
Loading...
Found 17 Skills
When creating or editing markdown files, these guidelines must always be followed.
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.
Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option.
Use when creating or formatting tables in markdown. Covers table syntax, alignment, escaping, and best practices.
Chinese Documentation Formatting Reference – Rules for spaces between Chinese and English, full-width/half-width punctuation, term retention, link formatting, and conventions from the Chinese Copywriting Guidelines. Only invoke when the user explicitly uses /chinese-documentation; do not trigger automatically based on context.
README style guide for concise, direct documentation. Use when writing or editing README files.
Readme Generator - Auto-activating skill for Technical Documentation. Triggers on: readme generator, readme generator Part of the Technical Documentation skill category.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.
Plain text formatting that's readable raw AND rendered
Guide for creating Claude Code skills to document @rytass packages (建立套件文件 skill 指南). Use when creating new package documentation skills, writing SKILL.md files, or designing skill structure.