- Analyze User Input:
- Product/Service: "Indie Game Expo Prompt Pack"
- Goal: Email signups
- Structure: Markdown with headings, short paragraphs, bullet lists
- Plan Details:
- 3 free sample prompts as gated download (booth checklist, pitch script, press kit template)
- Drive traffic via Discord, Reddit, Twitter
- Capture email + expo name + biggest prep pain point
- Deliver PDF instantly via email automation
- Quarterly updates for expo dates/requirements
- Monthly monitoring of email open/click rates
- Refresh landing page per checkpoint based on feedback
- No code maintenance; static site + email service only
- Constraints:
- Be honest and specific
- No fake testimonials, numbers, or claims
- Don't invent prices, links, or payment buttons
- Metadata: venture ID, stage APPROVE_PUBLISH, task f91e2e0e-6c1f-44c3-a505-c74d3227f0a2
- Deconstruct the Requirements:
- I need to write the complete public web page copy in markdown.
- It should have headings, short paragraphs, bullet lists.
- It must reflect the plan but be honest/specific.
- No fake data, no invented prices/links.
- Focus on the "Indie Game Expo Prompt Pack" concept.
- The gating mechanism is: 3 free sample prompts as a download in exchange for email + expo name + biggest prep pain point.
- Delivery is instant via email automation.
- Traffic sources: Discord, Reddit, Twitter.
- Maintenance: quarterly updates, monthly monitoring, refresh per checkpoint.
Key sections likely needed:
- Headline/Value prop
- What's inside (the 3 sample prompts)
- Who it's for
- How it works (the gate)
- Traffic/Community notes (maybe brief)
- Footer or CTA explanation
Since it's a "public web page," I should make it look like a landing page that explains what it is, who it's for, and gets them to sign up for the free gated download.
I need to be careful not to invent prices, payment links, fake testimonials, or exaggerated numbers. I'll stick to the facts from the plan.
- Drafting - Section by Section (Mental Outline):
- Hero Heading: Something clear about the Expo Prompt Pack
- Sub-headline: Who it's for + what they get
- What's Inside: Bullet list of the 3 sample prompts (booth checklist, pitch script, press kit template) - I'll describe them briefly without making up contents
- Who It's For: Indie devs, solo founders, small teams preparing for an expo
- How It Works: Simple 3-step process (enter email + expo name + pain point → get PDF instantly)
- Community & Traffic: Brief mention of where we share it (Discord, Reddit, Twitter) - but honestly, the web page copy might not need to advertise that; maybe a tiny footnote or just focus on the product. The plan says "Drive traffic via..." but the web page copy should be about the pack itself. I'll include a very brief, honest sentence about community sharing if needed, but keep it factual.
- What You'll Get: The 3 prompts as a PDF
- Sign-up Form conceptual: But since I can't make a form or add fake fields, I'll describe what's captured: email + expo name + biggest prep pain point, and that they get the PDF instantly via email.
- Maintenance/Updates: Quarterly refreshes, monthly analytics monitoring - honest statement.
Let's structure the markdown:
# Indie Game Expo Prompt Pack
Actually, let's plan the full copy in markdown format as requested. I'll make sure it's complete, honest, specific, no fake numbers/links/testimonials.
Important: The plan says "Publish 3 free sample prompts (booth checklist, pitch script, press kit template) as a gated download on the venture's site. Capture email + expo name + biggest prep pain point. Deliver PDF instantly via email automation."
So the core offer is: 3 prompts → gate → email + expo name + pain point → instant PDF delivery.
I'll write the page copy reflecting that exactly.
Let's draft:
# Indie Game Expo Prompt Pack
Prepare for your next expo with prompt-driven assets you can customize in minutes. This pack gives you three ready-to-use prompt templates designed to strip down the most time-consuming expo prep tasks.
### What’s Inside
- **Booth Checklist Prompt** – A structured prompt to generate a complete expo booth task list, from graphics to demo setup.
- **Pitch Script Prompt** – A concise, adaptable prompt to draft your investor/press pitch, tuned for expo audience attention spans.
- **Press Kit Template Prompt** – A prompt that outputs a press-ready blurb, key game facts, and contact snippets formatted for journalists.
### Who This Is For
- Solo indie developers preparing their first expo
- Small teams juggling multiple prep streams
- Creators who want to stop reinventing the wheel for each event
### How It Works
1. Enter your email, the name of the expo you’re preparing for, and your biggest prep pain point.
2. Instantly receive a PDF with your three prompt templates, pre-filled with expo-specific context where possible.
3. Use the prompts to generate booth checklists, pitch drafts, and press copy on the fly.
### What You’ll Capture
We’ll ask for:
- Your email address
- The expo name
- Your biggest prep pain point (e.g., “time,” “messaging,” “assets”)
In exchange, you get the PDF delivered to your inbox instantly—no waiting, no checkout.
### Community & Sharing
This pack is shared through indie devDiscord servers, the weekly r/IndieDev thread, and the #indiedev hashtag on Twitter. If you find the prompts useful, sharing the link helps keep the pack updated for everyone.
### Stay Updated
The prompt pack is refreshed quarterly to match new expo dates, requirements, and industry expectations. We monitor email open and click rates monthly to understand what’s working and what needs a refresh.
—
No pricing, no fake testimonials, no inflated claims. Just three practical prompts to help you show up ready.
Let's review against constraints:
- Markdown headings: Yes (###, #)
- Short paragraphs: Yes
- Bullet lists: Yes (What’s Inside, Who This Is For, etc.)
- Honest and specific: Yes, describes exactly the 3 prompts, the gate, the data captured, the delivery method
- No fake testimonials/numbers: Check
- No invented prices/links/payment buttons: Check - I didn't add any prices, links, or payment buttons. I mentioned community sharing channels factually per the plan, but without actual links.
- Reflects the plan: Yes - gated download, capture email+expo name+pain point, instant PDF, quarterly updates, monthly monitoring, traffic via Discord/Reddit/Twitter (mentioned briefly and honestly).
One thing: The plan says "Drive traffic via indie dev Discord announcements, Reddit r/IndieDev weekly thread, and Twitter #indiedev hashtag." My copy mentions "This pack is shared through..." which is fine for a public page, but I should make sure I'm not overpromising or inventing engagement stats. I'll keep it as a factual statement of where it's distributed.
Also, the plan says "Capture email + expo name + biggest prep pain point. Deliver PDF instantly via email automation." My copy has that exact 3-step/3-field process.
The maintenance plan: "Update prompt pack quarterly for new expo dates/requirements. Monitor email open/click rates monthly. Refresh landing page copy per checkpoint based on pain-point feedback. No code maintenance; static site + email service only." I included quarterly refresh and monthly monitoring. I didn't explicitly state "no code maintenance; static site + email service only" but I can add a small footer note or keep it implicit. The copy already says "No pricing, no fake testimonials, no inflated claims. Just three practical prompts..." I could add a brief line about maintenance but it's not strictly necessary for the "public web page copy" unless requested. The user asked for "complete public web page copy" - I think what I have is good. I'll maybe add a tiny footer sentence about quarterly updates and static site maintenance to be thorough.
Let's refine and finalize the markdown. I'll make sure every claim is grounded in the provided plan. No invented numbers. No fake testimonials. Exactly the offer.
One edge: The plan says "priceUsd: 0" and "distributionPlan: Publish 3 free sample prompts... as a gated download". So it's free, gated. My copy says "In exchange, you get