「reasoning」の検索結果

When processing code review feedback (bot or human) before changing anything — triages, verifies and pushes back with technical reasoning — even when the user just says 'fix the comments'.

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

Use when reasoning about cash runway — burn shape, fundraise triggers, layoff-vs-cut-vs-grow decisions. Triggers on 'how long do we have', 'should we raise', 'cut or grow'.

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

Use when constructing base / upside / downside scenarios — three-statement modeling, sensitivity analysis, optionality reasoning. Triggers on 'model the scenarios', 'what if growth halves'.

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

Use when designing or auditing a sales pipeline — stage exit criteria, per-cell conversion, coverage reasoning, leak detection. Triggers on 'tighten our pipeline', 'where is the leak'.

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

Use when shaping a capital-raise pitch — why-now / why-us / why-this framing, market-size reasoning, traction-story construction. Triggers on 'tighten the pitch', 'why-now is weak'.

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

Use when mapping competitors, naming defensibility, and finding white-space — moat reasoning, where-to-play, where-not-to-play. Triggers on 'who are we competing with', 'what's our moat'.

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

Orientação especializada para ajuste fino com GRPO/RL usando TRL para treinamento de modelos com raciocínio e tarefas específicas

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

[User-Invoked] Use ONLY when the user explicitly types /dual-ai or /dual-ai <workflow-id> — fans out one prompt, or one workflow invocation per tool, to two fresh parallel AI sessions (Claude Code + Codex CLI), both pre-set to xhigh reasoning effort and full-permission mode before the prompt executes. NEVER auto-activate.

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

Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.

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

技术文本残留评审过程、草稿引用或推理旁白时使用。

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

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

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

Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments, restructure or edit a manuscript, translate Chinese academic text into restrained English, answer reviewers, or run multi-round peer-review convergence without fabricating evidence.

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

System reference for the crouton layout engine (@fyit/crouton-layout) — the LayoutTree/layout_configs data model, the croutonLayoutBlocks registry and sizing contract, the viability metric, the deterministic placer (#709), and how layouts persist and seed. Use when reasoning about WHY a layout renders/composes/persists the way it does, when a question is shaped like "what is a LayoutTree / where do layouts live / why did the placer pick this arrangement / why won't this pane shrink / where does minWidth get read", or when a generated POC boots with the wrong (or no) default layout. Trigger phrases: "layout tree", "layout_configs", "viability check", "composeDefaultLayout", "block sizing contract", "why is my layout not viable". For authoring a block component, use the block-authoring skill instead.

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

Activates a structured decorator framework that modifies how Claude reasons, responds, and formats output. Trigger this skill whenever a prompt contains one or more markers prefixed with +++, such as +++Reasoning, +++StepByStep, +++Tone(style=formal), or any other +++ marker, regardless of what follows in the prompt. Also trigger when the user asks to activate, list, or clear decorators, references the prompt decorator framework, or uses phrases like "use decorator", "apply +++", or "what decorators are available". This skill must be active for any +++ marker to take effect.

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

Use when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.

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

在用户级或项目级检查、验证、显式设置或显式重置 Codex Flight Control 的角色模型与 reasoning effort 策略。仅当用户直接调用 $flight-configure-roles 时使用；禁止隐式触发，也禁止在普通飞控开发流程中顺便修改配置。

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

Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).

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

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

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

Role-based multi-model strategy. The model catalog lives in a local configuration file instead of the skill text -- roles (thinker/decision-maker, long-running worker, draft generator, reviewer/acceptance, escalation), reasoning effort as an independent axis, mandatory review for draft models, provider switching for independent reviews, budgets, delegation flow, and cost/quality of small workers.

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

Rollenbasierte Multi-Modell-Strategie. Modellkatalog liegt in einer lokalen Konfigurationsdatei statt im Skill-Text -- Rollen (Denker/Entscheider, Dauer-Worker, Entwurfsgenerator, Reviewer/Abnahme, Eskalation), Reasoning-Effort als eigene Achse, Abnahmepflicht für Entwurfsmodelle, Anbieterwechsel für unabhängige Reviews, Kontingente, Delegationsablauf und Kosten/Qualität kleiner Worker.

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

Send one research question to as many independent LLMs as possible at once, each in its strongest reasoning mode with proof of that mode, then synthesize. Floor of 3 models, quorum of 4; late answers are collected later. Use for high-stakes questions where one model's view is not enough. Triggers: /hyper, hyper research, ask every LLM, max fan-out research.

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

Decide-as-cofounder mode: the owner hands over the decision itself, so the agent does not ask back, does not offer a menu of options and does not wait, but picks, acts and reports the call with its reasoning. Triggers: /decide, /ds, decide yourself, your call, up to you, you know better, do as you see fit.

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

AI-powered design intelligence with 67 UI styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 15+ tech stacks. Generates complete design systems for any product type with industry-specific reasoning rules.

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

Use OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.

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