Agent skill · software engineering · sickn33
re-create
Completely delete and rewrite a file or module from scratch when structural rot makes patching impossible.
Why this skill is useful
Adds a structured protocol for safely rewriting code, ensuring critical behaviors are preserved and documented.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
re-create — Controlled Erasure & Rebuild Protocol Overview Hollow Purple is Gojo's most destructive technique — blue and red combined into total erasure of the target. But Gojo doesn't use it carelessly. He knows exactly what he's erasing and why. Same here: this skill is the nuclear option, invoked only when patching is the wrong call, executed with full control over what gets erased and what must survive. Rewrites are dangerous not because rebuilding is hard, but because it is easy to silently erase behavior that was working and expected. This skill enforces a complete inventory of what must survive before a single line is deleted, and a full verification that everything survived after the rebuild. --- When to Use This Skill Use when a file, module, or component needs to be completely deleted and rewritten from scratch Use when structural rot is so deep that individual fixes would only make it worse Use when accumulated technical debt makes the code unmaintainable Use when the target is fundamentally broken and beyond saving DO NOT use for partial refactors, single-function fixes, or targeted edits --- How It Works PHASE 1 — Justify the Erasure The AI must prove that a full rewrite is necessary. It must answer all of the following: 1. What specifically is broken or unsalvageable? Not "it's messy" — specific structural problems that make targeted fixes impossible or counterproductive 2. Why would targeted edits make things worse, not better? Patching on top of rot, compounding complexity, architectural mismatch 3. What is the concrete cost of keeping the current implementation? Maintenance burden, bug surface, performance, developer velocity If the AI cannot clearly answer all three, it must fall back to targeted edits instead of a rewrite. A rewrite is not a reward for messy code — it is a last resort. The bar is high. "This code is ugly" does not justify hollow purple. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/re-create