| name | docs |
| description | Use when authoring or editing OCX documentation โ user guide, reference pages, website content under `website/src/docs/`, VitePress pages, or doc narrative structure. |
OCX Documentation
Role: write user-facing docs for OCX website (website/src/docs/, VitePress).
Workflow
- Read source code โ no memory docs
- Read product context โ
.claude/rules/product-context.md before user-facing writing
- Search real-world examples from other ecosystems before comparisons
- Identify problem feature solves before solution
- Draft narratively โ idea โ problem โ solution โ depth
- Verify internal links point to existing sections with content
- Build locally โ
task website:serve, check rendering
Narrative Standards
- Idea โ problem โ solution, then depth โ never start "OCX is a..."
- No marketing tone โ examples make case
- Reference-style links only โ never inline
[text](url); definitions at file bottom
- Every external tool hyperlinked โ every occurrence, not first
- Analogies in
:::info callout boxes, not inline
- Custom anchors on every heading โ
{#parent-subsection}
Relevant Rules (load explicitly for planning)
.claude/rules/docs-style.md โ OCX narrative + linking + anchor conventions
.claude/rules/subsystem-website.md โ VitePress config, Vue component catalog (<Tooltip>, <Tree>, <Steps>, <Terminal>, <Frame>, <Description>, <CopySnippet>, <PackageCatalog>, etc.), styling, markdown extensions, frontmatter, generated content pipeline (auto-loads on website/**)
.claude/rules/product-context.md โ positioning, differentiators, competitive landscape
.claude/rules/quality-vite.md โ build tool conventions (if touching config)
Tool Preferences
- WebFetch / WebSearch โ real-world examples from other package managers before comparisons
task website:serve โ VitePress dev server (localhost:5173) for live preview
task website:build โ full build (schema โ recordings โ SBOM โ catalog โ VitePress)
Constraints
- NEVER edit generated content (catalog pages,
dependencies.md, .cast files, schema JSON) โ build pipeline overwrites
- NEVER inline links โ reference-style only
- NEVER hardcode colors โ use VitePress CSS variables (see
subsystem-website.md styling)
- ALWAYS read source before documenting; never memory
Handoff
- To Architect โ docs revealing design ambiguity
- To Builder โ code changes uncovered while writing docs
$ARGUMENTS