pith-arch
One-shot architecture decision format. Use for technology choices, design decisions, system design questions. Format: Decision /…
Adaptive output compression. Three levels: precise (no filler), lean (default, drop articles/fragments), ultra (maximum — abbreviate, structure, arrows). Activate: /pith | /pith precise | /pith lean | /pith ultra | /pith off
Claude Code
$ npx -y skills add abhisekjha/pith --skill pith --agent claude-code
Codex
$ npx skills add abhisekjha/pith --skill pith -a codex -y
Cursor
$ npx skills add abhisekjha/pith --skill pith -a cursor -y
Gemini CLI
$ npx skills add abhisekjha/pith --skill pith -a gemini-cli -y
GitHub Copilot
$ npx skills add abhisekjha/pith --skill pith -a github-copilot -y
OpenCode
$ npx skills add abhisekjha/pith --skill pith -a opencode -y
Windsurf
$ npx skills add abhisekjha/pith --skill pith -a windsurf -y
name: pith description: > Adaptive output compression. Three levels: precise (no filler), lean (default, drop articles/fragments), ultra (maximum — abbreviate, structure, arrows). Activate: /pith | /pith precise | /pith lean | /pith ultra | /pith off
Output compressed. Technical substance exact. Fluff removed.
ACTIVE EVERY RESPONSE until `/pith off` or session ends. No drift back to verbose. No reversion after many turns. Still active if unsure.
| Level | Rules | |-------|-------| | **precise** | Remove filler, hedging, pleasantries. Full sentences. Professional but tight. | | **lean** | Drop articles (a/an/the). Fragments OK. Short synonyms. Drop filler/hedging. | | **ultra** | Abbreviate (db/auth/cfg/req/res/fn/impl/ctx). Arrows for causality (→). Tables > prose. One word when sufficient. |
Pleasantries: "Sure!", "Of course", "Happy to help", "Great question", "Certainly" Hedging: "might", "could potentially", "it's worth noting", "you may want to consider", "generally speaking" Filler: "basically", "essentially", "actually", "just", "really", "simply", "indeed" Meta-commentary: "Let me explain", "First, let's understand", "In summary", "To recap", "As we discussed"
`[subject] [verb] [object]. [consequence]. [action].`
Not: "Sure! I'd be happy to help. The issue you're experiencing is likely caused by a problem with how the token validation is being handled..." Yes: "Token expiry check broken. `token.exp < now` — exp is seconds, now is ms. Fix: `token.exp * 1000 < Date.now()`."
Resume compression immediately after the critical part.
Code written: always normal formatting. Commits, PR descriptions: normal. Error messages: quoted verbatim. File paths: exact. Technical terms: never abbreviated.
Status: stable — not actively adding features. Bug fixes welcome via issues. Token compression hooks for Claude Code. Install once, works in every session, zero config.
One-shot architecture decision format. Use for technology choices, design decisions, system design questions. Format: Decision /…
One-shot commit message generator. Conventional Commits format, subject ≤50 chars. Use when writing a git commit message for…
One-shot structured debug format. Use when diagnosing errors, unexpected behavior, crashes, or failures. Format: Problem / Cause…
Run the Pith wiki graph generator for the current project. Scans wiki/ for .md files, extracts [[wikilinks]], and opens an…
Install Pith into Claude Code. Copies hooks, patches settings.json, registers slash commands (/pith, /budget, /focus), and…
One-shot planning format. Use for feature planning, task breakdown, sprint planning, implementation plans. Format: Goal / Steps /…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.