terse-mode

After this, the AI's output drops roughly 75% — articles, pleasantries, and filler gone — while code, errors, and answers stay exact.

For developers running long sessions where output tokens are a real budget.

Before: "Why is this test failing?"

"Great question! Let me take a careful look at this test. Based on what I can see, it appears that the test might be failing due to a few possible reasons. The first thing to check would be... [800 words]"

After: "Why is this test failing?"

"Line 47: expectedCount = 5, actual = 4. Off-by-one in the loop on line 23. Change `i < arr.length - 1` to `i < arr.length`."

Use when

• long runs are getting expensive
• the user says "be brief" or "cut the filler"
• token budgets need real cuts, not 5% trims

Three ways to use this

1. Paste it (any AI, 30 seconds, no install)
   Open the .md file, copy contents, paste into Claude / ChatGPT / Cursor / Perplexity with: "Read this and apply it whenever the task it describes comes up in our conversation." Done.
2. Install it (Claude Code / Cursor users)
   Drop the unzipped folder into ~/.claude/skills/ (Claude Code), .cursor/skills/ (Cursor), or your IDE's equivalent. Auto-loads next session.
3. New to AI assistants? Get Claude free at claude.ai, then use Option 1.

€7