vivreal-knowledge

Use when investigating what happened during a Vivreal user action across the stack, tracing an error end-to-end, validating a deploy, or doing tenant-scoped triage with Sentry. Teaches WHEN to trace cross-stack (frontend spans ↔ backend logs ↔ WebSocket events) and HOW (trace-ID propagation, the standard tag set, request_id fallback, service.* breadcrumbs). Triggers on: "what happened when I did X", "why did this error", trace this request, Sentry issue, deploy validation, "everything's broken for this group", crash, error timeline. For the full investigation agent with Sentry MCP tools wired in, dispatch the `sentry` agent / `/sentry-trace` (both in the `vivreal-sentry` plugin); this skill is the passively-loaded knowledge layer.

Use when writing, reviewing, or critiquing Vivreal marketing copy, messaging, or brand content — landing pages, pricing copy, social posts, cold email, ad copy, onboarding/in-app copy, taglines, or any customer-facing words. Teaches the defined Vivreal voice (the "Approachable Guide" register for non-technical SMB founders), the hard-banned words/patterns (em dashes, corporate fluff, developer jargon), the positive voice rules, an on-voice audit rubric, channel best-practices (founder-led LinkedIn spine, sequenced multi-channel, short-form video, one-primary-CTA, benefit-led copy, quantified social proof), and AI prompt scaffolding for staying on-voice. Triggers on: brand voice, tone, copy, messaging, marketing content, landing page copy, pricing copy, cold email, social post, ad copy, tagline, headline, value prop, positioning, on-voice, off-voice, jargon, CTA, social proof, founder-led, channel strategy. The `marketing-auditor` agent grounds in this skill; the `content-planner`/`content-creator` agents PRODUCE content to this voice. For funnel/conversion ECONOMICS use `principal-growth-auditor`; for internal cost/margin use vivreal-unit-economics.

The **public content-delivery stack**: deployed customer sites (Vivreal_Templates) call `VR_Client_API` to fetch content + run Stripe checkout + send emails, and every request first passes `VR_Client_Auth` — a tiny custom Lambda authorizer that validates the group's API key and injects tenant context. **This pair is the only Vivreal backend using API-key auth (not Cognito).** Read `C:\repos\VR_Client_API\CLAUDE.md` and `C:\repos\VR_Client_Auth\CLAUDE.md` for depth.

The CMS backend: collections, collection objects, integrations, media uploads, audit logging, content versioning. Maps to `NEXT_PUBLIC_CMS_URL`. Express + serverless-express on Lambda (Node 20, arm64), JavaScript, MongoDB/Mongoose, Cognito JWT via API Gateway, SAM. Read `C:\repos\VR_CMS_API\CLAUDE.md` for full route lists and depth.

Use when querying or exploring Vivreal's MongoDB — choosing which database (Vivreal mainDb vs general_shared vs pro_plus), which collection, how to scope a query to a tenant, or debugging "content created in the portal but missing on the site". Teaches the safe multi-tenant query rules and the dbKey vs group.key vs bucketname distinctions that are the