lilmgenius/paperthin

prism

Split one artifact — a claim, plan, or file — across 2 to 5 independent lenses, one per genuinely distinct failure mode (correctness, security, readability, cost, adversarial-user), and return their convergence: where they agree, where they disagree, and th…

Zobacz źródło
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Split one artifact across independent lenses and return where they converge and where they don't.

Goal

The result is a picture of where the lenses agree, where they disagree, and the smallest question that would resolve the disagreement. Not a checklist, and never an average — averaging the lenses is the failure this skill exists to prevent.

Workflow

  1. Read the artifact end to end before choosing the lenses.
  2. Choose one lens per genuinely distinct failure mode — correctness, security, readability, cost, adversarial-user, and the like. Two candidate lenses that share a failure mode are one lens, not two. In practice this lands between 2 and 5: below 2 there is nothing to converge, and past 5 you are almost always padding with lenses that overlap. There is no default count — the artifact's distinct failure modes set it.
  3. Through each lens, produce a one-line verdict — pass, fail, or unclear — with its single most load-bearing reason. No hedging list; if a reason isn't load-bearing, drop it.
  4. Compare the verdicts and group them: full agreement, agreement for different reasons, disagreement.
  5. Where there is disagreement, name the single next question whose answer would move it into agreement or a clean split with owners. That question is the output, not the individual verdicts.
  6. Where every lens agrees, return the shared verdict with the reasons that were load-bearing for at least two lenses.

Rules

  • Independent lenses, not roles. A "security reviewer" and a "senior security reviewer" are one lens, not two.
  • One reason per lens — the load-bearing one. A lens that returns a list is hedging.
  • Disagreement is the product. A prism that agrees on everything did not need to be run.
  • Never average. If two lenses split, the answer is the question that resolves the split, not the midpoint of their verdicts.
  • Draw the lenses fresh for the artifact in hand. A lens useful for a spec may be useless for a migration; don't carry lenses across artifacts.
  • Don't manufacture disagreement. A run that finds none returns the shared verdict and stops.
  • User-invoked on purpose: plural lenses are an opt-in spend, and their convergence must never masquerade as automatic proof, so this fires only when deliberately reached for.

Verification

The result reads as a picture, not a checklist — a reader sees which lenses agreed, which disagreed, and the one question that matters, and can act on it without re-running the prism. If they'd need to re-run it to know what to do next, step 5 was skipped.

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
lilmgenius
Społeczność

shower

Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own — a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone with no prior context; before a handoff, publish, or merge; or when you want a clean-room comprehension smoke test. Spawns a separate context-free reviewer; it diagnoses, it does not fix.

instalacje
1
GitHub Stars
1,1 tys.
Aktualizacja
27 wrz
lilmgenius
Społeczność

re0-plan

Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.

instalacje
1
GitHub Stars
1,1 tys.
Aktualizacja
6 wrz
lilmgenius
Społeczność

re0-release

Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.

instalacje
1
GitHub Stars
1,1 tys.
Aktualizacja
6 wrz
lilmgenius
Społeczność

re0-upgrade

Bring your installed paperthin skills up to the full current catalog in one step: retire what's been renamed, add every skill you don't have yet, and refresh the rest, all shown and confirmed before anything changes.

instalacje
1
GitHub Stars
1,1 tys.
Aktualizacja
6 wrz