document-writer
onmax/nuxt-skills
Writing guide for Nuxt blog posts and documentation with style standards, content patterns, and MDC component usage.
What is document-writer?
Provides structured guidance for writing documentation and blog posts in the Nuxt ecosystem. Use this skill when creating or editing markdown content to maintain consistent voice (active, present tense), proper grammar, and correct MDC component patterns. Includes reference files for writing style and content structure.
- Enforces grammatically correct, complete sentences in documentation (overrides brevity-first rules)
- Guides active voice and present tense usage across content
- Provides MDC component patterns (callouts, code groups, buttons) with appropriate use cases
- Supplies blog post frontmatter and structure templates
- Offers subject-first and imperative sentence patterns for technical clarity
- Includes heading conventions and code block labeling standards
How to install document-writer
npx skills add https://github.com/onmax/nuxt-skills --skill document-writer- Familiarity with Markdown syntax
- Knowledge of Nuxt ecosystem basics
- Access to nuxt-content for MDC syntax details (linked skill)
- Access to nuxt-ui for component props (linked skill)
How to use document-writer
- 1.Load the relevant reference file: writing-style.md for prose/voice work, or content-patterns.md for blog structure and frontmatter
- 2.Draft content using active voice, present tense, and subject-first sentence patterns
- 3.Apply the provided checklist (active voice 85%+, present tense, 2-4 sentences per paragraph, explanation before code)
- 4.Verify callout types match intent and use appropriate MDC components from the patterns table
- 5.Review heading conventions (no backticks in H1) and ensure code blocks have file path labels
Use cases
- Writing new blog posts for Nuxt ecosystem projects with consistent frontmatter and structure
- Editing existing documentation to align voice, tone, and grammar standards
- Choosing correct MDC callout types (note, tip, warning, important) for different content needs
- Structuring technical explanations with code examples and proper file path labels
- Ensuring multi-page documentation follows unified writing patterns
- Technical writers creating Nuxt documentation
- Developers writing blog posts for Nuxt projects
- Content editors maintaining documentation consistency
- Contributors to official Nuxt ecosystem projects
document-writer FAQ
Load writing-style.md when improving prose, voice, tone, or sentence structure. Load content-patterns.md when creating blog posts, setting up frontmatter, or using MDC components. Do not load all files at once—only what's relevant to your current task.
Yes. When writing documentation, maintain proper grammar and complete sentences. Brevity is still valued, but never at the cost of clarity or correctness.
The skill provides patterns for ::note, ::tip, ::warning, ::important callouts, ::code-group for multi-source code, and :u-button for CTAs. For detailed component props, refer to the nuxt-ui skill.
Use active voice (aim for 85%+ of sentences) and present tense. Follow subject-first patterns like 'The composable handles...' and imperative patterns like 'Add the following to...'
H1 headings should not contain backticks (they don't render properly). Backticks work fine in H2-H4 headings.
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 @onmax/nuxt-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
Nuxt 4+ development guidance with server routes, file-based routing, middleware, and latest patterns.

nuxt-better-auth
Authentication for Nuxt 4+ with Better Auth – composables, server helpers, and route protection.

nuxt-content
Typed content collections, markdown rendering, and CMS features for Nuxt with SQL queries and NuxtStudio integration.

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.