pi

To prevent hallucinating Pi APIs, use the pi skill to inject grounded reference documentation into your coding agent, ensuring it reasons from actual Pi architecture facts instead of inventing configurations.

Pi discovers and triggers Agent Skills by evaluating SKILL.md frontmatter and routing rules, applying progressive disclosure to load relevant skill context precisely when a coding task requires it.

Merging Pi settings requires following specific configuration rules for .pi/ directories and settings.json files, where the pi skill provides the exact merge hierarchy to ensure your extensions load correctly.

Yes, external coding agents can configure Pi models, providers, and session compaction by referencing the pi skill's grounded documentation for SDK/RPC embedding and session tree or fork lifecycle rules.

Pi extension lifecycle routing enforces specific UI rules and tool constraints that govern how extensions trigger, route reasoning, and interact with the environment, preventing unauthorized API calls.

You need Pi-specific reference injection when editing Pi extensions, skills, packages, or configuration, ensuring the agent follows trigger rules and routes reasoning from documented references.