Document canonical Personal AI Infrastructure architecture and behavioral rules across Skills, Workflows, Hooks, Memory, and Agents.
npx skills add https://github.com/verrio1/vaughn-pai --skill core-verrio1
Please help me install this Agent Skill. Skill: CORE Source: https://github.com/verrio1/vaughn-pai/tree/main/skills/CORE Command: npx skills add https://github.com/verrio1/vaughn-pai --skill core-verrio1
CORE provides a single, canonical reference for the Personal AI Infrastructure (PAI) architecture, behavior, and governance, across all skills and workflows.
Use CORE to query the high-level design or to surface routing, governance, and core concepts for any PAI task.
High-intent search queries and answers about installing and using this skill.
The Personal AI Infrastructure architecture follows a CLI-first approach with deterministic code and prompts-wrap principles. It defines behavioral rules and routing across Skills, Workflows, Hooks, Memory, and Agents to ensure unified system design and governance.
Routing across skills, workflows, hooks, memory, and agents is governed by the core behavioral rules and architectural boundaries defined in the system documentation. Querying the canonical reference surfaces the correct routing patterns and governance constraints for any task.
Core design principles include a CLI-first methodology, deterministic code execution, and prompts-wrap patterns. These principles ensure predictable behavior and provide a unified reference for developers building modules, memory structures, hooks, and workflows.
No external inputs or dependencies are required. The core reference operates autonomously by aligning with the repository context to expose architecture concepts, behavioral patterns, and governance boundaries without needing external data sources.
Auditing and extending the PAI core involves querying the canonical reference for governance boundaries and system design rules. Developers use this documentation to understand module interactions, verify architectural compliance, and safely evolve core components.
The canonical architecture reference is limited to documenting design principles and governance boundaries. It does not execute code or manage runtime routing; developers must implement the documented patterns and behavioral rules within their own modules and workflows.
javierhbrSet up a local read-only MCP gateway for platform truth and JIRA metadata.
danielmiesslerLoad PAI core identity and response formats at session start.
ajayjohnDefine governance rules for TARS identity, routing, memory, and task protocols.
htlin222Design system architecture, APIs, and component interfaces using established patterns.
