메뉴
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
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Wiki mode — persistent knowledge base maintenance. Active during /pith wiki mode. Defines page formats, ingest workflow, query workflow, and lint checks.
Pith onboarding conversation. Runs on first session in a new project. Introduces Pith, offers wiki setup, guides through initialization. Injected by session-start.js when no prior setup detected.
Run the Pith wiki graph generator for the current project. Scans wiki/ for .md files, extracts [[wikilinks]], and opens an interactive force-directed graph in the browser as wiki-graph.html.
Install Pith into Claude Code. Copies hooks, patches settings.json, registers slash commands (/pith, /budget, /focus), and records the plugin root so hooks can resolve paths.
Interactive guided tour of Pith. Walks the user through each feature experientially — one step at a time, hands-on, using their actual project. Resumable. Skippable. State tracked via tour.py.
Uninstall Pith from Claude Code. Removes hooks, slash commands, and cleans pith entries from settings.json. Preserves ~/.pith/state.json (token history) unless user explicitly asks to wipe all data.
| 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.
