What problem does it solve? Upgrading an existing re-frame v1.x ClojureScript application to re-frame2 involves a dependency-coordinate swap plus dozens of breaking-change rules, many of which fail silently at runtime rather than at compile time. This Skill routes that migration through a structured workflow so mechanical rewrites are applied automatically and judgment-call changes are flagged for human review instead of being guessed. ## Core Features & Use Cases - Planned migration sweep: Inventories v1 add-on libraries (http-fx, async-flow-fx, re-frame-10x) and app features, scans their source for removed v2 surfaces, and produces a per-item migration plan before any edit. - Type A / Type B rule application: Applies mechanical rewrites (namespace requires, effect-map consolidation, dispatch shapes, test-API renames) automatically, and asks first on intent-sensitive changes like handler semantics and the M-11 view conversion. - Runtime verification: Runs the project's own compile and test gates, then drives a boot smoke-test with live app-db and machine-snapshot introspection, since a clean compile is not the done-bar. - Use Case: Point it at a v1 project using re-frame/re-frame, re-frame-test, and async-flow-fx; it bumps the deps to day8/re-frame2 plus a substrate adapter, clears the React-19/Reagent-2 floor gate, rewrites the call sites, and produces a migration report citing each M-N/O-N rule applied. ## Quick Start Ask the AI to migrate this re-frame v1 project to re-frame2 using the re-frame-migration skill, starting from the repository root.
