re-frame2
Review Skills in day8/re-frame2, with license, maintenance context, and source paths.
- Skills
- 6
- Repository stars
- 44
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Repository
- Canonical name
- re-frame2
- Public sources
- 1
- License context
- MIT
Source entries
Agent Skills from re-frame2
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
day8/re-frame2
re-frame-migration
Migrates an existing re-frame v1.x ClojureScript codebase to re-frame2. Swaps the artefact coord (re-frame/re-frame → day8/re-frame2 + a substrate adapter), applies the mechanical (Type A) rewrites from MIGRATION.md automatically, and flags the judgment-call (Type B) call sites for human review before touching them. Trigger on phrasing like "migrate to re-frame2", "upgrade re-frame", "v1 to v2", "what breaks under re-frame2", or any prompt referencing a v1 surface (re-frame.db, dispatch-with, re
day8/re-frame2
re-frame2
Writes re-frame2 ClojureScript application code — events, subscriptions, effects, flows, frames, state machines (reg-machine, parallel regions, tags, spawn), schemas, stories, routing, tests, and the canonical patterns (RemoteData, Resources, Forms, Boot, WebSocket, NineStates, ManagedHTTP, AsyncEffect, LongRunningWork, StaleDetection, ReusableComponents, StatefulComponents, FormAction, SSR-Loaders). Use whenever the user mentions re-frame2, reg-event, reg-sub, reg-fx, reg-cofx, reg-flow, reg-vi
day8/re-frame2
re-frame2-pair
Pair-program against a **running** re-frame2 application via its Tool-Pair contract — attach to a live shadow-cljs nREPL, inspect a frame's app-db, dispatch events, hot-swap handlers, read the trace stream and per-frame epoch history, and time-travel with `restore-epoch`. Use when the user is operating on (or wants to operate on) a live runtime they have running locally. **Do not use** for static spec reading, architecture questions, design discussion, or ordinary source edits when no runtime is
day8/re-frame2
re-frame2-pair-retro
Retrospect on a `re-frame2-pair` session and turn it into prioritised improvement ideas for the pair skill, scripts, MCP surface, or upstream `re-frame2` Tool-Pair contract; optionally drafts a GitHub issue the user can file. Activates on two triggers: (a) **explicit pull** — user asks for a retrospective on a recent pair session ("retro on this pair session", "what went wrong with my pair session", "review my re-frame2-pair session", "draft an issue about that"); or (b) **post-error within a re
day8/re-frame2
re-frame2-ui
Writes, reviews, and debugs view code for `re-frame.ui` (artefact `day8/re-frame2-ui`, alias `ui/`) — re-frame2's compiled-view substrate, now the DONOR being absorbed into Freehand. Use it for an app that ALREADY depends on `day8/re-frame2-ui`; for new view work on the re-frame-native view layer, or for porting Reagent views onto it, route to `reagent-migration` and `spec/004-Views.md` instead — `defview` components, the closed template grammar, reactive `(sub …)` reads, handlers-as-data (event
day8/re-frame2
reagent-migration
Migrates Reagent VIEW code to **Freehand** (`re-frame.freehand`, alias `v`) — re-frame2's re-frame-native view layer. A Reagent hiccup view becomes a `v/defview` mounted in brackets and never called; `@(subscribe …)` becomes `(v/sub …)`; `#(dispatch …)` handlers lift to event vectors; Form-2 atoms and Form-3 lifecycle re-home to re-frame or to a registered behavior. This is the **optional, second** step of the journey: do the required re-frame v1→re-frame2 move first (the `re-frame-migration` sk
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository