--- name: Chorus Docs slug: chorus-docs category: Writing description: Chorus Docs routes questions about how to use, configure, deploy, or operate Chorus to the live documentation site at doc.chorus-ai.dev, grounding answers in current published docs instead of memory. github: "https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/docs-chorus" language: TypeScript stars: 1144 forks: 103 install: "npx degit https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/docs-chorus ~/.claude/skills/docs-chorus" installs_to: ~/.claude/skills/docs-chorus source_path: public/skill/docs-chorus/SKILL.md collection_size: 25 category_size: 1012 collection_url: "https://dirskills.com/collections/Chorus-AIDLC/Chorus" added: 2026-08-20T07:56:07.632Z last_synced: 2026-08-20T07:56:07.632Z canonical_url: "https://dirskills.com/skills/chorus-docs" --- # Chorus Docs Chorus Docs routes questions about how to use, configure, deploy, or operate Chorus to the live documentation site at doc.chorus-ai.dev, grounding answers in current published docs instead of memory. **Install:** ```bash npx degit https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/docs-chorus ~/.claude/skills/docs-chorus ``` ## README # Docs Skill This skill is a **thin router to the live Chorus documentation site** (`https://doc.chorus-ai.dev`). Use it to answer questions about **how to use, configure, deploy, or operate Chorus** — grounding the answer in the current published docs rather than memory. It is not a workflow skill: it does not drive the AI-DLC pipeline. For that, prefer the stage skills — `idea-chorus`, `proposal-chorus`, `develop-chorus`, `review-chorus`, or `yolo-chorus` (`/skill//SKILL.md`). --- ## When to Use Consider this skill whenever the user asks a **product-usage** question about Chorus, such as: - **UI workflow** — how the Idea → Proposal → Task → Verify pipeline works in the web app, what a control does, how statuses flow. - **Agent setup** — creating an API key, permissions and role presets, connecting an agent. - **Plugin setup** — installing/configuring the Claude Code / Codex / OpenClaw / Kiro / Pi plugin, or the standalone skill. - **API / MCP** — the REST API, the MCP tool surface, authentication, real-time events. - **Deployment** — self-hosting, the CDK stack, environment configuration. - **Operations / troubleshooting** — running Chorus, diagnosing connection or setup problems. Prefer *not* to use it to drive the pipeline (claiming ideas, writing proposals, executing tasks) — that is what the stage skills above are for. This skill answers "how does the product work / how do I set it up"; the stage skills do the work. --- ## Access Convention The docs site is agent-friendly. Prefer this three-step convention every time. Rather than answering from memory, ground the answer in the docs, and avoid hardcoding a page list — the index is the source of truth and pages change over time. 1. **Fetch the index.** Get `https://doc.chorus-ai.dev/llms.txt` — a machine-readable index that lists every documentation page with a one-line summary and its `.md` URL. Note the index is a single, unlocalized file that lives only at the root `/llms.txt`; there is no locale-prefixed variant, so `https://doc.chorus-ai.dev/zh/llms.txt` (and `/ja/`, `/ko/`) is not a real URL — don't request it. 2. **Fetch the relevant page(s) as raw Markdown.** Pick the page(s) that match the question from the index, then fetch the raw Markdown by appending `.md` to the page URL (e.g. `https://doc.chorus-ai.dev/guides/getting-started` → `https://doc.chorus-ai.dev/guides/getting-started.md`). 3. **Ground the answer and link the human page.** Base your answer on the fetched Markdown, and link the human-facing page (the `.md` URL without the `.md` suffix) so the user can open it in a browser. Use whatever web-fetch capability your environment provides (your IDE's fetch tool, `curl`, etc.) — this skill states the convention, not a specific tool binding. > Note: `` (your own Chorus instance) and the docs site are different hosts. The docs site is the fixed public host `https://doc.chorus-ai.dev`; use it regardless of where your Chorus instance is deployed. --- ## Locale The `/llms.txt` index itself is not localized — there is just one, at the root. Localization applies to pages, not the index: - The index always lives at `https://doc.chorus-ai.dev/llms.txt` and lists the root (`en`) page URLs; there is no `/zh/llms.txt`. - `en` is the root (unprefixed): `https://doc.chorus-ai.dev/...` - `zh`, `ja`, `ko` are path-prefixed pages: take a page path from the index and prepend the locale — `https://doc.chorus-ai.dev/zh/...`, `/ja/...`, `/ko/...` - Appending `.md` works on the prefixed pages too (e.g. `https://doc.chorus-ai.dev/zh/guides/getting-started.md`). - Match the user's language when the docs exist in it; fall back to `en` otherwise. --- ## Relationship to the Workflow Skills This skill complements the AI-DLC workflow skills — it does not replace them: | The user wants to… | Prefer | |--------------------|--------| | Learn how to use / configure / deploy / operate Chorus | **this skill** (`docs-chorus`) | | Drive an idea / write a proposal / execute or verify a task | `idea-chorus`, `proposal-chorus`, `develop-chorus`, `review-chorus`, `yolo-chorus` | Use the live host `doc.chorus-ai.dev`. `docs.chorus-ai.dev` (with an "s") is a dead link — prefer not to use it.