write-landing-docs · git:20260918.270a4a5 · 2026-09-18 · sha256 853138365a4dc111

write-landing-docs git:20260918.270a4a5A

Immutable. This exact content never changes and is served at /api/v1/blob/853138365a4dc111.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_37wko6pxavlvhnde/853138365a4dc1113a7beda23eff65710f62dbb659ab10382f6e11b21921c37b.json

Then /plugin install write-landing-docs@markdownregistry-37wko6pxavlvhnde in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: write-landing-docs
description: 'Use for public LobeHub website documentation under docs/**, including self-hosting, deployment, migration, and configuration guides. Excludes product changelogs and source-code API docs.'
---

# Write Landing Docs

- Public website documentation is authored under `docs/**`.
- Read the `Voice & Content` section of `../../../DESIGN.md` before drafting.
- For `docs/self-hosting/**`, read [Default Audience](references/self-hosting.md).
- Verify claims, defaults, commands, limitations, and rollback behavior from current code.
- Prefer one canonical page, a recommended path, short executable steps, and a visible verification
  result. Keep English and Simplified Chinese versions aligned.
- If a published path changes, update internal links and add a tested permanent redirect in the
  landing repository that preserves locale prefixes and query parameters.
- Run the focused documentation check for every changed page.

For `docs/changelog/**`, use `../docs-changelog/SKILL.md` instead.