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- 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)
How to use document-writer
- 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.Draft content using active voice, present tense, and subject-first sentence patterns
- 3.Apply modal verbs (can, should, must) to indicate optionality or requirement
- 4.Use appropriate MDC callout components: ::note for info, ::tip for suggestions, ::warning for cautions, ::important for required information
- 5.Add file path labels to code blocks and avoid backticks in H1 headings
- 6.Review your draft against the quality checklist: active voice 85%+, present tense, 2-4 sentences per paragraph, explanation before code
Use cases
- 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
- 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
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.
No. Backticks do not render properly in H1 headings. Use them freely in H2-H4 headings instead.
No. The document-writer skill overrides brevity rules. Maintain proper grammar, complete sentences, and clear punctuation even if it requires more words.
document-writer provides writing standards and content structure. Use nuxt-content for MDC syntax details and nuxt-ui for component props and theming.
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:
| Skill | Use For |
|---|---|
| nuxt-content | MDC syntax, prose components, code highlighting |
| nuxt-ui | Component props, theming, UI patterns |
Available References
| Reference | Purpose |
|---|---|
| references/writing-style.md | Voice, tone, sentence structure |
| references/content-patterns.md | Blog frontmatter, structure, component patterns |
Loading Files
Consider loading these reference files based on your task:
- references/writing-style.md - if writing prose, improving voice/tone, or structuring sentences
- references/content-patterns.md - if creating blog posts, setting up frontmatter, or using MDC components
DO NOT load all files at once. Load only what's relevant to your current task.
Quick Reference
Writing Patterns
| Pattern | Example |
|---|---|
| Subject-first | "The useFetch composable handles data fetching." |
| Imperative | "Add the following to nuxt.config.ts." |
| Contextual | "When using authentication, configure..." |
Modal Verbs
| Verb | Meaning |
|---|---|
can | Optional |
should | Recommended |
must | Required |
Component Patterns (WHEN to use)
| Need | Component |
|---|---|
| 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
- Load relevant reference file (writing-style.md for prose, content-patterns.md for structure)
- Draft content using active voice and present tense
- Apply the checklist below to verify quality — if any item fails, revise and re-check
- 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
Related skills
More from onmax/nuxt-skills and the wider catalog.

motion
Production-ready Vue 3/Nuxt animation library with gestures, scroll effects, and spring physics

nuxt-better-auth
Guides authentication in Nuxt apps using @nuxtjs/better-auth with client/server APIs, route protection, and session management.

nuxt-content
Build typed, content-driven Nuxt applications with collections, queries, and Markdown rendering.

nuxt-modules
Create, test, and publish Nuxt modules with defineNuxtModule patterns, Kit utilities, and CI/CD automation.

nuxt-seo
Nuxt SEO meta-module for robots.txt, sitemaps, OG images, and structured data.

nuxt-studio
Configure and operate self-hosted Nuxt Studio editor for Nuxt Content projects.