document-writer

Style guide and content patterns for Nuxt documentation and blog posts. Writing guidance for blog posts and documentation following patterns from official Nuxt websites. Override : When writing documentation, maintain proper grammar and complete sentences. The "sacrifice grammar for brevity" rule does NOT apply here. Documentation must be: Brevity is still valued, but never at the cost of clarity or correctness. For component and syntax details, use these skills: 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. For component props: see nuxt-ui skill - Enforces active voice, present tense, and grammatically correct prose without sacrificing clarity for brevity - Provides writing patterns (subject-first, imperative, contextual) and modal verb guidance (can/should/must) for consistent documentation voice - Includes MDC component patterns for callouts (note, tip, warning, important) and CTAs, with references to nuxt-content and nuxt-ui skills for syntax and props - Offers structured checklist covering voice, tense, paragraph length, code block labeling, and callout type appropriateness - Writing blog posts for Nuxt ecosystem projects - Creating or editing documentation pages - Ensuring consistent writing style across content - Grammatically correct - Clear and unambiguous - Properly punctuated...