299 件（hybridlabor-api のリポジトリ） ・ 人気順
概要と使いどころ
How to add a page to the tdmcp VitePress docs site so it builds, gets a clean URL, and lands in the right nav — including the repo's partial-translation convention (only the artist guide is EN+PT; reference/legal pages are English). Use when authoring the privacy policy or any new docs page for tdmcp.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate Firecrawl into product code: SDK setup and FIRECRAWL_API_KEY onboarding, /scrape, /search and /interact endpoints. Use when an application (not the agent itself) calls Firecrawl.
日本語の概要は準備中です。原文の説明を表示しています。
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-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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
How to author one new tdmcp MCP tool the house way — the file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport over executePythonScript), the result helpers (errorResult/guardTd/jsonResult/structuredResult), fail-forward error handling, ESM/.js + Biome style, and the offline msw unit test that proves it. Load this whenever building, extending, reviewing, or testing a tdmcp tool file under src/tools/** (and its test under tests/unit/**). Use it for every Phase-13 / v0.5.0 feature-build tool and any re-run after a gate failure.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.
日本語の概要は準備中です。原文の説明を表示しています。
Open the AOS Hub on 127.0.0.1:7900 (services, plan kits, store) or stop/status it. Generated from plugin-commands.json; invoke as $bdb-aos:hub.
日本語の概要は準備中です。原文の説明を表示しています。
Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updates, dry-run CLI shape, or follow-ups that revise this contract.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Idea to published-ready content: brief, script, render routed through the Creator Extension content-studio skill (Hyperframes or Remotion), then a social pack. Use for "make a reel", "idea to video", "content from this idea", "script and render a clip".
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.
日本語の概要は準備中です。原文の説明を表示しています。
Hand work down the chain master session, project orchestrator, package orchestrator. Use when the human asks how to split work across levels, which channel connects them, or what each level may do. A convention mapped onto existing mechanisms, not a new tool. GO is never inherited.
日本語の概要は準備中です。原文の説明を表示しています。
Generate, scaffold, validate and lint Makefiles and .mk files: .PHONY targets, build automation, common mistakes. Use for any Makefile work.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for finding interrupted coding runs and reporting resume candidates. Use after an agent host restart or an interrupted automation; resuming anything needs the user's literal GO.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for monitoring explicitly authorized delivery tasks and reporting stalled work. Report-only: findings are produced in the session or as a draft; no scheduled action is taken.
日本語の概要は準備中です。原文の説明を表示しています。
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or drafting proposed host automations for report-only review.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
日本語の概要は準備中です。原文の説明を表示しています。