smithery.ai

write-docs

Create or revise documentation for the simple-stack repository, especially MDX guides and API reference content under www/src/content/docs/.

First seen Mar 19, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • Create or revise documentation for the simple-stack repository, especially MDX guides and API reference content under www/src/content/docs/.
  • Use when asked to write docs, restructure guides, add examples, or enforce documentation tone, structure, and code highlighting conventions.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,350 B
  • docs SUMMARY.md 299 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

Write Docs

Overview

Write clear, progressive documentation for this repository using the existing Starlight + MDX docs setup. Favor stepwise examples, explicit usefulness, and consistent tone.

Workflow

  1. Locate the target doc or create a new MDX file under www/src/content/docs/.
  2. Follow the style reference in references/docs-style.md.
  3. Start each feature or API section with: what it does, why it is useful, then an example.
  4. Build examples incrementally (naive first, then improvements and features).
  5. Use Starlight code line highlighting (ins, del, {n-m}) to emphasize changes while keeping full context.
  6. Keep guide content and API reference content clearly separated by headings or separate docs.

House style essentials

  • Use second-person voice and consistent terminology.
  • Avoid emojis, slang, or playful narration.
  • Prefer short, direct sentences and descriptive headings.

References

  • Read references/docs-style.md for the full style guide and code highlighting examples.