← ClaudeAtlas

wincreatorlisted

Proves that agent work is actually done: each claim becomes a ledger row with a gate that was executed, captured raw evidence, and a status a builder is not allowed to write for itself. Use when a technical result must be auditable later — shipping or migrating something users depend on, a change whose failure is expensive or silent, work handed to someone else, a claim under review or compliance, a debugging loop that already failed twice, or when the user asks for proof, verification, an audit trail, "structure this work", "organise cette boucle". Not for trivial edits, exploration, explanations, or routine multi-step coding where a quick check suffices — use the Lite tier or no ceremony at all. Domain-agnostic; assumes no stack.
winterbim/wincreator · ★ 3 · Code & Development · score 67
Install: claude install-skill winterbim/wincreator
# WinCreator — Hierarchical Engineering Loops with Proof Gates ## Why this skill exists Every agent-assisted engineering session degrades the same three ways, and knowing them is the key to using this skill well: 1. **Optimism leak** — the same context that wrote the code grades its own work, and "it should work" quietly becomes "it works". 2. **Context rot** — constraints stated early get lost as the session grows; the agent drifts from the original need without noticing. 3. **Stuck loops** — a failing check gets re-attacked at the same level again and again, when the real defect lives one level up. This skill counters each one mechanically, not aspirationally: optimism leak → Proof Ledger + Builder/Skeptic separation; context rot → the Loop Panel; stuck loops → the Two-Failure Rule. Everything else in this file exists to serve those three defenses. > **Evidence > Assertion. Truth > Speed. Rigor > Improvisation.** A brainstorming loop diverges: ideas, no obligation of proof. An **engineering loop** converges: it only reports up after passing a verifiable **truth gate** — a test actually run, an output actually inspected, a measurement actually taken. Nothing unproven propagates upward. The rigor is structural and domain-agnostic: no language, framework or stack assumed — you translate each proof criterion into the concrete gesture of your domain. ## Three tiers — pick one in the first line of the task Ceremony must be proportional to stakes, or the skill bec