retheme
Skill1 starsChanged 17 days agoMITView on GitHub
Systematically apply an approved design lane (LANE.md) to a React + Tailwind site — tokens first, then section-by-section, with build + screenshot verification after every pass. Use when the user says "retheme", "apply the lane", "make it match the design", or after /unslop:interview produced an approved LANE.md.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KhaledSaeed18/deck-kittheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KhaledSaeed18/deck-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read in full: unslop/LANE.md, ${CLAUDE_PLUGIN_ROOT}/rules/anti-slop-checklist.md, and unslop/DESIGN-AUDIT.md if present (its Top 5 fixes …
- Distinctive: line 51
Read the new screenshots and confirm the pass did what it claimed at 375 and 1440px before starting the next pass.
- Very specific: line 59
Before/after: first audit screenshots vs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Retheme
Apply the approved lane to the codebase, pass by pass, with evidence at every step. This is the only unslop skill that edits source.
Preconditions (hard)
unslop/LANE.mdexists and was user-approved. If missing, stop and run/unslop:interviewfirst.- Clean git state: ask the user to commit or stash, or create a branch
(
unslop/retheme) before touching anything. npm run buildpasses before you start. If it doesn't, fix nothing design-related — report the build error and stop.- Read in full:
unslop/LANE.md,${CLAUDE_PLUGIN_ROOT}/rules/anti-slop-checklist.md, andunslop/DESIGN-AUDIT.mdif present (its Top 5 fixes get priority).
Passes (in order — never skip ahead)
Pass 1 — Tokens. Install the lane's :root CSS variables and Tailwind config
mapping. Replace stock color classes (indigo-600, gray-50, …) with token-based
ones. Load the lane's Google Fonts. No layout changes yet.
Pass 2 — Typography & spacing. Apply the type scale, weights, tracking and leading per the lane. Snap arbitrary spacing to the scale; set the section rhythm.
Pass 3 — Sections, one at a time. Nav → hero → each content section → footer. Apply the lane's surfaces (radius system, depth cue, texture), fix the layout tells from the checklist (L1–L4), and build the lane's signature moment where it belongs. One section per edit batch.
Pass 4 — States & motion. Hover and focus-visible styled to the lane;
loading/empty/error states on data-touching UI; motion per the lane's budget with
the stated prefers-reduced-motion stance; kill transition-all.
Pass 5 — Exit audit. Re-run the full audit procedure (screenshots, slop-scan, contrast-check, checklist walk) and verify every acceptance check in LANE.md.
Verification after EVERY pass (non-negotiable)
npm run build # must pass clean
node "${CLAUDE_PLUGIN_ROOT}/scripts/screenshot.mjs" <url> ./unslop/screenshots/pass-NRead the new screenshots and confirm the pass did what it claimed at 375 and 1440px before starting the next pass. If a pass broke something, fix it inside that pass. Never claim a pass is done without a passing build and fresh screenshots you have actually looked at.
Finish
- Final score from Pass 5 vs. the original audit score, stated plainly.
- Before/after: first audit screenshots vs. final ones, linked in a short
unslop/RETHEME-REPORT.md. - Any acceptance check that could not be met: say so explicitly — no silent skips.
- Client report. Also write
unslop/CLIENT-REPORT.html— a self-contained HTML page for a non-technical reader, following${CLAUDE_PLUGIN_ROOT}/rules/client-report.md. Score delta up front, before/after screenshots embedded, what changed in plain language. This is the artifact a freelancer hands to (or invoices) a client. - Suggest a commit with a summary of the passes.
Scope rules
- Change only what the lane and checklist require. No feature additions, no refactors, no dependency swaps beyond fonts/motion lib the lane demands.
- Copy/content stays unless it's placeholder lorem — flag content problems, don't rewrite the user's words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.