re0-work

lilmgenius/paperthin/re0-work

re0-work 是一种受控的重启方法。它保留已获得的知识，并拒绝复制前一次迭代中偶然形成的架构。从头开始并不意味着失忆：契约、模式、词汇、真实表面测试、质量门禁和负面语料在它们赢得保留时会保留下来。脚手架、解释性UI、调试面板、浅层生成内容以及仅用于学习不该做什么的代码则不会保留。工作流程包括：阅读当前计划、经验教训或re0-memo笔记、领域笔记、QA证据以及触发重启的用户投诉；识别要保留的内容（如契约、通过QA的模式、质量门禁、词汇、可复用服务、真实表面测试和负面语料）；识别要丢弃的内容（如解释性UI、调试面板、脚手架、浅层生成内容、偶然的抽象以及仅用于学习不该做什么的代码）；在规划代码之前命名第一个质量门禁；编写一个包含一个完整垂直循环的v0骨架计划；仅构建第一个循环直到它通过门禁。

安装量 · 362查看来源

Installation

npx skills add https://github.com/lilmgenius/paperthin --skill re0-work

技能文件

SKILL.md

最近同步 · 2026年8月27日

SKILL.md›

---
name: re0-work
description: "Restart a project or artifact from v0 while preserving only proven lessons, contracts, gates, vocabulary, real-surface tests, and negative corpus. Use when the foundation is wrong, accumulated code is misleading progress, or a new pass should learn from the old one without inheriting its accidental architecture."
---

Start over from what the previous cycle proved, not from what it happened to build.

## Goal

`re0-work` is a controlled restart. It keeps earned knowledge and refuses to copy forward accidental architecture. Starting from scratch is not amnesia: contracts, schemas, vocabulary, real-surface tests, quality gates, and negative corpus survive when they earned it. Scaffold, explanatory UI, debug panels, shallow generated content, and code whose only value was learning what not to do do not.

## Workflow

1. Read the current plan, any lessons or re0-memo notes, local domain notes, QA evidence, and any user complaint that triggered the restart.
2. Identify what to preserve: contracts, schemas that survived QA, quality gates, vocabulary, reusable services, real-surface tests, and negative corpus.
3. Identify what to discard: explanatory UI, debug panels, scaffold, shallow generated content, accidental abstractions, and code whose only value was learning what not to do.
4. Name the first quality gate before planning code.
5. Write a v0 skeleton plan with one complete vertical loop.
6. Build only the first loop until it clears the gate.

## Rules

- Starting from scratch means no copy-forward unless the artifact earned it.
- One complete vertical loop beats many shallow surfaces.
- Preserve provenance in local docs, not in the shipped product.
- Do not rebuild around a vague lesson. Turn it into a gate or leave it out.
- Do not delete negative corpus; archive or reference it where the next cycle will see it.
- If a reusable module survives, name the contract that proved it survives.

## Verification

Before finishing:

1. The preserve/discard split is explicit and evidence-backed.
2. The new v0 plan has one complete vertical loop and a named first gate.
3. No old architecture is copied forward merely because it exists.
4. A fresh builder can start without rereading the failed codebase.