re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Realign a listing whose order has gone arbitrary — a list, table, catalog, sections, an enum — into a logical sequence under one stated principle. Move items only: nothing is reworded, added, or removed. Use when the order no longer helps a reader follow the set.
$ npx -y skills add LilMGenius/paperthin --skill reorder --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/reorderContext preview
The summary Claude sees to decide when to auto-load this skill.
Realign a listing whose order has gone arbitrary — a list, table, catalog, sections, an enum — into a logical sequence under one stated principle. Move items only: nothing is reworded, added, or removed. Use when the order no longer helps a reader follow the set.
name: reorder disable-model-invocation: true description: "Realign a listing whose order has gone arbitrary — a list, table, catalog, sections, an enum — into a logical sequence under one stated principle. Move items only: nothing is reworded, added, or removed. Use when the order no longer helps a reader follow the set."
Put a listing back into an order that carries meaning, moving items only.
A listing's order is information: kin sit together, and the sequence follows one axis a reader can feel. Order drifts — items get appended where they were written, not where they belong — until the sequence tells the reader nothing. `reorder` realigns the set under a single, nameable principle so the order reads as intentional again. It is fast and single-purpose: it moves items, and changes nothing else.
1. Pin the listing and its items — the ordered set in focus. 2. Name the principle that makes the order carry the most meaning: workflow or lifecycle sequence, dependency, grouping by kind, severity, frequency, or plain alphabetical. If the set already has a latent order, surface and finish it rather than imposing a new one. 3. Cluster kin adjacent, then sequence the clusters by that one principle. 4. Move items into the new order in place. Reword nothing; add and remove nothing. 5. If the same set is mirrored elsewhere — a translated copy, a second surface — apply the identical order to each.
1. A reader can name the ordering principle from the result alone. 2. Every item that was there is still there — only positions changed; nothing reworded, added, or removed. 3. Kin are adjacent and the sequence follows the one principle end to end. 4. Every mirrored copy of the set carries the identical order.
Turning old engineering wisdom into reflexes your agent reaches for on its own. On any agent | Claude Code, Codex, OpenCode, Antigravity, Copilot, Cursor, Grok-Build, Pi, Hermes, OpenClaw, etc.
Repo: LilMGenius/paperthin
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Audit and consolidate a fact that's scattered across places into one canonical source, after…
Rebuild the human's lost context on a project from live state, in plain language: what needs…
Read the live cycle state and return the single highest-leverage next best action, not a…
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting…
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns,…