atmos-docs-writelisted

Write, improve, restructure, audit, or maintain Atmos user documentation. Use this whenever the user asks to create a new docs page, add a workflow guide, revise concepts or terminology, improve existing docs, refresh docs from code/spec/release evidence, sync bilingual docs, or update `apps/docs/content/docs`. Trigger for phrases like "帮我写 docs", "优化文档", "新增一篇 workflow", "调整概念说明", "发布后更新 docs", "docs for this feature", or "keep docs in sync". Reads existing docs and product evidence first, updates English and Chinese MDX together, keeps `meta.json` and `meta.zh.json` navigation aligned, verifies Fumadocs/Next checks, and avoids leaking internal implementation details into user docs.
AruNi-01/atmos · ★ 3 · Web & Frontend · score 70

Install: claude install-skill AruNi-01/atmos

# Atmos Docs Write Use this skill for ordinary Atmos user documentation work: create new pages, improve existing pages, clarify concepts, add workflow guides, audit stale docs, or refresh docs after product changes and releases. The goal is to turn product knowledge into durable, task-oriented user documentation that matches the current docs app structure. ## What This Skill Owns This skill owns user documentation under: - `apps/docs/content/docs/**/*.mdx` - `apps/docs/content/docs/**/meta.json` - `apps/docs/content/docs/**/meta.zh.json` It may read source files, release notes, specs, README files, product UI code, CLI help, and repository docs to verify behavior before writing. This skill does not own: - internal architecture docs under root `docs/` - planning specs under `specs/`, except as source evidence - landing-page changelog data; use `atmos-changelog` for `apps/landing/src/lib/changelog-data.ts` - release creation; use the relevant Atmos release skill first - marketing copy or launch assets ## Start Here Before editing docs, read: 1. `AGENTS.md` 2. `apps/docs/AGENTS.md` 3. Existing nearby docs pages and the folder `meta.json` / `meta.zh.json` files you may touch 4. The relevant area AGENTS file for source evidence: - CLI: `apps/cli/AGENTS.md` - Web app: `apps/web/AGENTS.md` - Desktop: `apps/desktop/AGENTS.md` - Mobile: `apps/mobile/AGENTS.md` - API or WebSocket behavior: `apps/api/AGENTS.md` - Runtime: `agents/references/runtime/AGENTS.md`