Skip to content

re-frame2-improver

Critique-mode for existing re-frame2 ClojureScript code. Reviews a body of source files (or a supplied snippet) against a catalogue of re-frame2 anti-patterns, surfaces concrete findings cross-linked to canonical idioms, and may propose inline fixes. Explicit-pull-only.

What it does

The re-frame2-improver skill is a focused code reviewer for already-written re-frame2 code. It reads a body of source files (or a user-supplied snippet), detects anti-patterns from a small catalogue, and returns one complete, severity-ordered critique in the same turn — each finding with concrete file/line evidence, its consequence, the smallest safe correction, and a cross-link to the canonical idiom under skills/re-frame2/patterns/. It applies fixes via Edit only when the request says to fix as well as review; broader redesigns stay proposals.

It is explicit-pull-only: the user asks for a review, the skill activates, delivers the complete critique in that turn, and exits. Vocabulary alone ("review", "audit", "any improvements?") is not enough — a body of re-frame2 source must be in scope.

When to reach for it

Load this skill on an explicit review request — "review my re-frame2 code for anti-patterns", "audit this against re-frame2 best practices", "any improvements?", "is there a better re-frame2 pattern here", "spot any anti-patterns in cart/handlers.cljs" — and a body of re-frame2 source is in scope: read or edited in the conversation, supplied as a snippet, or named as a concrete, resolvable .cljs / .cljc file or directory path the skill can read (it reads the named path before critiquing). A path that does not resolve does not establish scope.

Do not use this skill for:

Kickoff

The skill activates on explicit pull. To force-load:

/skill re-frame2-improver

If no source files have been read, edited, supplied as snippets, or named as a resolvable .cljs / .cljc path, the skill declines and asks for a snippet rather than fabricate evidence.

Where the skill lives