「trade-off」の検索結果

Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.

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

Apply MCAF non-functional-requirements guidance to capture or refine explicit quality attributes such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.

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

Configure render settings, compositing nodes, output formats, and execute renders via Cycles or EEVEE engines using Python API or command-line interface. Use when automating render execution for batch processing, configuring quality and performance trade-offs, setting up compositing pipelines for post-processing, generating multiple output formats from a single render, or producing final output for publication or presentation.

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

Use when the user asks to rank deployment platforms and stacks against their product with quantitative trade-offs. Not for source or remote mutation.

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

Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off

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

Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives

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

Correct, idiomatic, high-performance JSON encoding and decoding with github.com/go-faster/jx. Use this skill whenever you write or review jx-based Encode/Decode methods, implement JSON marshaling over jx, use jx.Decoder / jx.Encoder / jx.Writer, or encounter questions about jx buffer safety, Capture, pooling, or Writer vs Encoder trade-offs. Also trigger when the file imports "github.com/go-faster/jx" and you are adding or changing any encoding / decoding logic.

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

Use when a feature or code change made by Claude is complete and the developer wants to confirm they actually understood it before shipping. Triggers on "handoff", "quiz me", "comprehension check", "did I understand this", "verify I read the code", "test my understanding", or after finishing a feature when the developer wants to take ownership of AI-written code. Also triggers on requests for an interactive or clickable quiz ("interactive mode", "let me answer with the mouse", "mode interactif", "je réponds à la souris"). Quizzes the developer on WHERE the logic lives (file/function) and WHY decisions were made (trade-offs, behavior, debugging), with the number of questions scaled to the size of the change. Multiple-choice questions are clickable by default (asked through `AskUserQuestion`) and fall back to typed answers. Points to file:line on wrong answers, allows one retry, then reveals the answer, and ends with a score plus the weak areas to re-read. Conducts the quiz in the developer's language.

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

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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

"Perform break-even analysis to determine the sales volume or revenue needed to cover all costs. Use this skill when the user needs to calculate break-even point, assess margin of safety, evaluate operating leverage, or decide pricing and volume trade-offs — even if they say 'how many units do we need to sell', 'when will we be profitable', or 'what happens if we lower the price'.".

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

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

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

"Calculate safety stock levels to buffer against demand and lead time uncertainty. Use this skill when the user needs to set inventory buffers, determine service level trade-offs, or optimize safety stock across SKUs — even if they say 'how much buffer inventory', 'stockout prevention', or 'service level calculation'.".

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

Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve scheduled triggers, reduce KVS writes, move work to the frontend, use bridge APIs, batch API calls, add caching, or evaluate Forge Remote trade-offs. By default, perform an audit first and offer to make the recommended changes after presenting the audit. Only modify files immediately when the user explicitly asks the agent to implement or apply optimizations.

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

Use when behavior-preserving frontend refactoring focuses on function API shape, flags, dependencies, mutability, construction, or command/function trade-offs, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.

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

Use when a task needs the judgment of a Business Teacher, Postsecondary — grading case analysis on the rigor of business reasoning rather than matching a single "correct" answer, updating stale textbook examples against current market conditions rather than teaching them as still-current, distinguishing taught analytical frameworks from personal business opinion presented as universal fact, and preserving the incomplete-information trade-offs of real business decisions rather than simplifying problems into false certainty.

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

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

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

Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".

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

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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

User asks for design, planning, or approach exploration before implementation. Covers new features, components, refactors, or architecture decisions. Creates design docs and proposes approaches with trade-offs.

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

Dr. Kaia Chen - AI Architect, mentor, and strategic advisor for Marcus. Use when the user says "Kaia", "Dr. Chen", "ask Kaia", "/kaia", or wants architectural advice, trade-off analysis, production readiness guidance, mentorship, a voice of reason, or a second opinion on design decisions. Kaia grounds her advice in the actual codebase (via Chen MCP tools) and research literature, and logs important decisions and insights via Simon.

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

Relentless delivery mode for complex, multi-step tasks. Use when: multi-file features, unclear root cause debugging, multi-angle research, architecture decisions with trade-offs. Activates parallel subagent dispatch and strict verification.

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

Researches and compares free and open source software projects in a supplied domain, using either user-named candidates or a discovered shortlist. Use when evaluating FOSS alternatives, comparing GitHub popularity, maintenance, licences, domain fit, trade-offs, or producing a linked HTML comparison report.

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

Multi-agent collaboration bringing 2-4 perspectives into one discussion for architecture decisions and trade-off analysis. Use for 'should we X or Y', design review, or debate before deciding.

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

Answer factual project questions (codebase, architecture) with cited evidence. NOT for brainstorming, trade-offs (mk:party), debugging (mk:investigate), review (mk:review), or plans (mk:plan-creator).

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