Results for “fallout”

Analyzes multi-step conversion funnels in Adobe Analytics to identify visitor drop-off points, compute step conversion rates, and pinpoint the worst leakage steps.

Use this skill for feature flags, gradual rollout, kill switches, metrics, experiment gates, rollback. Trigger when the task involves programming work related to Feature Flag Rollout, implementation, audits, debugging, strategy, or validation.

Trigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.

Conduz investigação de incidentes com método: triagem, hipóteses, mitigação, RCA e postmortem, priorizando evidências e confirmação humana.

琦玉（少年漫）认知与表达框架（压缩蒸馏）：无敌无聊、一拳解构热血、超市券日常 触发：一拳超人 等。虚构

Designs and executes tabletop breach simulation exercises for testing organizational breach response capabilities. Covers scenario creation with realistic inject timelines, participant role assignment, communication testing across internal and external channels, decision-point evaluation, and after-action report generation. Keywords: tabletop exercise, breach simulation, incident response testing, scenario design, after-action report.

葛优（演员）认知与表达框架（压缩蒸馏）：蔫坏冷面、话少留白、小人物体面与大谎 触发：甲方乙方、活着 等。虚构创作谈

贾宝玉（古典虚构）认知与表达框架（压缩蒸馏）：情不情、反仕途经济、女儿崇拜叙事… 触发：红楼梦 等。虚构；非性别刻板侮辱

Error Recovery Playbook

`analysis-agent`/`task-agent`/`review-agent`: use when retryable, terminal, timeout, partial-failure, or fallback semantics change across boundaries; skip unchanged failures.

Trigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.

Reconstruct a product flow, then audit how usable it is — whether it makes sense, where users get confused or stuck, whether the copy and instructions are clear, and where friction causes drop-off. Produces a prioritized, severity-weighted findings report. Works from three inputs: frontend code in a repo, a live running app driven via a browser, or a written flow / spec / screenshots. Use this skill whenever the user asks for a UX review, usability audit, "is this flow confusing", "does this signup/onboarding/checkout make sense", "why are people dropping off", "audit this form", "where's the friction", or hands over a flow and asks whether it's user-friendly. Trigger even on casual phrasings ("is my checkout any good?") — it imposes the structure ad-hoc UX opinions miss. Audits flow usability and friction; for visual polish and interface quality the impeccable audit/critique skills apply instead.

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

韩红（歌手 / 公益）认知与表达框架（压缩蒸馏）：高音情感爆发、救灾叙事、直球正义人设 触发：天路、慈善 等。非替基金会官方发言

Composite skill — runs the postmortem chain after any production incident (`/hotfix`, rollback, or prod outage acknowledged). Chains adt-research (root-cause learning) → adr-write (decision capture) → generate-tests (regression test) → security-sweep (conditional, only if root cause is auth/input/secret-related) → knowledge-loop (memory + RAG curation) → handoff. Stops the silent-postmortem failure mode where a hotfix ships and the lessons evaporate. Auto-queues after `/hotfix` Phase 10 completes; also fires when user says "postmortem", "what did we learn", "write up the incident".

Detects outbound HTTP clients constructed without explicit timeouts in AEM Cloud Service code and applies mechanical fixes with CSO-aligned defaults to prevent request-thread pool saturation.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Advanced Tauri event patterns for bidirectional communication, streaming data, window-to-window messaging, and custom event handling

Package a customer escalation for engineering, product, or leadership as a decision-ready handoff — impact, timeline, facts vs. hypotheses, and a specific ask with an owner.

Responds to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing eradication procedures.

Session handoff generation and loading. Trigger: session end, context full, /handoff

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Layer alternative channels / scrapers / data sources with explicit fall-through, where each rung covers a different failure mode. Use when interacting with the world (sending a notification, fetching from a third party, detecting a state change, authenticating) and the single canonical path could fail in known ways. Distinct from retrying — retries handle transient failures; fallback chains handle modal ones (channel down, API gone, cookie expired). Three layers tops; the terminal rung is loud.

沈墨（悬疑剧虚构）认知与表达框架（压缩蒸馏）：创伤反杀叙事、时代灰雾、钢琴意象 触发：漫长的季节 等。虚构；禁止犯罪模仿

Creates or resumes a HANDOFF.md so a fresh Claude Code session can continue work without repeating dead ends, with strict anti-hallucination verification.

利威尔（少年漫）认知与表达框架（压缩蒸馏）：兵长洁癖战力、矮个子反差、残酷抉择 触发：进击的巨人 等。虚构；非仇恨教唆

Package an in-progress task on this cluster so a Claude agent on another cluster (MMM Young, CX3, HX1, Isambard) can pick it up, or resume a task handed off to this cluster. Use when the user says hand off / migrate / continue this on <cluster>, or asks you to pick up an existing handoff.

漩涡鸣人（少年漫）认知与表达框架（压缩蒸馏）：吊车尾逆袭、嘴遁与羁绊、不认输口号 触发：火影忍者 等。虚构；非暴力教唆

Maps external dependencies and I/O boundaries, generates chaos tests for failure modes like timeouts and connection errors, runs them, and reports resilience gaps with fixes.

顾佳（都市剧虚构）认知与表达框架（压缩蒸馏）：精英妈妈、婚姻风险对冲、体面崩塌 触发：三十而已 等。虚构

Use to design or audit a QA dispute and appeal workflow with timeboxes, adjudication standards, and second-level consistency so appeals improve trust instead of rewriting scores without rules. Trigger for "QA appeal process", "agents disputing scores", "who adjudicates QA disputes", "overturn rate too high", second-level review standards, or calibration erosion from ad-hoc score changes.

**Server Logs:**

Meta-skill codifying the no-wakeup-polling pattern. Describes the ScheduleWakeup anti-pattern, the fix (--auto merge + detached watcher), and when to still use wakeups. Reduces handoff spam by 80%.

Design a wise systems intervention from an existing analysis. Maps proposed actions against Meadows' leverage points, checks for unintended consequences, and generates alternatives.

Graceful degradation when primary approach fails. Try alternates in priority order; record which path succeeded for future routing.