From paxus-skills
Bring a Paxus client into your AI workflow with the firm's standard folder structure. Run when starting work with a new client, or when bringing an existing client into Claude Code for the first time. Creates ~/paxus-ai/clients/{client-slug}/ with CLAUDE.md, STATUS.md, and the standard subfolders, and optionally scaffolds the first project under it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/paxus-skills:onboard-clientThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are setting up a Paxus client folder in the operator's `~/paxus-ai/clients/` workstation. Follow the five phases below in order. Be conversational and warm — match the Paxus voice from the firm rules.
You are setting up a Paxus client folder in the operator's ~/paxus-ai/clients/ workstation. Follow the five phases below in order. Be conversational and warm — match the Paxus voice from the firm rules.
[TBD — operator to fill] in the generated file. Never invent details.O'Reilly Construction → oreilly construction)&, /, ., ,) with a single dashclient-
Show the operator the derived slug and ask "Use {slug}, or want a different one?" before creating any folders.~/paxus-ai/clients/{slug}/ already exists, stop and ask the operator: open the existing folder, create with a numeric suffix ({slug}-2, {slug}-3), or abort.templates/ in this skill folder. Read them, fill in the per-client values, write the result. Replace each {{PLACEHOLDER}} with the corresponding answer; if a field is unknown, use [TBD — operator to fill].templates/ is missing or unreadable, stop and tell the operator the skill is corrupted — they should re-run the paxus-ai-workstation SETUP. Do not try to generate templates from memory.Greet the operator and ask three questions in one message:
Wait for all three answers. From the name, derive a slug. Show the slug to the operator and ask "Use {slug}, or want a different one?"
If they provided context (text, file path), read it carefully. Use it to pre-fill answers for Phase 2 — don't migrate the file verbatim, but let it inform the answers you offer.
Ask each question individually. After the operator answers, briefly confirm what you captured before moving to the next question. If Phase 1 context pre-filled an answer, present it as "Based on what you shared, this looks like X — keep it or change?"
Questions:
If the operator says "I don't know" or "skip" for a question, accept it. Write [TBD — operator to fill] in the generated file at that field.
Ask: "Want to scaffold your first project for this client now? If yes, what's it called?"
Suggest defaults based on context — e.g., if it's the middle of the month, suggest {current-month}-close; if Phase 2 mentioned an upcoming board meeting, suggest {date}-board-package.
If yes:
~/paxus-ai/clients/{client-slug}/projects/{project-slug}/templates/project-claude-md.md and templates/project-status-md.md, fill in project name + purpose + end state, write to the new folderIf no:
/onboard-client later or create a project folder manuallyAsk two questions, one at a time:
If the operator says "nothing" to both, accept and move on.
If they have feedback, append to ~/.claude/skills/onboard-client/learnings.md with this format:
## {YYYY-MM-DD} — {operator first name} — client: {slug}
- [LEARNING] {what they said about #1}
- [SUGGESTION] {what they said about #2}
To get the operator's first name:
~/.claude/CLAUDE.md for a clear self-identification (e.g., a heading like # CLAUDE.md — Cassie Rigsby or a line "I'm Cassie..."). If you find one, use that name.anonymous and continue. Do not block the learning capture on this.Show the operator:
tree ~/paxus-ai/clients/{client-slug}/ (or find/ls -R if tree isn't installed). Visual confirmation of what was created.notes/ so Claude has them when you work in this folder"STATUS.md and fill in your immediate next steps"projects/{slug}/. Open Code in that folder when you're ready to start."End with one line: "Client onboarded: {name}. Folder at ~/paxus-ai/clients/{slug}/. Run /onboard-client again whenever you bring on the next client."
When generating files, use these templates from the templates/ folder:
~/paxus-ai/clients/{slug}/CLAUDE.md ← from templates/client-claude-md.md~/paxus-ai/clients/{slug}/STATUS.md ← from templates/client-status-md.md~/paxus-ai/clients/{slug}/projects/{project-slug}/CLAUDE.md ← from templates/project-claude-md.md (Phase 3 only)~/paxus-ai/clients/{slug}/projects/{project-slug}/STATUS.md ← from templates/project-status-md.md (Phase 3 only)Always create these folders even if empty:
~/paxus-ai/clients/{slug}/notes/~/paxus-ai/clients/{slug}/deliverables/~/paxus-ai/clients/{slug}/projects/The standardized firm rules (templates/firm-rules.md) are referenced by the client CLAUDE.md but not duplicated — they live once in the operator's global ~/.claude/CLAUDE.md.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
npx claudepluginhub benalihq/paxus-skills --plugin paxus-skills