「alternatives」の検索結果

Analyzes buyback program design with timing optimization, price sensitivity, and EPS accretion impact modeling. Use when optimizing buybacks, modeling repurchase economics, or comparing return-of-capital alternatives.

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

Structures exchange offers, consent solicitations, and amend-and-extend transactions as Chapter 11 alternatives. Use when managing out-of-court workouts, designing exchange offers, or structuring pre-negotiated deals.

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

Evaluates 363 sale processes with stalking horse protections, bid procedures, and credit bidding mechanics. Use when analyzing 363 sales, structuring stalking horse bids, or evaluating asset sale alternatives.

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

Socratic design refinement before implementation — challenges assumptions, surfaces alternatives, identifies risks before code is written

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

Use when a product idea needs pressure-testing against alternatives, category, urgency, and distribution.

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

Use when a B2B SaaS product needs upstream positioning or messaging clarity — defining who it's for, the category, competitive alternatives, differentiation, value props, strategic narrative, or a messaging hierarchy. Triggers include "my messaging isn't working," "we sound like everyone else," repositioning, or auditing an existing positioning doc. Use before homepage, deck, or sales-narrative work. Not for writing the final copy (use copywriter-skill) or running the sales process (use sales-skill).

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

AI solution exploration using ant colony optimization — deploying scout hypotheses, reinforcing promising approaches, detecting diminishing returns, and knowing when to abandon a strategy. Use when facing a problem with multiple plausible approaches and no clear winner, when the first approach is not working but alternatives are unclear, when debugging with no obvious root cause requiring parallel hypothesis investigation, or when previous attempts have converged prematurely on a suboptimal approach.

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

Implement circuit breaker logic for agentic tool calls — tracking tool health, transitioning between closed/open/half-open states, reducing task scope when tools fail, routing to alternatives via capability maps, and enforcing failure budgets to prevent error accumulation. Separates orchestration (deciding what to attempt) from execution (calling tools), following the expeditor pattern. Use when building agents that depend on multiple tools with varying reliability, designing fault-tolerant agentic workflows, recovering gracefully from tool outages mid-task, or hardening existing agents against cascading tool failures.

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

Testing Vue 3 SPAs: Vitest + @vue/test-utils, RTL-style alternatives, Pinia testing via createTestingPinia, composable testing, msw for network mocks, Cypress component testing, Playwright e2e. Use this skill to: - Set up Vitest for Vue 3 with jsdom + @vue/test-utils. - Pick mount vs shallowMount. - Test components by props/emits/slots contract. - Mock Pinia stores in tests. - Test composables in isolation. - Set up Playwright or Cypress for end-to-end. Do NOT use this skill for: - General Vue conventions (see vue-conventions). - State patterns (see vue-state-management). - Form-specific patterns (see vue-forms).

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

Cofold protein-ligand, protein-protein, and nucleic-acid complexes with Boltz-2, and predict binding affinity with its trained affinity head. Use this skill to build Boltz input YAML, run structure prediction with MSAs, pocket constraints, templates, and modified residues, screen compound libraries by cofolding, and interpret confidence scores (pLDDT, pTM, ipTM, PDE) and affinity output (binder probability and log10 IC50). Also trigger on Boltz, Boltz-1, Boltz-2, cofolding, boltz predict, affinity_pred_value, affinity_probability_binary, ipTM, or open-weights AlphaFold3 alternatives.

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

Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.

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

Continuous self-reflection routine combining Schön (reflection-in-action / reflection-on-action) and Mezirow (content / process / premise) levels, anchored on KAMI values (val-002 глубина, val-007 честность перед собой, принцип 1 правда, принцип 2 нулевая толерантность к бреду). Triggers FIRE DURING THE TURN, not at end. Use when: (1) about to make a 2nd+ patch attempt at the same problem, (2) user pushes back with "стоп / нет / опять / так, ещё раз / не то / пиздёж", (3) noticing self drifting into "I think that..." without evidence, (4) about to report "готово", (5) copying a pattern from one place to another, (6) task took >2× expected time. Embeds scientific method (explicit hypotheses + falsifiability + prediction-first + alternatives) as substrate for premise-level reflection, not as ceremony.

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

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

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

You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.

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

"Habitual Domain (HD) theory by Taiwanese scholar P.L. Yu (游伯龍, 1977) — integrates four domains (potential/actual/reachable/activated), eight general hypotheses, seven-layer decision structure, and nine HD-expansion tools to analyze decision blind spots, break cognitive inertia, and support cross-domain integration. Use for diagnosing why alternatives are invisible, decision paralysis, breaking cognitive frames, or explaining perception gaps between people. Triggers: 『思維框架』『打破盲點』『創新思考』『決策盲區』『跨域整合』『游伯龍』『習慣領域』『HD 理論』『七層決策』『四領域』『八大通性』『P.L. Yu』. Especially for NYCU EMBA HD course, 政大科管所, 中山企管系 decision-analysis/innovation/leadership courses. Taiwan-origin theory cited in J. Optimization Theory, Theory & Decision, Human Systems Management.".

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

"Apply Granovetter's embeddedness theory to analyze how economic behavior is embedded in ongoing social relations, avoiding both over-socialized and under-socialized accounts. Use this skill when the user needs to explain why market transactions deviate from pure economic rationality, analyze how trust and social ties shape business dealings, evaluate structural vs relational embeddedness in inter-firm networks, or when they ask 'why do firms prefer existing partners over cheaper alternatives', 'how do social relationships shape economic outcomes', or 'is this market truly arms-length'.".

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

"Apply Christensen's Disruptive Innovation theory to assess low-end and new-market threats to incumbents. Use this skill when the user needs to evaluate whether a new entrant poses a disruptive threat, analyze why incumbents fail against inferior-but-cheaper alternatives, or design a disruption strategy targeting overserved customers.".

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

Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.

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

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

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

Use when a task needs the judgment of an Environmental Restoration Planner — screening or comparing CERCLA/RCRA remedial alternatives against the nine evaluation criteria, building a life-cycle cost estimate for a Feasibility Study, scoping a stream or wetland restoration design against a reference reach, sizing compensatory mitigation credits, drafting a Statement of Work or Remedial Action Work Plan, or scoping a Five-Year Review for a site with land-use controls in place.

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

Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

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

Apply classic design patterns judiciously: when each pattern fits, modern alternatives, and anti-patterns. Use when designing object interactions or reviewing pattern usage.

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

Full design improvement pipeline — syncs your app to Google Stitch, generates alternatives, presents side-by-side comparison, and adopts cherry-picked improvements. Triggers: 'stitch pipeline', 'improve my design with stitch', 'make my app look better', 'stitch redesign everything'.

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

Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis".

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