jaydubya818/Pi

active-listener

Listen carefully and reflect back what the user said before acting. Use when the user needs to feel heard or when clarifying intent before proceeding.

artifact-first-reporting

Always produce a structured artifact (file, table, or doc) as the primary output before summarizing. Use for reporting tasks where the deliverable should be a concrete artifact.

backend-implementation-discipline

Follow backend implementation best practices: typed interfaces, error handling, migrations, and test coverage. Use when implementing backend features, APIs, or data models.

conversational-response

Respond in a natural, concise conversational tone without unnecessary structure or headers. Use for chat-style interactions that don't require formal output.

delegation-protocol

Define how tasks are handed off between agents or roles, including context passing and acceptance criteria. Use when orchestrating multi-agent or multi-role workflows.

domain-boundary

Enforce clear boundaries between domains (frontend, backend, infra) and prevent cross-domain coupling. Use when reviewing or designing code that spans multiple system layers.

frontend-implementation-discipline

Follow frontend implementation best practices: component structure, accessibility, typed props, and test coverage. Use when implementing UI features or components.

implementation-handoff-discipline

Ensure implementation plans include all context needed for a clean handoff to the executing agent. Use before handing off a spec or plan for implementation.

mental-model

Build and maintain an explicit mental model of the user's system or codebase before acting. Use at the start of complex tasks to ground reasoning in actual project structure.

planning-handoff-discipline

Ensure planning outputs are complete and unambiguous before handoff to implementation. Use when transitioning from planning to execution phase.

security-review-discipline

Apply security review discipline: check for injection, auth gaps, secrets exposure, and unsafe defaults. Use when reviewing or implementing code with security implications.

synthesis-first-reporting

Lead with a synthesized summary before details when reporting findings. Use for research or analysis tasks where the key insight should surface immediately.

test-validation-discipline

Validate implementations with tests before marking work complete. Use when implementing features to ensure test coverage is part of the definition of done.

validation-handoff-discipline

Ensure validation criteria and test scenarios are fully specified before handoff. Use before passing work to a validation or QA phase.

zero-micromanagement

Execute tasks autonomously without asking for permission on each step. Use to signal that the agent should proceed with reasonable judgment rather than checking in constantly.

library

Private skill distribution system. Use when the user wants to install, use, add, push, remove, sync, list, or search for skills, agents, or prompts from their private library catalog. Triggers on /library commands or mentions of library, skill distribution,…