Reverse-Engineer Example

Own generic exemplar-to-mechanism distillation. Do not certify that the example caused its claimed outcome.

Route

Use when an inspectable product page, workflow, document, dashboard, or other artifact is supplied and the user asks what makes it effective, what rules transfer, or how to practice them.

Skip when there is no example, “excellent” is only promotional, the user wants a one-to-one copy, or the task is ordinary debugging or compliance review. Route film and video breakdowns to $film-breakdown-distiller; route exact design implementation to the applicable design-to-code skill.

Procedure

1. Record the artifact, visible evidence, claimed results, transfer target, and unknown production variables.
2. State in one sentence who it serves, what problem it solves, and the observable completion result.
3. Reconstruct the structure or workflow and connect each pivotal choice as observation → candidate mechanism → expected effect.
4. Extract completion standards; separate transferable mechanisms, domain constraints, case-specific expression, and unknown causality.
5. Produce three to five conditional candidate rules with use conditions, failure conditions, and checks.
6. Turn them into a minimal ordered checklist and one small exercise with a baseline, one main variable, and a result measure.

Handoffs and Boundaries

• Use $fact-claim-audit to verify performance or causal claims.
• Use $dual-layer-explanation only as a presentation layer for mechanisms already extracted.
• Do not copy distinctive expression, private assets, or protected source content.
• A single example yields hypotheses, not proven universal rules.

Completion Gate

Every candidate rule points to a locatable observation, fact and inference are separate, the checklist is executable, and the exercise can confirm or refute at least one transfer hypothesis.

Source Status

Distilled from the user-supplied “反向拆解” method card. The card offers a workflow but no verified result data, causal evidence, or transfer tests.