「thinking」の検索結果

When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.

日本語の概要は準備中です。原文の説明を表示しています。

Before heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.

日本語の概要は準備中です。原文の説明を表示しています。

When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the reflex is to add a feature, layer, or process. Prefer removing harmful or nonessential elements first, with an irreversibility guard before deletion.

日本語の概要は準備中です。原文の説明を表示しています。

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

日本語の概要は準備中です。原文の説明を表示しています。

Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.

日本語の概要は準備中です。原文の説明を表示しています。

Use when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.

日本語の概要は準備中です。原文の説明を表示しています。

For authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.

日本語の概要は準備中です。原文の説明を表示しています。

Use under time pressure when the situation is still changing and you must act before certainty — cycle Observe→Orient→Decide→Act on ~70% confidence, then re-observe.

日本語の概要は準備中です。原文の説明を表示しています。

When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.

日本語の概要は準備中です。原文の説明を表示しています。

Before rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.

日本語の概要は準備中です。原文の説明を表示しています。

Use when search or investigation could run forever. Set an explicit good-enough threshold first, then stop at the first option that clears it.

日本語の概要は準備中です。原文の説明を表示しています。

When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.

日本語の概要は準備中です。原文の説明を表示しています。

When two design requirements seem mutually exclusive, name the contradiction, separate conflicting states, then invent a concrete no-compromise resolution.

日本語の概要は準備中です。原文の説明を表示しています。

Before committing to a plan or launch, assume it already failed and reason backward through concrete causes — convert failure paths into mitigations, gates, and stop checks.

日本語の概要は準備中です。原文の説明を表示しています。

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

日本語の概要は準備中です。原文の説明を表示しています。

When a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.

日本語の概要は準備中です。原文の説明を表示しています。

The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Universal MCP client for connecting to any MCP server with progressive disclosure. Wraps MCP servers as skills to avoid context window bloat from tool definitions. Use when interacting with external MCP servers (Zapier, Sequential Thinking, GitHub, filesystem, etc.), listing available tools, or executing MCP tool calls. Triggers on requests like "connect to Zapier", "use MCP server", "list MCP tools", "call Zapier action", "use sequential thinking", or any MCP server interaction.

日本語の概要は準備中です。原文の説明を表示しています。

Agnes AI API 接入支持与问题排查 Skill。帮助新用户完成 Agnes AI API 的接入配置， 诊断和解决接入过程中遇到的认证、参数、响应、图像生成、视频生成等各类问题。 涵盖 Thinking 模式开启、视频长度调节、流式输出、工具调用等高级功能指导。 兼容 OpenClaw、Claude Code、Hermes、Codex 等工具链。 thinking、stream、tool calling、模型选择、Base URL、响应格式、timeout、超时、轮询、 FAQ、问题排查、调试、免费调用、RPM、video_id、task_id、Prompt 模板、提示词、 生图、生视频、图生图、文生图、图生视频、文生视频、灰度自检、1M 上下文、4K 图片、4K 图、4K、灰度、自检、反馈、Bug、issue、问题反馈、功能建议。

日本語の概要は準備中です。原文の説明を表示しています。

Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. If you're thinking relationally, you're thinking wrong. 2025 lesson: Firestore pricing can surprise you. Reads are cheap until they're not. A poorly designed listener can cost more than a dedicated database. Plan your data model for your query patterns, not your data relationships. Use when "firebase, firestore, firebase auth, cloud functions, firebase storage, realtime database, firebase hosting, firebase emulator, security rules, firebase admin, firebase, firestore, cloud-functions, serverless, backend, realtime, authentication, google-cloud" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.

日本語の概要は準備中です。原文の説明を表示しています。

Master optimization protocol for Gemini Agent (Antigravity) to unlock native 2M+ to 10M+ long-context reasoning, Gemini 4 Pro & Gemini 4 Flash dynamic thinking budget control, native context caching, Multimodal Live API, and high-speed problem solving / Protokol optimasi utama untuk Gemini Agent (Antigravity) untuk mengaktifkan pemikiran long-context 2M+ hingga 10M+, kontrol thinking budget dinamis Gemini 4 Pro & Gemini 4 Flash, context caching native, Multimodal Live API, dan pemecahan masalah kecepatan tinggi.

日本語の概要は準備中です。原文の説明を表示しています。