PluginBench
Skill
Pass
Audit score 90

document-writer

onmax/nuxt-skills

Writing guide for Nuxt documentation and blog posts with style standards, content patterns, and MDC component usage.

What is document-writer?

A skill for writing consistent, grammatically correct documentation and blog posts in the Nuxt ecosystem. Use it when creating or editing markdown content to follow established voice, tone, and structure patterns while leveraging MDC components and Nuxt UI.

  • Enforces active voice and present tense writing standards
  • Provides content structure patterns for blog posts and documentation
  • Specifies when to use MDC callout components (note, tip, warning, important)
  • Defines heading conventions and code block labeling practices
  • Supplies modal verb guidance (can, should, must) for clarity
  • Includes subject-first and imperative sentence patterns

How to install document-writer

npx skills add https://github.com/onmax/nuxt-skills --skill document-writer
Prerequisites
  • Nuxt project with nuxt-content module for MDC syntax support
  • Basic familiarity with markdown formatting
  • Access to reference files (writing-style.md and content-patterns.md)
Claude Code
Cursor
Windsurf
Cline

How to use document-writer

  1. 1.Load the relevant reference file based on your task: writing-style.md for prose and voice, or content-patterns.md for structure and frontmatter
  2. 2.Draft content using active voice, present tense, and subject-first sentence patterns
  3. 3.Apply modal verbs (can, should, must) to indicate optionality or requirement
  4. 4.Use appropriate MDC callout components: ::note for info, ::tip for suggestions, ::warning for cautions, ::important for required information
  5. 5.Add file path labels to code blocks and avoid backticks in H1 headings
  6. 6.Review your draft against the quality checklist: active voice 85%+, present tense, 2-4 sentences per paragraph, explanation before code

Use cases

Good for
  • Writing new blog posts for Nuxt ecosystem projects with consistent frontmatter and structure
  • Editing existing documentation to align with official Nuxt writing standards
  • Creating component guides that explain features before showing code examples
  • Structuring multi-part tutorials with proper heading hierarchy and callouts
  • Ensuring grammatical correctness across documentation without sacrificing clarity
Who it's for
  • Technical writers documenting Nuxt projects
  • Developers authoring blog posts or guides
  • Content maintainers standardizing documentation style
  • Open-source project maintainers following Nuxt conventions

document-writer FAQ

When should I use ::note vs ::tip vs ::warning?

Use ::note for informational asides, ::tip for suggestions and best practices, ::warning for cautions or potential issues, and ::important for required information or critical steps.

Can I use backticks in H1 headings?

No. Backticks do not render properly in H1 headings. Use them freely in H2-H4 headings instead.

Should I sacrifice clarity for brevity in documentation?

No. The document-writer skill overrides brevity rules. Maintain proper grammar, complete sentences, and clear punctuation even if it requires more words.

What's the difference between this skill and nuxt-content or nuxt-ui?

document-writer provides writing standards and content structure. Use nuxt-content for MDC syntax details and nuxt-ui for component props and theming.

How much active voice should I aim for?

Target 85% or higher active voice in your documentation. Use the checklist to verify before finalizing content.

Full instructions (SKILL.md)

Source of truth, from onmax/nuxt-skills.


name: document-writer description: 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. license: MIT

Documentation Writer for Nuxt Ecosystem

Writing guidance for blog posts and documentation following patterns from official Nuxt websites.

When to Use

  • Writing blog posts for Nuxt ecosystem projects
  • Creating or editing documentation pages
  • Ensuring consistent writing style across content

Writing Standard

Override: When writing documentation, maintain proper grammar and complete sentences. The "sacrifice grammar for brevity" rule does NOT apply here.

Documentation must be:

  • Grammatically correct
  • Clear and unambiguous
  • Properly punctuated
  • Complete sentences (not fragments)

Brevity is still valued, but never at the cost of clarity or correctness.

Related Skills

For component and syntax details, use these skills:

SkillUse For
nuxt-contentMDC syntax, prose components, code highlighting
nuxt-uiComponent props, theming, UI patterns

Available References

ReferencePurpose
references/writing-style.mdVoice, tone, sentence structure
references/content-patterns.mdBlog frontmatter, structure, component patterns

Loading Files

Consider loading these reference files based on your task:

DO NOT load all files at once. Load only what's relevant to your current task.

Quick Reference

Writing Patterns

PatternExample
Subject-first"The useFetch composable handles data fetching."
Imperative"Add the following to nuxt.config.ts."
Contextual"When using authentication, configure..."

Modal Verbs

VerbMeaning
canOptional
shouldRecommended
mustRequired

Component Patterns (WHEN to use)

NeedComponent
Info aside::note
Suggestion::tip
Caution::warning
Required::important
CTA:u-button{to="..." label="..."}
Multi-source code::code-group

For component props: see nuxt-ui skill

Headings

  • H1 (#): No backticks — they don't render properly
  • H2-H4: Backticks work fine

Workflow

  1. Load relevant reference file (writing-style.md for prose, content-patterns.md for structure)
  2. Draft content using active voice and present tense
  3. Apply the checklist below to verify quality — if any item fails, revise and re-check
  4. Verify callout types match intent (note/tip/warning/important)

Example

# Getting Started with Authentication

Nuxt Better Auth provides a simple way to add authentication to your application.
Configure the module in your `nuxt.config.ts` to get started.

::note
Authentication requires a database connection. See the [database setup](/docs/database) guide for details.
::

## Installation

Add the module to your project:

~~~bash [Terminal]
pnpm add @nuxtjs/better-auth
~~~

The module auto-imports the `useUserSession` composable. Access the current user session from any component.

Checklist

  • Active voice (85%+)
  • Present tense
  • 2-4 sentences per paragraph
  • Explanation before code
  • File path labels on code blocks
  • Appropriate callout types
  • No backticks in H1 headings