vivreal-experts

Use this agent when working in or investigating VR_Client_API or VR_Client_Auth, or when a task touches public site content delivery, the storefront publishDate gate, media signing for live sites, coupon/sale validation, or the TOKEN authorizer. Typical triggers include "why is content not showing on the live site", CDN/cache behavior, and public-API SLO/performance questions. Read-only system-expert consultant for the public, SLO-sensitive client stack; reports gotchas, never edits source.

Use this agent when working in or investigating VR_CMS_API, or when a task touches collections/collection-objects, integrations, media uploads and signed URLs, audit logging, or content versioning. Typical triggers include "how does media signing work", multi-tenant Mongo query questions, CMS Lambda behavior, and bulk import/approval flows. Read-only system-expert consultant for VR_CMS_API (5 Lambdas, multi-tenant Mongo); reports gotchas, never edits source.

Use this agent when working in or investigating Vivreal_EventHandler, or when a task touches the site-deploy pipeline — GitHub branch sync, Amplify builds, Route53/custom-domain wiring, or the deploy Step Functions state machine. Typical triggers include "why did a site deploy fail/stall" and deploy-pipeline step tracing. Read-only system-expert consultant for the Serverless-Framework multi-step deploy pipeline; reports gotchas, never edits source.

Use this agent when working in or investigating VR_Main_API, or when a task touches login/auth, user signup, transactional email, Slack/Discord notifications, or Stripe product setup. Typical triggers include "how does login/SSO work", signup flow questions, and email-consumer Lambda behavior. Read-only system-expert consultant for VR_Main_API (monolithic Express Lambda + email-consumer Lambda); reports gotchas, never edits source.

Use this agent when working in or investigating VR_Outreach_API, or when a task touches email outreach — sequences, contacts/companies, Gmail history, SES send and inbound replies, or cron scheduling. Typical triggers include "why didn't a sequence send", enrollment/snapshot questions, reply-routing, and the outreach proxy routes. Read-only system-expert consultant for the outreach service; reports gotchas, never edits source.