SuperAPI AI Directory
Partner中文AI newsFavorites
Skillscontext-fold

context-fold

Office & productivity

View repository

Updated 10-16 03:14

About this skill

context-fold

The core mechanism of VibeSucceed. Fold the pile of contract/progress documents that must be read at kickoff for the current project (PROJECT / HANDOFF / DECISIONS / MOMENTUM / LOG and the like) into "one hot zone + a pile of cold archives", so that kickoff only reads the hot zone.

Why

Reading all N documents in full at every kickoff = burning tens of thousands of tokens before doing any work at every kickoff. The hot zone compresses it to a few hundred tokens.append-only ≠ append-into-context:History stays on disk as before, just don't drag it into context every time.

When to use

  • Project kickoff requires reading multiple documents, and every kickoff's tokens are very expensive.
  • Contract/progress documents only grow, never shrink, piling up ever larger.

Action (one-time setup)

  1. Find all the contract/progress documents in the project that get read at kickoff.
  2. Distill from them thehot zone NOW.md(target ≤ 500 tokens), containing only: a one-sentence positioning, what's being done now, where we left off last time (the most recent entry), this round's next step, the 2–3 decisions currently in use, and the cold-archive index.
  3. Mark the remaining documents ascold archives—don't delete them, but don't read them at kickoff.
  4. Rewrite the project kickoff entry point (CLAUDE.md / AGENTS.md / AGENT_INDEX.md etc.): change "read N documents in order" to "read only NOW.md, retrieve cold archives on demand".
  5. Rewrite the wrap-up protocol: each round only refresh NOW.md + append one line to the cold archive, without writing details back into the hot zone.

Iron rules

  • NOW.md is the only mandatory read at kickoff, kept at a few hundred tokens; if it exceeds that, sink the details into the cold archive.
  • Don't delete any historical document, only change "what gets read at kickoff".
  • Folding is summarizing, don't write parsing scripts.
  • After the change, remind the user to use npx ccusage to measure the kickoff token reduction before and after.

Self-check

After setup, starting a new round of work should require reading only NOW.md to restate "what's being done / where we left off / next step"; if you still have to dig through cold archives to explain it clearly, the hot zone is missing something—add it to NOW.md。