Practical fit

When To Use PersonaKit

Use PersonaKit when the operating contract matters more than a one-off prompt.

PersonaKit is useful when the same kind of AI coding session repeats and the starting contract matters. It usually runs before the work begins; prompts describe the immediate task, and skills or tools are used later only inside the active boundary.

Use PersonaKit When

Review Mode Must Stay Read-Only

A reviewer should find defects, risks, and missing validation without becoming the implementer.

Open review session

Bounded Implementation Repeats

A common fix lane needs the same role, allowed capabilities, forbidden actions, stop points, and verification every time.

Open CLI maintenance

Agents Need Grounding Before Tools

MCP-aware clients or host grounding skills should resolve the contract before choosing host-local skills or tools, because availability is not authorization.

Open MCP grounding Open host skill example

Pack Authoring Needs Guardrails

Creating PersonaKit content should stay compact, dry-run first, reuse existing pieces, and validate afterward.

Open pack authoring

Skip PersonaKit When

Workflow Use Instead Why
Open-ended product thinking Chat, notes, whiteboard, or design doc The boundary is not known yet.
One-off prompt Prompt, saved prompt, or slash skill No durable operating contract is needed.
Skill use during a session Host skill, tool, or MCP client The session is already underway; use the capability directly inside the active boundary.
Formatter invocation Editor command, script, or formatter The procedure is mechanical and does not need role authorization.
Deployment CI/CD with approvals and audit logs PersonaKit may forbid deployment in a session; it should not perform deployment.
Secret retrieval Secret manager PersonaKit is not a vault or permission broker.
Long-running autonomous work Dedicated orchestration system PersonaKit is not a memory system, continuation engine, or multi-agent controller.

Adoption Pattern

Before creating new PersonaKit content, look for existing personas, directives, kits, intents, essentials, and skills that can be reused or recomposed.

  1. Pick one repeated work mode.
  2. Start from the closest example root instead of a blank root.
  3. Keep or revise one persona for who is acting.
  4. Keep or revise one directive for the work type, stop points, and validation.
  5. Add one kit for durable rules only when the rule should repeat.
  6. Declare only the skills that matter to the boundary.
  7. Define or adjust one session as the entry point.
  8. Validate, inspect the contract, and export handoff context.

Learn the model