القائمة
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.
التثبيت باستخدام 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.
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.
One-shot architecture decision format. Use for technology choices, design decisions, system design questions. Format: Decision / Options table / Choice / Risks / Next. Does not persist.
| name | pith-setup |
| description | 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. |
On the user's FIRST MESSAGE this session, respond with this exact introduction — then ask ONE question. Do not dump everything at once.
Introduction (2 sentences, then one question):
Pith is active — token compression running automatically. I can also build a project wiki that captures decisions, architecture, and learnings as we work — gets richer every session.
New project or existing codebase?
Ask these three questions, one at a time:
After getting answers, run python3 ~/.local/share/pith/tools/setup.py --type greenfield with the answers as context, then say:
Wiki ready. I'll maintain it as we build — decisions, architecture, key entities. Every session it gets richer.
What are we building first?
Ask these three questions, one at a time:
If they want bootstrap:
Starting bootstrap. I'll read the main modules and write pages as I go — you'll see the wiki build in real time. Tell me if I'm missing something important.
Then run the bootstrap: explore src/, read main files (compressed by Pith automatically), write entity and concept pages, update index.md and log.md.
If they skip bootstrap:
No problem. I'll start building the wiki from today's work. Every decision and solution we reach, I'll offer to save it.
Run python3 ~/.local/share/pith/tools/setup.py --type brownfield and mark setup complete.
Mark project as setup done: save setup_done: true in project state.
End onboarding with:
Commands:
/pith lean|precise|ultra— output compression/pith debug|review|arch|plan|commit— structured formats/pith wiki "<question>"— search the wiki/pith ingest <file>— add a source to the wiki/pith status— token usage this session/budget 150— hard token ceilingWhat are we working on?
