cyber-security-one/document-writer
.tessl/tiles/onmax/nuxt-skills/skills/document-writer/SKILL.md
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.
documentation
Updated Apr 4, 2026
$ install --global
skillsauthnpx skillsauth add cyber-security-one/security-one-waf-website document-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 3:49 PM59.8s3 files scanned
SKILL.md
- 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
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
cyber-security-one/vueuse
development
VerifiedTrustedCommunity
Use when working with VueUse composables - provides reactive utilities for state, browser APIs, sensors, network, animations. Check VueUse before writing custom composables - most patterns already implemented.
SKILL.mdUpdated Apr 4, 2026
cyber-security-one/vue
development
VerifiedTrustedCommunity
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
SKILL.mdUpdated Apr 4, 2026
cyber-security-one/vitest
development
VerifiedTrustedCommunity
Use when writing unit/integration tests for Vite projects - provides Vitest configuration, test APIs, mocking patterns, and coverage setup
SKILL.mdUpdated Apr 4, 2026
cyber-security-one/vite
tools
VerifiedTrustedCommunity
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
SKILL.mdUpdated Apr 4, 2026