130건 · 관련도순
Full-spectrum product research pipeline. Runs competitive analysis, technology trend scouting, user feedback analysis, and feature ideation. Triggers: on: research, competitive research, market research, feature discovery, what should we build next.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstorm), extracting user intent (elicit), or reviewing already-written code (quality-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research and ideation partner for GAME DESIGN — think through design ideas before writing them into the GDD; produces a brief, never edits the GDD itself. Use to assess a genre or market for viability, dissect a reference game (mechanics → dynamics → aesthetics), explore how to improve or extend an existing system, flow, or content type, research new mechanics the design lacks, investigate a part of the GDD in code, or develop the research bucket of a /unikit-gd-review report into decided edits. Trigger on "explore how to improve the flow", "ways to improve the combat system", "is this genre saturated", "break down the combat of Hades", "work out the review's open questions". GAME-DESIGN research only — for CODE or technical research use /unikit-explore; to reconstruct a design from code use /unikit-gd-recon; to write a change into the GDD use /unikit-gd-system or /unikit-gd-spec; to apply edits you know use /unikit-gd-apply; to invent a new game use /unikit-gd-brainstorm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run before implementing UI — research real product patterns (Refero/Mobbin MCP), pick a design direction, and output tokens or a short DESIGN.md before writing code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find question-based Google Autocomplete suggestions for any topic. Prepends question modifiers (what, how, why) to a seed topic and returns real autocomplete suggestions — useful for AEO prompt research, content ideation, and understanding what people ask about a topic. Use when the user wants to discover questions people search for, find content angles, or do keyword/prompt research for a topic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols. Implements suicide ideation detection, automated escalation, and crisis resource integration. Use for mental health apps, recovery platforms, support communities. Activate on "crisis detection", "suicide prevention", "mental health NLP", "intervention protocol". NOT for general sentiment analysis, medical diagnosis, or replacing professional help.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rapidly generate up to 25 distinct ad creative hypotheses for testing. Produces a matrix of angles (pain, benefit, social proof, urgency, curiosity, comparison) x formats (static, carousel hook, UGC-style, bold-text overlay) with headline, visual prompt, and rationale for each, then generates the visuals with any image tool. Use when the user wants "ad variations", "ad concepts", "creative testing batch", "give me 25 ads", or paid-social creative ideation. Part of the Creative Production set.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate project ideas via creative constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates ideas with named methods from creative practice (SCAMPER, lateral provocations, constraints, pataphysics, and more), routed to the user's situation. Use for open-ended generative or selective requests: "I want to make or start something", "I'm stuck", "inspire me", "make this weirder", "help me pick", or inventing a research question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Exploratory data-migration validation and QA ideation workflow. Use when you need to discover hidden risks, generate new validation angles, and converge mapping specs/validation reports into a prioritized QA backlog for CRM migrations. Version 2.0, updated 2025-12-28.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate ideas via named methods from creative practice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Meta-skill: Structured thinking as a 3-phase workflow. Combines analysis (think), ideation (brainstorm), and decision-making (decide) into one continuous process.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft IA shard sections from reconciled ideation and architecture sources, with write-as-you-go section locking
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Exhaustive idea extraction through recursive breadth-before-depth exploration with Deep Think protocol and fractal structure. Use during /ideate to transform raw ideas into comprehensive, structured ideation output. Writes to a fractal folder hierarchy — every node has an index, CX file, and children.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define system architecture, error architecture, and data strategy with map guards and ideation context reload
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate ideation completeness through constraints, exhaustion, rubric checks, and output compilation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute recursive breadth-before-depth ideation discovery with Deep Think, CX gate enforcement, and feature deepening
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end Android indie idea workflow — feature-build phase only (no monetization). Phased — discover (if no idea) → generate 2 candidates → refine scope (offline/online, sharing, MVP vs full, core-value features) → risk/reward/tradeoff analysis when scoping down → emit idea brief. Use for greenfield app concepts, new feature ideation, idea discovery, or pre-design discovery before writing a design document. Triggers — new app idea, feature concept, indie dev brainstorm, validate idea, refine idea, what should I build, find an app idea, idea pipeline, I have no idea, help me find an app idea, scope down, MVP scoping, core value features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Combines multi-agent brainstorming, the /grill-me slash command, and the 3 Core Godmodes (godmode-engineering, godmode-ui-ux, godmode-shipping) to force a comprehensive, multi-agent ideation and technical design workflow, ending in a plan-canvas review and a hand-off to /startcycle-graph. Use when the user asks to brainstorm, ideate, design, scope or sharpen a plan, idea or product, or when broad exploration before a build is the situation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.