docs: trim duplicated agent playbooks

[phuongnse]

Summary

Trim duplicated agent/playbook guidance so common rules point back to a single owner instead of being restated across multiple docs. Keep existing frontend and wireframe anchors, but redirect detailed guidance to frontend.md, wireframes.md, docs-style.md, visual-artifact-checklist.md, and repo skills.

Linked spec

N/A - docs/tooling cleanup; no product use-case spec.

Requirements & rules followed

• Spec -> code - N/A - docs/tooling cleanup only; no use-case ACs.
• Ready review - changed paths are agent/playbook docs only; no behavior AC map triggered.
• Path coverage matrix - N/A - no runtime implementation surface.
• Verification gate - python scripts/axis.py verify passed for this docs-only branch.
• Docs review - AGENTS.md, docs hub, agent checklist, design gate, docs-style, patterns index, and patterns.md updated.
• Retrospective review - no new durable rule or repeat finding emerged.
• Workarounds - this PR does not introduce or resolve a P0/P1 workaround.
• No new TODO / FIXME / NotImplementedException / placeholder / stub under src/, tests/, frontend/src/.

[coderabbitai]

Warning

Review limit reached

@phuongnse, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 40 minutes and 46 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 61c5e38a-5091-4858-b708-c63ab968f5a0

📥 Commits

Reviewing files that changed from the base of the PR and between ecc0782 and 06a8867.

📒 Files selected for processing (7)

• AGENTS.md
• docs/README.md
• docs/playbooks/agent-checklist.md
• docs/playbooks/design-gate.md
• docs/playbooks/docs-style.md
• docs/playbooks/patterns-index.md
• docs/playbooks/patterns.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/docs-trim-agent-playbooks

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}