docs: add MAP Prompt Library catalog with 14 recipes and audit table (#326)

[azalio]

Summary

Implements #326 — adds docs/PROMPT_LIBRARY.md as the MAP Prompt Library catalog. This is a documentation-only change; no agent/skill prompt bodies or template sources are modified.

Changes

docs/PROMPT_LIBRARY.md (new file)

• 14 copyable prompt recipes grouped by SDLC phase: Understand (3), Plan (3), Build (4), Review (2), Learn (2)
• Each recipe: prompt text with named <SLOTS>, recommended MAP surface, prerequisites, why-it-works, completion signal
• Roles covered: Engineer, Tech Lead, Operator/Maintainer
• Prompt-pattern audit table classifying 9 Claude Code Prompt Library source patterns against MAP's existing surfaces (Implemented / Docs-only gap / Internal-prompt eval candidate)
• Guardrails section distinguishing safe docs edits from internal-prompt changes requiring mapify skill-eval measurement

README.md

• Added Prompt Library row to the documentation table

docs/USAGE.md

• Added link to Prompt Library in the header paragraph

Acceptance criteria check

• ✅ 14 recipes across 5 categories (Understand, Plan, Build, Review, Learn) and 3 roles
• ✅ Each recipe has: prompt text, slots, MAP surface, prerequisites, why-it-works, verification/completion signal
• ✅ README and USAGE link to the catalog
• ✅ Audit table classifies source patterns as Implemented / Docs-only gap / Internal-prompt eval candidate, with repo evidence
• ✅ No internal agent/skill prompt body changed
• ✅ No template sources touched (no render-templates needed)

Test results

3309 passed, 4 skipped, 0 failures
ruff: All checks passed
pyright: 0 errors, 0 warnings, 0 informations

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@azalio, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: caf279ed-50e8-47b7-8de3-985450997781

📥 Commits

Reviewing files that changed from the base of the PR and between 8b3474d and 2f0b746.

📒 Files selected for processing (3)

• README.md
• docs/PROMPT_LIBRARY.md
• docs/USAGE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/compassionate-cerf-5tugql

---

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.}