[simplast]

What

Adds Pi (earendil-works/pi) to the documented agents: a setup page at /guides/with-pi, a row in the plugins table, a section on the standalone-skills page, and Pi in the agent lists in the FAQ, the quickstart and the README.

Why

HyperFrames already works with Pi without any per-agent install:

• npx hyperframes skills update copies the core skills into the shared ~/.agents/skills folder, which Pi reads in every project.
• skillsMirror deliberately skips Pi in the mirror fan-out because its universal copy is authoritative (UNIVERSAL_STORE_READERS, Global skill mirroring should avoid redundant agent directories and provide target controls #3294).
• agent_runtime.ts already fingerprints pi as an agent runtime.

The site never said any of that, so a Pi user had no setup page and no reason to expect the skills to load. I checked the open and closed issues and PRs first: nothing asks for this, and #3325 only covers the mirror behaviour.

How

• docs/guides/with-pi.mdx — the new page: both install routes, the /skill:hyperframes spelling Pi uses, project trust, preview and render, troubleshooting.
• docs/docs.json — guides/with-pi in the "Use it with your agent" group.
• docs/guides/plugins.mdx — a Pi row and a mention in the intro, since Pi has no plugin of its own.
• docs/guides/skills.mdx — a short "Use the skills in Pi" section that points at the page.
• docs/faq.mdx, docs/quickstart.mdx, README.md — name Pi in the agent lists that were already there.

Pi's slash command is /skill:<name> rather than a bare /hyperframes, so the page gives the prompt in the form Pi accepts while the other agents keep theirs.

Test plan

• Manual: npx skills add <checkout> --skill hyperframes --global --agent claude-code universal --copy lands the bundle in ~/.agents/skills/hyperframes; with that folder in place, pi --print lists hyperframes among its available skills.
• Manual: npx skills add <checkout> --skill hyperframes --agent pi --copy in a scratch project writes .agents/skills/hyperframes, which is the project route the page documents.
• docs/docs.json parses as JSON, and oxfmt reformatted nothing in the touched files.
• Docs only: no unit tests needed, no runtime behaviour changed.

[mintlify]

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit 83fe9bc.

Approve preview