vibes-marketing-validation

Generate brand visuals via the Higgsfield MCP — logo variants, moodboard tiles, and a brand-guidelines document — once the brand intake (`brand.json` + `saas-context.json`) exists. Auto-activate after `saas-brand-intake` finishes, or when the user says "generate logo", "make moodboard", "create visuals", `/generate-visuals`, `/regen-logo`, `/regen-moodboard`. Never fall back to other image generators if Higgsfield is unavailable — stop and report.

Enforce the brand approval gate. Use this skill BEFORE any landing page work. Reads/writes `brands/<slug>/approval.json`. Auto-activate when the user says "approve", "looks good, continue", "ship it", `/approve-brand`, or attempts to start the landing page. If approval is missing, refuse to start any landing work and route back to `saas-visual-generator` if visuals also need changes.

Shared library of Higgsfield MCP prompt patterns used by `saas-visual-generator` and `saas-landing-builder`. Auto-activate when another skill is about to call `mcp__higgsfield__generate_image`, `mcp__higgsfield__generate_video`, or `mcp__higgsfield__media_upload`. Centralizes the model picks, aspect ratios, durations, negative prompts, and output paths used across the flow.

Run SaaS brand intake interviews when the user wants to validate a new product idea. Use this when there is no existing brand directory and the user mentions a SaaS idea, says "I want to validate", "let's start a new brand", "I have an idea", "validate my SaaS", or runs `/new-brand`. Collects brand basics, SaaS context, and visual direction in three question clusters, then writes `brands/<slug>/brand.json` and `saas-context.json` and hands off to `saas-visual-generator`.

Build the SaaS landing page in `sites/<slug>/` once the brand is approved. Auto-activate when `approval.json.approved === true` and the user asks for a landing page, website, marketing site, or runs `/build-landing`. Generates a Next.js + Tailwind + Framer Motion app, wires Higgsfield-generated hero motion + feature micro-animations, writes SaaS copy from `brand.json` + `saas-context.json`, and ALWAYS places a `<Waitlist />` section at the bottom.

Pick and wire the waitlist backend adapter when generating the landing page. Auto-activate when `saas-landing-builder` is scaffolding the waitlist component. Chooses between local-JSON (default), Supabase, Resend, or Loops based on env vars and user preference, then writes the matching `app/api/waitlist/route.ts` and `lib/waitlist.ts` into `sites/<slug>/`.