「inversion」の検索結果

Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.

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

当用户面临复杂决策、规划或问题解决时激活——尤其是正向推理陷入困境、选项过多无法判断优先级、或需要识别隐藏风险时。典型触发信号：用户在问"怎么才能成功""如何避免失败""我应该怎么做"时卡住了。不适用于已有明确最佳路径且只需执行的简单任务,也不适用于需要创意发散而非风险规避的场景。

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

Classify gate call variants in a minified JavaScript bundle. Covers context-window extraction around a flag occurrence, identification of 4–6 reader variants (sync boolean, sync config-object, bootstrap-aware TTL, truthy-only, async bootstrap, async bridge), default-value extraction (boolean / null / numeric / config-object literal), conjunction detection across `&&` predicates, kill-switch inversion detection, and production of a gate-mechanics record that feeds probe- feature-flag-state. Use when a flag's behavior cannot be inferred from its name alone, when the binary uses multiple reader libraries, or when config-object gates carry structured schemas distinct from boolean gates.

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

Find the route to guaranteed failure, negate it. Use when a goal keeps not being reached head-on.

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

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

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

Execute sophisticated Data Extraction and Privacy Leakage attacks explicitly against Large Language Models (LLMs) to natively force the neural network entirely into organically regurgitating exact, verbatim strings of Highly Confidential Personally Identifiable Information (PII), proprietary source code, or copyrighted material categorically memorized intrinsically during its foundational pre-training phase.

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

AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.

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

Opt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, and service layers. Only activates when ProjectConfig.yaml -> architecture_pattern is "di-first". For simpler projects, use uw-scriptable-object-arch instead.

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

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

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

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

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

Problem redefinition before problem solving. Takes a stated problem, extracts its premises, then spawns reframers applying different lenses (problem-vs-symptom, scope-shift, stakeholder-shift, level-of-abstraction, time-horizon, inversion, category-shift, constraints-shift) in isolation, and synthesizes the alternatives into a report with an orchestrator recommendation. Produces feedback only — no code, no tickets, no artifacts.

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

Use when stuck on approach, not debugging. Unstick via 7 techniques: simplification, collision-zone thinking, inversion, first principles, via negativa. For debugging use mk:sequential-thinking.

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

Structured second-pass reasoning after a review or plan verdict: pre-mortem, inversion, red team, Socratic lens, etc. NOT for initial review (mk:review) or new plans (mk:plan-creator).

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

Use when stuck on approach (not debugging). Strategic unsticking via 7 non-default techniques: simplification cascades, collision-zone thinking, meta-pattern recognition, inversion, scale game, first principles, via negativa. Triggers on complexity spiraling, innovation block, recurring patterns across domains, forced-assumption solutions, scale uncertainty, told-it's-impossible, or bloated systems needing subtraction. For evidence-based root-cause debugging, use mk:sequential-thinking instead.

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

Detect syntenic blocks and structural rearrangements between genomes using MCScanX (Wang 2012), JCVI/MCScan (Tang 2008 Python), GENESPACE (Lovell 2022) for orthology-anchored riparian visualization, SyRI for structural variation, AnchorWave for sequence-level synteny, i-ADHoRe 3.0 for highly diverged species, SynNet for synteny networks, and ntSynt for multi-genome macrosynteny. Use when identifying collinear gene blocks across species, distinguishing macrosynteny from microsynteny, detecting inversions/translocations/duplications, anchoring orthology in WGD lineages, producing publication riparian plots, computing synteny block age via Ks (cross-references whole-genome-duplication), or running synteny-aware ortholog inference in polyploids.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.

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

Use when qualifying or disqualifying a single deal — MEDDIC slots with evidence, inversion test, disqualification heuristic. Triggers on 'is this deal real', 'should we walk away'.

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

Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary.

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

Use when assessing AI/ML systems for prompt injection, jailbreak vulnerabilities, model inversion risk, data poisoning exposure, or agent tool abuse. Covers MITRE ATLAS technique mapping, injection signature detection, and adversarial robustness scoring.

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

Use when designing, implementing, reviewing, debugging, testing, profiling, or porting concurrent, parallel, distributed, high-performance, network dataplane, kernel-bypass, or real-time software, including locks, semaphores, monitors, MPI, CSP rendezvous, DPDK, VPP, eBPF, XDP, AF_XDP, SR-IOV, RSS, RoCEv2/RDMA, RMS/EDF, priority inversion, and environment selection from silicon to edge.

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

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

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

Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.

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

Orders and orients assembled contigs into chromosome-scale scaffolds from long-range linking data, inserting N-gap spacers (adds no sequence). Covers Hi-C/Omni-C scaffolding (YaHS, SALSA2, 3D-DNA/Juicer), Hi-C read-mapping prerequisites (map each end separately, no mate rescue, dedup, enzyme-aware), reading the contact map for misjoins/inversions/false-duplications, manual curation in Juicebox/PretextView (the VGP/DToL standard), reference-guided scaffolding (RagTag) and its karyotype-erasure hazard, genetic-map (ALLMAPS) and Bionano optical-map integration, chimera-breaking before scaffolding, gap-filling, and telomere/contig-vs-scaffold-N50 QC (tidk). Use when turning contigs into chromosomes with Hi-C, integrating a linkage map or optical map, choosing a scaffolder by available linking data, or judging whether a chromosome-scale assembly is trustworthy.

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