Results for “thinking”

Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.

The English summary is being prepared. Showing the original description.

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

The English summary is being prepared. Showing the original description.

Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.

The English summary is being prepared. Showing the original description.

Use for lateral thinking, or when ideas feel stuck or incremental: "we've tried everything", "need a surprising angle", "break the pattern", "give me a wild idea that could work". Uses provocations and reframes. Skip for rule lookups or strict logical proofs.

The English summary is being prepared. Showing the original description.

Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.

The English summary is being prepared. Showing the original description.

Use for systems thinking, or when a change may ripple beyond its target: "what are the side effects?", "why does this keep coming back?", "how do these teams or services affect each other?". Maps loops, delays and leverage points. Skip for single-step fixes.

The English summary is being prepared. Showing the original description.

Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.

The English summary is being prepared. Showing the original description.

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

The English summary is being prepared. Showing the original description.

Use for strategic thinking, or when the user must choose a direction under constraints: "where should we focus?", "how do we win?", "roadmap for next year", "what should we not do?". Ends in explicit bets and risks. Skip for step-by-step implementation.

The English summary is being prepared. Showing the original description.

Use when the user describes a problem, decision or stuck situation but names no method: "how should I approach this?", "help me think this through", "we can't decide", "where do I start?". Picks the best-fit thinking method and runs it. Skip for plain execution tasks or when a method is named.

The English summary is being prepared. Showing the original description.

Use for first principles thinking, or when the user questions an inherited default: "why do we do it this way?", "is this cost really necessary?", "should we copy what competitors do?". Strips analogies and rebuilds from fundamentals. Skip for convention-following checklists.

The English summary is being prepared. Showing the original description.

Use when stuck on approach, not debugging. Unstick via 7 techniques: simplification, collision-zone thinking, inversion, first principles, via negativa. For debugging use mk:sequential-thinking.

The English summary is being prepared. Showing the original description.

Meta-skill: Structured thinking as a 3-phase workflow. Combines analysis (think), ideation (brainstorm), and decision-making (decide) into one continuous process.

The English summary is being prepared. Showing the original description.

Problem solving and analysis: Structured thinking processes for complex problems. Divide & Conquer, Root Cause Analysis, SWOT, Pareto, and decision heuristics.

The English summary is being prepared. Showing the original description.

TEKION Slide Generator v4 — プレゼンスライド生成（OpenAI GPT-image-2 デフォルト / Gemini 3.1 Flash 両対応）。「スライドを作って」「プレゼン資料」で発動。Markdown/テキスト→デザインガイドライン→並列画像生成→PPTX/PDF。日本語テキスト精度重視の営業資料・提案書はOpenAI、大量生成や実在ブランド/人物はGemini。Visual/Balanced 2スタイル、ロゴ/参考画像、グラウンディング、Thinking制御対応。

The English summary is being prepared. Showing the original description.

Product Inventor e Design Alchemist de nivel maximo — combina Product Thinking, Design Systems, UI Engineering, Psicologia Cognitiva, Storytelling e execucao impecavel nivel Jobs/Apple.

The English summary is being prepared. Showing the original description.

Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?

The English summary is being prepared. Showing the original description.

Claude API (platform.claude.com) の Messages API リファレンス。 streaming (SSE), thinking (adaptive) / preserved thinking / effort, prompt caching, context editing, compaction (on-demand / threshold), structured outputs, Message Batches, token counting, vision / PDF, Files API, citations, embeddings (Voyage AI), errors, rate limits, beta headers, Bedrock / Vertex AI / Foundry 経由アクセス。

The English summary is being prepared. Showing the original description.

Shakes your mental models with critical rigor, challenges assumptions, exposes blind spots, and provides multi-perspective insights as a strict thinking mentor. Deliberately breaks format conventions to stimulate genuine cognitive discomfort. Use when you want to stress-test an idea, shake your mental model, ask to challenge my assumptions, find blind spots, deepen my thinking, or request critical review with phrases like yusaburi or what do you think of this plan.

The English summary is being prepared. Showing the original description.

Think through the consequences of consequences — not just what happens immediately, but what happens next, and next after that, across time. Load when a decision looks obviously good or obviously bad on initial read, when the user is optimising for a short-term outcome that might create a long-term problem, when unintended consequences are a concern, or when deep-thinking diagnoses a second-order frame. Triggers on "what are the downstream effects", "what happens after that", "unintended consequences", "think ahead on this", "long-term vs short-term", or "what comes after that". Based on Howard Marks second-level thinking and Farnam Street mental models. Most powerful for decisions with delayed consequences or systemic effects.

The English summary is being prepared. Showing the original description.

Break a stuck or complex problem into the smallest sub-question that, if answered, unlocks the next step — then answer it and repeat until the path forward is clear. Load when a problem feels genuinely stuck, when reasoning keeps circling, or when deep-thinking diagnoses a Socratic frame. Also triggers on "I keep going in circles", "what is the real question here", "help me reason through this step by step", "unstick my thinking", "recursive questioning", "what is the root question". Based on the recursive Socratic questioning method (EMNLP 2023) which outperforms CoT and Tree-of-Thought on complex reasoning tasks.

The English summary is being prepared. Showing the original description.

スキルを作成・更新・プロンプト改善するためのメタスキル。 **collaborative**モードでユーザーと対話しながら共創し、 抽象的なアイデアから具体的な実装まで柔軟に対応する。 **orchestrate**モードでタスクの実行エンジン（Claude Code / Codex / 連携）を選択。 Anchors: • Continuous Delivery (Jez Humble) / 適用: 自動化パイプライン / 目的: 決定論的実行 • The Lean Startup (Eric Ries) / 適用: Build-Measure-Learn / 目的: 反復改善 • Domain-Driven Design (Eric Evans) / 適用: ユビキタス言語 / 目的: 一貫した語彙 • Design Thinking (IDEO) / 適用: ユーザー中心設計 / 目的: 共感と共創 • Microservices Patterns (Richardson) / 適用: サービス委譲 / 目的: 疎結合な連携 Trigger: 新規スキルの作成、既存スキルの更新、プロンプト改善を行う場合に使用。 スキル作成, スキル更新, プロンプト改善, skill creation, skill update, improve prompt, Codexに任せて, assign codex, Codexで実行, GPTに依頼, 実行モード選択, どのAIを使う

The English summary is being prepared. Showing the original description.

Decision validation and thinking frameworks for startup founders. Use when you need to pressure-test a decision, validate your next steps, think through strategic options, or sanity-check your approach. Triggers on phrases like "should I", "help me think through", "is this the right move", "validate my thinking", "what am I missing". Covers fundraising, customer development, runway management, prioritization, and crypto/web3 founder challenges.

The English summary is being prepared. Showing the original description.

Operating discipline distilled from Claude Fable 5 for sessions and subagents on weaker models (Opus 4.x, Sonnet 5/4.x, Haiku 4.5) doing agentic coding. Load it at the START of any non-trivial task when not running on Fable 5: debugging, refactoring, changes across 2+ files, or unfamiliar code; and instruct a subagent on Opus/Sonnet/Haiku to read this skill with a non-trivial assignment. Triggers include "think like Fable", "fable-mode", "turn on discipline", "work carefully", dispatching a subagent on a weaker model, and repeated mistakes or rework in the session. NOT needed for trivial edits (rename, typo, one-liner) or purely conversational answers.

The English summary is being prepared. Showing the original description.