What This Is
On March 15, 2026, Heru Feedback was fully implemented on QCR using Cursor agents. The prompts that drove that implementation were NOT saved to memory — Amen Ra caught this gap on March 16. He provided the complete prompt set, which is now preserved in the platform template.
Where to Find Them
Platform Template (source of truth):
.claude/plans/platform/heru-feedback-complete-implementation.md
This template includes ALL the prompts from the QCR implementation, organized into:
- Part 1: Mobile Widget (Tasks 1.1-1.5) — RNViewShot fix, tooltip, bubble preference, voice, screen recording
- Part 2: Backend API (Tasks 2.1-2.3) — model/resolvers, Slack, admin page
- Part 3: Resolution Loop (Tasks 3.1-3.7) — reporter fields, SES, push notifications, stats
My Voyages Adaptation:
/Volumes/X10-Pro/Native-Projects/clients/my-voyages/.claude/plans/platform/heru-feedback-implementation.md
- FAB HIDDEN by default (shake-only mode for product owner preference)
- Self-contained — Cursor agent doesn’t need boilerplate context
Key Customization Points Per Heru
When deploying to a new Heru, customize:
HERU_NAME— display nameFAB_DEFAULT_VISIBLE— true for internal apps (QCR, FMO), false for client apps (My Voyages)- Backend structure — some Herus use
features/dir, others usegraphql/directly - API URL and SDK key per environment
- Slack channel name
Lesson
ALWAYS save agent prompts to .claude/plans/platform/ after a successful implementation.
The prompts are the recipe. Without them, each Heru implementation starts from scratch.