document-writer

The document-writer skill provides a specialized framework for generating high-quality documentation and blog content consistent with official Nuxt ecosystem standards. It enforces strict grammatical precision, prohibiting the common AI habit of sacrificing sentence structure for brevity. By prioritizing clear, unambiguous prose and standardized structural patterns, this tool ensures that technical content remains accessible and authoritative. Users can generate blog posts, setup guides, or configuration tutorials that adhere to specific Nuxt conventions, such as proper H1 heading formatting and the correct application of callout components. Whether detailing a new feature or explaining complex composables, the agent maintains an active voice and present tense, ensuring your technical manuals meet the professional requirements expected of the Nuxt framework and its surrounding community projects.

When to Use This Skill

• •Drafting technical blog posts for Nuxt-related projects
• •Authoring documentation for custom Vue composables or plugins
• •Updating legacy README or documentation files to match official project patterns
• •Creating tutorials that integrate Nuxt Content and MDC syntax

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

• “Draft a documentation page for this new composable
• “Write a blog post about our latest Nuxt integration following project standards
• “Refactor this documentation section to meet Nuxt style guidelines
• “Explain this configuration step using proper MDC callouts
• “Draft a guide for installing our project, ensuring professional grammar

Pro Tips

• 💡Always explicitly state the target audience for your document; this helps the skill tailor its tone, complexity, and examples appropriately.
• 💡When incorporating Nuxt-UI components, provide a high-level description of the desired UI element and its purpose, not just the component name, for optimal usage guidance.
• 💡For complex technical explanations, break them down into smaller, logical sections and ask the skill to elaborate on each part sequentially to maintain clarity and focus.

What this skill does

• •Enforces strict adherence to Nuxt ecosystem writing standards
• •Validates grammatical accuracy and full-sentence structure
• •Applies standardized callout components like ::note, ::tip, and ::warning
• •Generates content using the required H1, H2, and H3 heading constraints
• •Maintains active voice and present tense throughout technical guides

When not to use it

• ✕Writing creative fiction or non-technical marketing copy
• ✕Generating short-form social media updates where brevity outweighs formal grammar

Example workflow

1. Define the technical scope and audience for the documentation
2. Trigger the agent to draft the content using the specified tone guidelines
3. Review the generated text for proper H1 and H2 heading formatting
4. Insert appropriate callout components like ::tip or ::warning where needed
5. Verify that all code blocks include necessary file path labels
6. Finalize the document with a grammatical check for active voice

Prerequisites

• –Access to the project's content structure
• –Basic knowledge of Nuxt Content (MDC) syntax

Pitfalls & limitations

• !Using backticks in H1 tags, which prevents proper rendering
• !Over-relying on sentence fragments which violates the grammar mandate
• !Ignoring the specific callout types defined for Nuxt-UI and Nuxt-Content

FAQ

How it compares

Unlike generic writing prompts that often produce vague or grammatically loose text, this skill forces strict adherence to official Nuxt writing standards, ensuring every document is ready for production deployment without manual style correction.

Source & trust

Recommended Rules

Recommended Workflows

Recommended MCP Servers