1,226 件 ・ 関連度順
概要と使いどころ
Customer discovery framework using Jobs-To-Be-Done theory — uncover the functional, social, and emotional jobs customers hire products to do. Produces JTBD canvases with job statements, outcome metrics, and competing solutions. Use alongside cm-brainstorm-idea for evidence-based product decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Manage and tag music libraries with beets, the Python-based CLI tool that auto-tags audio files using MusicBrainz metadata. Import, organize, deduplicate, and query your music collection with a powerful plugin system and flexible query language.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Survey the whole tdmcp project and produce a prioritized list of NEW features it could implement — across artist controls, CLI/DX, AI/LLM integration, and TouchDesigner depth. Use whenever the user wants to brainstorm, discover, survey, list, or audit what features/tools/effects/controls/commands/prompts/capabilities tdmcp *could* add, asks 'what could we build / what's missing / what are the opportunities / ideas for the project', or wants a feature backlog or gap analysis. Also for follow-ups: re-run, refresh, update, re-survey, deepen, or re-prioritize the backlog, or survey just one surface (e.g. 'CLI ideas only'). This is the IDEATION harness — it produces a list to decide from; it does NOT build. When the user has already chosen a feature and wants it implemented/shipped/added, use tdmcp-pipeline instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user brings an external source worth keeping — a URL, a paper, a tweet/thread, a blog post, a docs page — and wants it pulled into the second brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy, then refreshes the knowledge graph so it joins the rest of your thinking. Trigger on "/graph-ingest", "ingest this url", "add this paper to my knowledge", "add this tweet/page to my knowledge", "capture this source".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to build, refresh, or visualize the repo's knowledge graph — code structure plus the committed wiki/ — via graphify. Produces an interactive graph + a GRAPH_REPORT.md of God Nodes, surprising connections, and suggested questions. Trigger on "/graph", "build the knowledge graph", "graph the repo", "map the codebase", "refresh the graph", "visualize the second brain".
日本語の概要は準備中です。原文の説明を表示しています。
解除大脑的两道封印（负面词语和负面情绪），恢复理性思考能力。适用于面对压力、挫折、冲突时大脑"宕机"无法思考的场景，以及长期的思维模式优化。当你陷入"我不行"、"做不到"、"没办法"的自我否定循环，或被愤怒、焦虑、恐惧等情绪淹没时使用此skill。不适用于需要深度心理治疗的精神健康问题（如抑郁症、焦虑症需专业医疗），也不适用于纯粹的知识学习瓶颈（那是方法问题不是封印问题）。关键触发信号："我不行/我做不到"、"气死我了/急死了"、"脑子一片空白"、"越想越烦"、"控制不住自己"。
日本語の概要は準備中です。原文の説明を表示しています。
Use to build or update an Opportunity Solution Tree from research data. Never from brainstorming.
日本語の概要は準備中です。原文の説明を表示しています。
Collaborative document creation via a structured three-stage workflow. Use for writing specs, PRDs, design docs, proposals, RFCs, and any long-form document where quality and clarity matter. Brainstorms 5-20 options per section, builds iteratively, and tests with reader sub-agents.
日本語の概要は準備中です。原文の説明を表示しています。
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
日本語の概要は準備中です。原文の説明を表示しています。
Interactive idea refinement using Socratic method to develop fully-formed designs
日本語の概要は準備中です。原文の説明を表示しています。
Use when EZ_math_model model selection is unclear after the modeling decision tree, the problem spans multiple domains, or modeler needs several candidate approaches before writing modeling_plan.md.
日本語の概要は準備中です。原文の説明を表示しています。
Build MindNode-inspired mind mapping interfaces — 8 node shapes, 27+ themes, layout algorithms (horizontal, vertical, radial with D3), keyboard shortcuts, focus mode, dual view. React + xyflow/react v12 + Zustand + Tailwind. Triggers on mind map, visual thinking tool, node-based diagram, brainstorm canvas, MindNode.
日本語の概要は準備中です。原文の説明を表示しています。
Use when uncertainty remains and the minimum useful sequence of questions should be asked.
日本語の概要は準備中です。原文の説明を表示しています。
Use when local validation and remote workflow status must be reconciled before trust, merge, or shipment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs a standup-ready summary of recent project activity from local evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a launch needs a go/no-go decision with rollback and monitoring evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verification depends on agent runtime phases, queued input, tool-call lifecycle, save points, retry, abort, compaction, or branch behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding what project context should be remembered, retrieved, updated, or deliberately forgotten.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an engineering plan needs pressure-testing for architecture, complexity, data, risk, and operability.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a command, adapter, or runtime smoke depends on proving an agent runtime's capabilities before trusting command routing, writes, shell access, or validation claims.
日本語の概要は準備中です。原文の説明を表示しています。