Docs Editing

Plugin docs-editing from marketplace cadasto in Cadasto/plugin-marketplace. Commands read from the repo's manifest — 12 days ago.

Skills (8)

• ai-seo

  Use when asked to make content citable by AI systems ("add or update llms.txt", "add JSON-LD or schema.org markup", "serve Markdown twins", "optimise for AI search or RAG retrieval", "why does the AI summarise our docs wrongly?"). Not classic search SEO (seo-audit).

• copy-editing

  Use when asked to improve prose that already exists ("edit this", "tighten this", "review this page", "proofread", "cut this down", "fix the tone", "why does this read badly?"). Line-edits to house style and flags unsupported claims. Editing, not drafting (technical-writing); AI tells throughout is

• docs-editing

  Router for prose work ("improve these docs", "what should this document be?") or any request spanning technical-writing (new docs), copy-editing (tighten existing), humanize (AI tells), marketing-copy (landing and launch copy), seo-audit (search visibility), ai-seo (llms.txt, AI citability).

• docs-lint-setup

  Use when asked to "set up Vale", "add prose linting", "bootstrap the docs linter", "add a prose-lint CI job", "lint for AI tells", or "why is Vale so noisy?". Writes .vale.ini, seeds the vocabulary, adds the ai-tells style; never overwrites an existing config unprompted.

• humanize

  Use when asked to remove AI writing patterns from existing prose, such as "humanize this", "this reads like ChatGPT", "remove the AI tells", "make it sound less robotic", "is this AI slop?". Finds tells, then restates without adding facts. Not general tightening (copy-editing) and never an authorshi

• marketing-copy

  Use when asked for positioning or promotional copy ("write the landing page", "the hero section", "a tagline", "product or feature copy", "the launch announcement or release post", "make the pitch clearer"). Benefit-led copy for technical readers, claims grounded.

• seo-audit

  Use when asked about search-engine visibility ("run an SEO audit", "fix titles and meta descriptions", "check headings, internal links, sitemap, robots.txt", "why isn't this page indexed?", "find duplicate or orphan pages"). Classic SEO, not AI citability (ai-seo).

• technical-writing

  Use when asked to write documentation ("write a README", "document this API or feature", "write a how-to, tutorial, or reference page", "write release notes or a changelog entry", "structure the docs", "what should this document contain?"). New docs; editing existing prose is copy-editing.

Subagents (2)

• prose-reviewer

  Use this agent to review documentation or page copy for the defects a linter cannot see: unsourced statistics, testimonials and superlatives; capability described as shipped when it is planned; inventories and counts that no longer match the tree; two document kinds merged into one file; terminology

• seo-auditor

  Use this agent for a context-isolated discoverability sweep over a docs tree or published site: per-page titles, meta descriptions, single h1, heading order, canonicals, image alt text and link text; then robots.txt, sitemap coverage, redirect chains, orphan and duplicate-intent pages; then the AI-c

Hooks (2)

• SessionStart

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

• PostToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/prose-lint-on-save.sh

Similar plugins