compress-prompt

# Compress a KB Prompt ## Mental model - The artifact you compress is loaded into a coding agent that runs in ANOTHER repo, on ANOTHER user's task. Every token becomes that agent's context → scaffolding = distraction that dilutes focus. - Compress ≠ shrink words. Compress = strip scaffolding, keep 100% signal, sharpen focus, replace with meaningful unicode characters, like arrows. - Reader is AI like you, capable: it already knows the domain AND the KB grammar. Use terms and acronyms. Don't explain — nudge. - CAPS = importance. Word count is an OUTCOME, never a target. - INVARIANT ≠ STEP. Invariants (always-on constraints) → declare ONCE, flag always-on. Steps → ordered, run once. NEVER re-assert an invariant as per-step reminders — that's the echo authors reflexively add; compress hoists + cuts it. - GOLDEN RULE: NEVER trade a high-value token for a few saved words (unless it is repeatedly used and overall gives high results, we can loose 2% of value overall). - BULLETS vs ORDERED: ALWAYS convert bullets to ordered lists, if work is sequential or can be sequential. Reason: aligns with AI sequential token generation. - DENSIFY EVERY rule. - Take time to think during reasoning, take different options, iterate multiple times TRANSFORM. - Your task is MAXIMUM compression, not just low hanging fruits! - NO rush, TAKE time - Don't bring this skill terms or meta-thinking - Identify what is load bearing ## Allowed reads — read-only, NEVER adjust Read ONLY: the target artifact + it...