document-writer

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 - 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 - Complete sentences (not fragments) - H1 ( # ) : No backticks — they don't render properly - H2-H4 : Backticks work fine - 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)