القائمة
One-shot architecture decision format. Use for technology choices, design decisions, system design questions. Format: Decision / Options table / Choice / Risks / Next. Does not persist.
التثبيت باستخدام 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-arch |
| description | One-shot architecture decision format. Use for technology choices, design decisions, system design questions. Format: Decision / Options table / Choice / Risks / Next. Does not persist. |
Architecture decision format. Structured. No narrative.
Decision: [what is being decided — one line]
| Option | Pro | Con | Complexity |
|---|---|---|---|
| A | ... | ... | low/med/high |
| B | ... | ... | low/med/high |
| C | ... | ... | low/med/high |
Choice: [option name] — [single sentence reason]
Risks:
Next: [immediate first action]
Decision: session storage strategy for auth
| Option | Pro | Con | Complexity |
|---|---|---|---|
| JWT | stateless, no DB reads | can't revoke, large cookie | low |
| Redis | revocable, small cookie | infra dependency | medium |
| DB session | simple, no new infra | DB read every request | low |
Choice: Redis — revocability is required (security team req), team already operates Redis for cache
Risks:
Next: Add ioredis to package.json, write src/lib/session.ts
One-shot. Does not persist.
