Restructure and enrich the tdmcp documentation site for artists — categorized/collapsible sidebar (EN+PT), interactive goal-based guide home, new step-by-step tutorials, copy-prompt/level-badge components. Use whenever the user asks to make the docs more interactive, easier to navigate, better organized, add categories/subcategories, add tutorials, improve docs UX/IA, or for follow-ups: re-run, continue, fix QA findings, add one more tutorial, re-organize a section, or update the docs structure. NOT for syncing docs with a release (tdmcp-docs-roadmap-update) or cookbook entries (tdmcp-cookbook-examples).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Pipeline (sub-agents, no TeamCreate in this environment): architect → (builder ∥ tutorial writers) → QA → fix loop. Data flows through _workspace/docs-interactive/ files.
_workspace/docs-interactive/ missing → initial run (full pipeline)._workspace/docs-interactive_prev/ and run fresh.Spawn docs-ia-architect (model opus). Input: the user's complaint/goals + any prior proposal from conversation. Output: 01_ia_spec.md. Review the spec briefly; if it invents nonexistent tools/pages without NEW markers, send it back once.
In ONE message spawn:
docs-interactive-builder (opus) — implements sidebar/home/components from the spec; creates stubs for tutorial pages so the build never breaks.docs-tutorial-writer (opus) per tutorial in spec §3 — each owns only its EN+PT page pair.
File ownership prevents conflicts: builder never writes tutorial prose; writers never touch config/theme.Spawn docs-roadmap-qa (opus): npm run docs:build gate, EN/PT structural parity, dead links, sidebar↔file existence cross-check, generated reference/tools.md untouched. Instruct it explicitly to write its findings to _workspace/docs-interactive/04_qa_report.md (its default from other harnesses is _workspace/docs_roadmap_qa.md — the fix loop reads the path above, so the prompt must override the default).
One retry per agent; on second failure continue without that slice and state the gap explicitly. Conflicting spec vs. reality (page missing, tool renamed) → prefer reality, note the deviation in the report.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Claude Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Claude Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
How to migrate the tdmcp Codex Desktop bundle from legacy .dxt to .mcpb (MCP Bundle) and keep it building — covers the manifest schema (verify against the installed packer, never hardcode), the build-mcpb.mjs packer/zip-fallback flow, the npm scripts, and the full .dxt→.mcpb reference sweep across docs and scripts. Use when packaging or migrating the tdmcp desktop bundle.
The English summary is being prepared. Showing the original description.
Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.
The English summary is being prepared. Showing the original description.