[TomyCesaille]

Closes #7. Closes #8.

The website follows the README, in its order and in how it explains prtop to an agent.

Order (#7):

1. Install with Claude Code, for Claude Code: the setup prompt. Claude installs prtop for you and for itself: it checks your sign-in, fits the settings, then sets itself up to use prtop (/prs, watching in the background). The README's heading and paragraph say the same.
2. Install manually: Homebrew or Chocolatey, which bring glab and gh, signing in, the .env with PRTOP_FORGES, then prtop.
3. How to read prtop: the infographic, unchanged.
4. Made for Claude Code, where the README has "With an AI agent".

Made for Claude Code (#8): the example shows only what prtop watch prints, two quiet checks then the changed table. Claude's reply (⏺ … Merge it? 🚀) is gone: inside the same block it read as prtop's output. Two sentences from the README's "With an AI agent" frame it: prtop watch exits with the new table as soon as it changes, and prtop never writes to GitLab or GitHub, so merging, rebasing or triggering a deploy stays with Claude, behind your confirmation. The /prs command and the READMEs already say so and stay as they are.

docs/src/pages/index.astro changes, and the README's Claude Code install section. The site builds, and a local preview shows the four sections in that order.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.