980 件 ・ 関連度順
概要と使いどころ
Performs corticotropin stimulation test to diagnose adrenal insufficiency when morning cortisol is indeterminate (3-15 µg/dL). Triggers include morning cortisol 3-15 µg/dL requiring further AI testing.
日本語の概要は準備中です。原文の説明を表示しています。
Capture what someone actually said without contaminating it with your own inference. Invoke when eliciting intent in conversation (design discussion, requirement interview, decision surfacing) and when turning a conversation into a durable record (ADR, decision node, memory entry, spec `## Decisions` row). Enforces quote-before-critique, keeps illustration separate from commitment, and holds interpretation subordinate to verbatim. Prevents the failure where unspecified space is filled by the recorder and then evaluated as if the speaker had specified it.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level numerical methods knowledge. Use when working with root finding, numerical integration, numerical differentiation, interpolation, numerical linear algebra, ODEs, PDEs, or optimization algorithms. Also use when the user mentions 'Newton method', 'bisection', 'Runge-Kutta', 'finite difference', 'finite element', 'interpolation', 'numerical integration', 'quadrature', 'iterative solvers', 'condition number', 'round-off error', or 'truncation error'.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").
日本語の概要は準備中です。原文の説明を表示しています。
Adresse les commentaires de revue sur les PR (humain + bots). Mode auto-détecté selon le type d'issue. Usage: /review [<issue#>|<PR#>]
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
日本語の概要は準備中です。原文の説明を表示しています。
Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
日本語の概要は準備中です。原文の説明を表示しています。
Force plan, HLD, ADRs, and constraints to exist BEFORE any code is generated. Trigger when starting a new feature, epic, or significant change.
日本語の概要は準備中です。原文の説明を表示しています。
Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.
日本語の概要は準備中です。原文の説明を表示しています。
Generate architecture and design documents for implemented code changes with risk-based depth selection. Automatically evaluates risk signals, layer spread, and change magnitude to choose documentation level (A/B/C). Use after completing a feature, before merging a PR that touches multiple layers or sensitive areas (auth, infra, migrations, payments), or when an implemented change needs a design record or ADR.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write a spec", "create RFC", "write a PRD", or "document this decision". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repo has its own generators, scripts or turbo tasks and an agent reaches for a generic skill instead — derive a Playbook context (ADR-244) from the real config, graded by the tree.
日本語の概要は準備中です。原文の説明を表示しています。
Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices.
日本語の概要は準備中です。原文の説明を表示しています。
Analisa seu histórico recente de chats do Claude Code para identificar padrões de codificação, lacunas no desenvolvimento e áreas para melhoria, seleciona recursos de aprendizagem relevantes do HackerNews e envia automaticamente um relatório de crescimento personalizado para suas DMs do Slack.
日本語の概要は準備中です。原文の説明を表示しています。
Escreva código C# moderno com recursos avançados como records, pattern matching e async/await. Otimiza aplicações .NET, implementa padrões empresariais e garante testes abrangentes.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões de banco de dados ClickHouse, otimização de consultas, analytics e melhores práticas de engenharia de dados para cargas de trabalho analíticas de alto desempenho.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões de arquitetura backend, design de API, otimização de banco de dados e melhores práticas server-side para Node.js, Express e rotas de API Next.js.
日本語の概要は準備中です。原文の説明を表示しています。