4,690 件 ・ 関連度順
概要と使いどころ
CRISP Execute — Sprint execution loop with change request management, security gates, product gates, and stakeholder reporting. Use after Phase S (Spec) is complete and crisp-state.json shows ready_for_execute: true. Triggers on "start sprint", "begin build", "execute", "sprint 1", "run sprints", or when handed off from crisp-orchestrator.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Adds new visual examples to the tdmcp prompt cookbook documentation — both the English and Portuguese versions. Use when asked to: add more cookbook examples, create visual examples for the docs, show more surprising things you can do, add entries to the prompt cookbook, expand the cookbook, or any request to extend the cookbook with new prompts and results. Runs a 3-phase pipeline: curate candidates → write EN → write PT.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates the AI-Controlled Party mixer/Soundcraft Ui24R design team. Use whenever the user wants to design, update, refine, re-run, or implement-plan the Soundcraft Ui24R scene-arming expansion, mixer-aware AI party, operator-approved mixer cues, snapshots/cues/show control, Companion bridge, or any follow-up based on prior mixer design results. Produces a spec for tdmcp-pipeline; does not implement runtime code.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Scout ONE external surface of the TouchDesigner community for what's HYPED in 2025-2026 that could become a tdmcp tool. Use when a td-trend-scout sub-agent is assigned a surface (community-showcase, tutorials, generative-ai, hardware-interactive, or vfx-aesthetics) during the tdmcp-hype-scout harness — produces `_workspace/hype-scout/01_scout_<surface>.md` with cited trend candidates ranked by hype intensity, recency, and build-ease in tdmcp.
日本語の概要は準備中です。原文の説明を表示しています。
host chinese call of cthulhu and similar investigative tabletop rpg sessions as kp/keeper. use when the user asks to start, continue, simulate, or play a coc scenario, wants chatgpt to be kp, asks for preset investigator cards, npc teammates, dice checks, horror investigation pacing, solo/co-op tabletop roleplaying, or persistent pre-session prep/project folders for a campaign. ask only the minimum setup questions: whether the user wants a custom investigator persona and how many npc teammates; otherwise handle scenario selection, character card creation, npc teammates, dice, pacing, narration, and campaign notes automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Build Cadmus on Linux and macOS hosts using xtask. Use when asked how to compile, test, lint, or run the project locally.
日本語の概要は準備中です。原文の説明を表示しています。
Run clippy locally and report only issues in the current diff, matching the CI reviewdog flow. Use when asked how to lint changed code or get clippy feedback on a branch before pushing.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and /level-up (finds one automation to build). Trigger on "/weekly", "weekly review", "weekly planning", "how did this week go", "plan my week".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says 'run a sale', 'discount this category', 'set up a coupon', 'reprice these products', 'end the sale', or asks what a discount would cost them. Plans the price change, shows it as a preview before anything moves, writes it with a snapshot, and can put it back.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse-engineer the hook from a viral Threads post or thread URL. Identifies which of the 10 canonical 2026 Threads formulas it uses (warm contrarian, data-point, build-in-public, quote-post, mini-list, relatable, listicle, story, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal (replies, reposts, likes, quotes). Use to learn from a post you admire. Not for writing your own (use threads-post-writer).
日本語の概要は準備中です。原文の説明を表示しています。
Draft a single Threads post or a multi-post thread using a 2026 Threads hook formula (warm contrarian, data-point, build-in-public, quote-post, mini-list, relatable, listicle, story, curiosity-gap, how-I teardown), picked by goal (replies, reposts, likes, quotes). Respects the 500-char limit and one-hashtag cap, runs the humanizer pass, and publishes via Publora, which auto-splits long content into a thread. Not for auditing a draft (use threads-humanizer) or hook teardown (use threads-hook-extractor).
日本語の概要は準備中です。原文の説明を表示しています。
Remove the AI tells readers react to in a Threads post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity. Also --mode audit (500-char fit, hook, hashtag cap), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the numbers, turning points and stories posts are made of). Not for writing from scratch (use threads-post-writer). Keywords: humanize, de-AI Threads post, interview me, audit before posting.
日本語の概要は準備中です。原文の説明を表示しています。
Rates any SKILL.md on a 0-100 scale across 10 dimensions with a SHIP / REWORK / SCRAP verdict. Evaluates trigger precision, instruction clarity, output predictability, edge case coverage, anti-hallucination guardrails, developer experience, composability, open-source readiness, wow factor, and real-world utility. No flattery — calibrated against Anthropic's own skill-creator rubric. Use this skill whenever someone says "score this skill", "rate my skill", "is this skill good", "skill review", "skill audit", "roast my SKILL.md", "grade this", "will this skill work", "evaluate my skill", "how good is this", or pastes a SKILL.md and asks for feedback. Also trigger when comparing two skills, benchmarking a skill collection, or asking "what's wrong with this skill" — even without the word "score".
日本語の概要は準備中です。原文の説明を表示しています。
Trace execution time of Python method invocations in a live process with call stack visualization. Use this to see a hierarchical call tree showing which sub-calls are slow and where time is spent within a function.
日本語の概要は準備中です。原文の説明を表示しています。
Display input/output args, return object and cost time of a Python method invocation in a live process. Use this to observe function behavior at runtime — see what arguments go in, what comes back, and how long it takes. This is the most frequently used diagnostic command.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative reference for working with the released Wandelbots NOVA API v2 in the wandelbots-nova Python SDK. Use whenever a task touches the NOVA API, the generated `wandelbots_api_client` models (`nova.api.models.*`), motion planning requests (`plan_trajectory`, `MotionGroupSetup`, `LimitSet`, `LimitsOverride`), robot limits, or torque/velocity/acceleration/jerk limits. Reach for this skill before guessing field names or assuming a field exists — the installed client reflects the RELEASED API, while nightly specs may contain unreleased fields. Especially relevant for controller-reported limits (e.g. KUKA torque) and any "does field X exist / how is it forwarded to the planner?" question.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "buy token", "sell token", "swap token", "trade crypto", "check trade status", "query transaction", "scan tokens", "feed", "monitor chain", "query token", "token details", "check token safety", "list wallets", "show wallets", "my wallets", "AI scan", "AI扫链", "auto scan", "smart scan", "tweet scan", "推文扫链", "twitter scan", "onboarding", "get started", "check IP", "get IP", "IP whitelist", "查IP", "IP白名单", "launch token", "create token", "发币", "创建代币", "auto sell", "stop loss", "take profit", "trailing stop", "止盈止损", "移动止损", "holders", "top holders", "kol holders", "insider", "持仓", "持仓列表", or mentions trading on Solana/ETH/BSC/Base chains via XXYY. Enables on-chain token trading and data queries through the XXYY Open API.
日本語の概要は準備中です。原文の説明を表示しています。