Start a new composition: project init, brainstorm, then ask whether graph or startcycle follows. Generated from plugin-commands.json; invoke as $bdb-aos:startproject.
The English summary is being prepared. Showing the original description.
Pre-ship framing and the technical release gate, with approvals under the go-gate rules. Generated from plugin-commands.json; invoke as $bdb-aos:shipping.
The English summary is being prepared. Showing the original description.
Implement ONE tdmcp tool from a spec — the canonical file pattern (Zod schema + …Impl + register… ToolRegistrar), a bridge Python payload via buildPayloadScript, and an offline msw unit test — touching only new files, never shared registries. Use when coding/implementing/writing a tdmcp tool, generator, effect, control, CHOP/TOP/SOP builder, or Python bridge work, especially when several features are built in parallel.
The English summary is being prepared. Showing the original description.
Run a prompt repeatedly on an interval, using the harness built-in plus loop templates. Generated from plugin-commands.json; invoke as $bdb-aos:loop.
The English summary is being prepared. Showing the original description.
Wire builders' isolated tdmcp tool files into the shared registries, CLI, and docs as a single writer, conflict-safe, and confirm a green typecheck + build. Use when integrating/wiring/registering new tdmcp tools, adding their CLI commands, resolving build breaks after parallel feature work, or merging several builders' files into the registry without conflicts.
The English summary is being prepared. Showing the original description.
Design a tdmcp feature into an implementable spec before any code is written — choose the layer, define the Zod input schema, lay out the TD network topology, plan the bridge/Python approach, sketch a UI wireframe when relevant, and list probe-first risks + the test plan. Use whenever a tdmcp feature idea needs a design/wireframe/spec, or when someone asks to plan/scope/architect a new tool, generator, effect, control, or AI prompt for the TouchDesigner MCP server.
The English summary is being prepared. Showing the original description.
Browse and preview AOS skills, agents and playbooks in the local store UI. Generated from plugin-commands.json; invoke as $bdb-aos:store.
The English summary is being prepared. Showing the original description.
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
The English summary is being prepared. Showing the original description.
Consolidate the five tdmcp surveyor reports into one prioritized FEATURE_BACKLOG.md — dedupe cross-surface overlaps, reconcile every candidate against the roadmap (NEW vs planned vs extension), rank by a selectable impact×effort weighting profile into P0/P1/P2 (high-confidence first), and emit per-surface tables + a recommended-next shortlist that hands straight to the build pipeline. Use when a td-synthesizer agent is consolidating surveys during the feature-discovery harness.
The English summary is being prepared. Showing the original description.
Set up the current project folder for AOS: slug, wiki, memory, Synapse map, AGENTS.md. Generated from plugin-commands.json; invoke as $bdb-aos:init.
The English summary is being prepared. Showing the original description.
Bring this machine to a complete, verified AOS installation (skills, MCP servers, gate hooks, memB, OpenWiki, Synapse). Generated from plugin-commands.json; invoke as $bdb-aos:setup.
The English summary is being prepared. Showing the original description.
Start a single Rhino MCP session. Accepts a version argument (e.g. `8`, `WIP`) and an optional explicit port. Walks forward from `10500` to pick a free port if none was given. On macOS this opens a new document in the running Rhino; on Windows it launches a new Rhino process. Use when the user asks to start a Rhino MCP session — for N parallel Rhinos use `/launch-rhinos` instead.
The English summary is being prepared. Showing the original description.
Coordinate parallel coding agents across repositories through the AO daemon. Generated from plugin-commands.json; invoke as $bdb-aos:orchestrator.
The English summary is being prepared. Showing the original description.
Check the machine and the current project, and print suggested permissions.allow entries without writing any settings. Generated from plugin-commands.json; invoke as $bdb-aos:doctor.
The English summary is being prepared. Showing the original description.
Run the startcycle-graph pipeline: durable state, repair loop, quality gate, escalation. Generated from plugin-commands.json; invoke as $bdb-aos:graph.
The English summary is being prepared. Showing the original description.
Plan end to end: draft, render in plan-canvas or Plan Builder, annotate, await approval, then hand off. Generated from plugin-commands.json; invoke as $bdb-aos:plan.
The English summary is being prepared. Showing the original description.
Supervise other Claude Code sessions on this machine: roster, status requests, GO board, idle notices. Generated from plugin-commands.json; invoke as $bdb-aos:mastersession.
The English summary is being prepared. Showing the original description.
Spin up N Rhino MCP sessions in parallel and fan out one agent per Rhino. Use when the user wants multiple Rhinos running simultaneously with each agent driving its own — e.g. "spawn 3 agents and have each launch Rhino", "run 5 Rhino tasks in parallel". For a single Rhino, use `/launch-rhino` instead.
The English summary is being prepared. Showing the original description.
List all pb-* playbooks with duration, difficulty and requirements, and start one. Generated from plugin-commands.json; invoke as $bdb-aos:playbooks.
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-dxt.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.
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
The English summary is being prepared. Showing the original description.
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
The English summary is being prepared. Showing the original description.
Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar
The English summary is being prepared. Showing the original description.
Clean up git worktrees across your repos: list every worktree, classify it as merged, remote-only, local-only or dirty, recap what each holds, and remove only the merged clean ones after GO. Use for "clean up worktrees", "what is in my aos-wt folders", "land my worktrees", "prune worktrees".
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)