PROMPT
# Frontend ROAS Campaign Strategy for Health Supplement Using quest-webflow-system-7990-07990
## EXPERT ROLE
Act as a senior Frontend specialist. Solve the exact task. Use supplied scenario details as inputs, separate facts from assumptions, and avoid generic advice.
## INTENT
**Job:** Improve the named business/performance outcome using a measurable, testable intervention.
**Audience:** Professionals or practitioners using AI for frontend tasks.
**Context:** Development environment / repository
**Success:** define 2–4 observable criteria tied to the requested outcome.
## WORKING BRIEF
Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims.
> Act as Senior Frontend Strategist for Developer Prompt (experienced, scaled Health Supplement to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Health Supplement - $12M ARR, team 22, targeting SMB owners, stage Series A Current: CAC $139, LTV $1479, churn 7%, traffic 14209/mo, conversion 4.0% Assets: 200 blogs 10 case studies Goal: achieve 4.8 ROAS in 90 days Constraint: Budget $15k/mo, team of 3 Tone: calm luxurious Aesop FRAMEWORK: QUEST + structured 4-step. TASK: Complete Frontend system for Developer Prompt / Health Supplement. - common failure modes about frontend for Health Supplement - 5 Whys root cause for achieve 4.8 ROAS - Hidden cost of failure - Contrarian insight advanced practitioner insight Variant A (Origin Story): Subject/headline 10 options with hypothesis, preview 3, body 250 words with {{FirstName}} tags PS PPS, visual brief, CTA, send logic delay trigger segment. Include placeholder [BRAND][AUDIENCE][DATA] + filled example for Health Supplement Variant B (Objection Crusher): Same structure different angle Variant C (Referral Ask): Same structure third angle Each variant must be fundamentally different not reworded OUTPUT: Markdown H2/H3 tables copy blocks ready for Notion/Google Docs/Webflow, both placeholder and filled side by side No generic advice, every sentence actionable, specific numbers, decision tree If [condition] then A else B, no buzzwords without definition
## EXECUTION
Developer Goal → Context → Technical Requirements → Implementation Plan → Edge Cases → Tests → Review. Complete the task in the smallest complete workflow that solves it. Make inputs, decisions and deliverables explicit. Return the requested result, not a description of the workflow.
## FAILURE PREVENTION + QA
Watch for: requirements ambiguity; architecture drift; edge cases missed; tests absent. Apply only relevant prevention rules. Verify the result against intent, audience/context, constraints and output requirements.
## ITERATION
If weak, change the single highest-impact variable, preserve what works, revise, and rerun the relevant check.
## OUTPUT CONTRACT
Return a specific, immediately usable result. Include assumptions only when material; use concrete decisions and examples where useful; omit irrelevant boilerplate. Do not merely restate this prompt.
## SPECIALIST STANDARD
Judge the result using the professional standards of **Frontend**. Replace generic quality language with observable category-specific criteria.
## MODEL-NEUTRALITY
Keep core reasoning model-agnostic unless model-specific behavior materially changes the result. When a model is specified, adapt only the relevant syntax or capability.
## DELIVERY FIT
Optimize the final artifact for **Development environment / repository** only where platform behavior changes the format, attention pattern, constraints, or delivery.
## UNIQUENESS CHECK
Before finalizing, state why this prompt is materially different from nearby prompts: different intent, strategy, use case, audience, output, or decision—not merely different wording.