596 件 ・ 関連度順
概要と使いどころ
Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Audit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.
日本語の概要は準備中です。原文の説明を表示しています。
Coach senior leaders on strategic thinking, stakeholder management, presence, and organizational impact.
日本語の概要は準備中です。原文の説明を表示しています。
Build discernment habits: nudges and checklists for evaluating claims, spotting manipulation, and thinking clearly under pressure. Use when you want better judgment about what to believe and share.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the devil's advocate technique: structured critical thinking that stress-tests ideas, plans, and decisions. Use when you need honest critique before committing to something important.
日本語の概要は準備中です。原文の説明を表示しています。
Anthropic Claude API guidance — messages API, tool use, prompt caching, extended thinking, and production patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Excalidraw architecture diagrams (.excalidraw JSON files) from your codebase. Triggers: you need whiteboard-style sketches that read as a thinking artifact rather than a polished spec — ideal for design.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether your leadership behaviors amplify or diminish your team using Liz Wiseman's Multipliers framework. Use when a leader asks "am I a good manager", "why isn't my team performing at their potential", "I feel like I'm doing all the thinking for my team", "my team seems dependent on me", "I want to be a better leader", "how do I empower my people", or "my team is smart but underperforming". Also trigger when someone describes always having the best ideas in the room, team members not taking initiative, reports waiting for direction before acting, or a leader who feels exhausted from carrying the team. Diminisher patterns are often invisible to the leader exhibiting them.
日本語の概要は準備中です。原文の説明を表示しています。
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
日本語の概要は準備中です。原文の説明を表示しています。
Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification
日本語の概要は準備中です。原文の説明を表示しています。
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.
日本語の概要は準備中です。原文の説明を表示しています。
Timeboxed ideation on a topic where lens-driven proposers generate structurally different ideas, blind critics cull them, and pairwise judges rank the survivors on a tournament ladder instead of 1-10 scores, evolving the leaders until the clock runs out. Use when the user wants to brainstorm, explore ideas, discover features, generate options, or think through possibilities for a specified duration. Triggers on requests like "brainstorm X for 30 minutes", "ideate on X", "spend an hour thinking about X", "what features should we build", "explore options for X". Not for executing a task over time (timeboxed-iterating) or optimizing a measurable metric (autoresearch).
日本語の概要は準備中です。原文の説明を表示しています。
Game theory expert covering Nash equilibrium, strategic thinking, auction theory, and cooperative games
日本語の概要は準備中です。原文の説明を表示しています。
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
日本語の概要は準備中です。原文の説明を表示しています。
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
日本語の概要は準備中です。原文の説明を表示しています。
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
日本語の概要は準備中です。原文の説明を表示しています。
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
日本語の概要は準備中です。原文の説明を表示しています。
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode scope review. Challenges the scope of any plan, workflow, or feature before execution. Four modes: SCOPE EXPANSION (dream bigger), SELECTIVE EXPANSION (cherry-pick worthwhile expansions), HOLD SCOPE (maximum rigor within current scope), SCOPE REDUCTION (strip to essentials). Use before executing any multi-step workflow or when questioning whether the scope is right. Prevents scope creep and missed opportunities. Use proactively when the user defines a plan, creates a workflow, or says "is this enough?" or "am I thinking too small?".
日本語の概要は準備中です。原文の説明を表示しています。
Broadcast agent activity status to Discord channel (thinking, tool use, web search, coding, done, error). Use for transparency so users know agent is working.
日本語の概要は準備中です。原文の説明を表示しています。