Indie Dev Chaos Cleanup Kit

1. Analyze the Request:

• Product: "Indie Dev Chaos Cleanup Kit"
• Format: Markdown (headings, short paragraphs, bullet lists)
• Goal: Pre-orders or email waitlist sign-ups (target: 50 leads)
• Checkpoint: 72 hours
• Kill Rule: Max 3 iterations without revenue
• Boost Rule: Min $500 revenue
• Clone Rule: Min $2000 revenue
• Channel: Owned site
• Price: $29 (but also "pay-what-you-want" early bird discount)
• Distribution: Landing page with pay-what-you-want early bird, then digital download via Gumroad/LemonSqueezy
• Maintenance: Static repo, updates only from user feedback in first 30 days
• Constraints: Be honest/specific, no fake testimonials/numbers/claims, don't invent prices/links/buttons beyond what's given (price $29 is given, but also pay-what-you-want early bird - I'll be careful not to invent fake URLs or specific payment gateway details beyond the named platforms Gumroad/LemonSqueezy which are in the plan)

1. Deconstruct the Product & Plan:

• Name: Indie Dev Chaos Cleanup Kit
• Target audience: Indie developers, solo devs, people overwhelmed with project mess, disorganized codebases, tooling chaos, etc.
• It's a cleanup kit - likely some tools, templates, checklists, maybe scripts to organize indie game/dev projects.
• Pricing: $29 standard, but early bird pay-what-you-want to drive conversion/validation.
• Goal: 50 leads/pre-orders via email waitlist.
• Timeline: 72-hour checkpoint.
• Post-validation: Digital download via Gumroad/LemonSqueezy.
• Maintenance: Static site/repo, updates from feedback loop in first 30 days.

1. Determine the Content Structure (Markdown):

• Heading: Main title
• Subheadings: Problem, Solution, What's Inside, Pricing/early bird, How it works, Target audience, Contact/Email sign-up
• Short paragraphs
• Bullet lists for features/what's inside
• Honest, no fake testimonials
• No invented prices beyond $29 and pay-what-you-want mention
• No fake links, but can mention Gumroad/LemonSqueezy as the distribution method per the plan

I need to be careful: "Do not invent prices, links or payment buttons." The plan says priceUsd:29 and pay-what-you-want early bird, and distribution via Gumroad/LemonSqueezy. I can mention the $29 price point and the pay-what-you-want early bird concept, but I shouldn't invent actual payment button HTML or specific URLs. I'll just reference the platforms names as given in the plan, maybe as text, not as clickable links I'm inventing. Or I can just say "available on Gumroad/LemonSqueezy" without a URL. That should be safe.

I also need to adhere to the "honest and specific about what it is and who it is for" constraint. I'll describe it realistically: a collection of checklists, organizational templates, maybe some bash/scripts or docs to help indie devs clean up their project mess. Not overpromising.

1. Drafting - Section by Section (mental or scratchpad):

Heading: # Indie Dev Chaos Cleanup Kit

Subheading or short paragraph: What it is, who it's for.

Let's structure:

• headline
• paragraph problem
• bullet list: what's inside (features, but honest)
• paragraph: pricing/early bird
• paragraph: how it works/distribution
• bullet list: target audience
• maybe a CTA paragraph for email sign-up

Must not invent fake stats. Keep it grounded.

Let's outline actual content:

   # Indie Dev Chaos Cleanup Kit

   A curated collection of checklists, folder structures, script templates, and documentation foundations to help indie developers tame project chaos and get back to building.

   Whether you're jumping between game jams, managing a side project, or just tired of wondering "where is that asset?", this kit gives you a proven starting point.

   * What's Inside
   * Project inventory checklist
   * Standard folder structure template
   * Build & release script skeleton
   * Asset naming convention guide
   * Quick cleanup runbook

   Early bird: pay-what-you-want
   For the first 72 hours, you can grab the kit for as little as you'd like (minimum $5 to cover costs). After that, the price locks in at $29.

   Once validated (hitting 50 leads or $500 in revenue), the kit will be released as a digital download via Gumroad or LemonSqueezy.

   Built for solo devs, hobbyists, and anyone who've started an indie project and let the folder structure drift into oblivion.

   📧 Want early access? Enter your email below to join the waitlist.

Wait, the constraint says "Do not invent prices, links or payment buttons." I included "$5 to cover costs" as a minimum for pay-what-you-want. The plan says "pay-what-you-want early bird discount to drive conversion". It doesn't specify a minimum, but I should keep it general or stick to what's implied. Maybe just say "pay-what-you-want" without inventing a min amount, or say "choose your own price". I'll avoid putting a specific number for the minimum to stay safe. I'll just say "pay-what-you-want (you set the price)".

Also, "Once validated (hitting 50 leads or $500 in revenue)" - the plan has checkpointHours:72, killRule maxIterationsWithoutRevenue:3, boostRule minRevenueUsd:500, cloneRule minRevenueUsd:2000. I can reference the goals/metrics honestly without faking results. I'll phrase it as "the goal is to reach..." not "once we hit...". Actually, the page copy is for pre-orders/sign-ups, so I can state the goal. I'll be careful: "Our goal is to collect 50 email sign-ups or $500 in revenue within the first 72 hours..." That's honest, it's the plan's metrics.

Let's re-read the prompt: "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims. Do not invent prices, links or payment buttons." So I can state the price $29 as given, and the pay-what-you-want early bird concept. I should not invent a specific minimum for pay-what-you-want, or if I do, keep it very generic or omit. I'll just say "pay-what-you-want early bird" and mention the $29 standard price.

Also, "Do not invent ... links". I'll mention "Gumroad or LemonSqueezy" as text, no URLs.

Let's draft the markdown carefully.

Structure:

• H1: Indie Dev Chaos Cleanup Kit
• H2 or paragraph: What it is
• Short paragraph: Problem/goal
• Bullet list: Features/components (honest, no fluff)
• Paragraph: Pricing model (early bird $29 standard, pay-what-you-want window)
• Paragraph: Distribution/validation timeline (72h checkpoint, 50 leads/$500 goal)
• Bullet list: Target audience
• Paragraph: CTA for email waitlist

Make sure no fake numbers like "used by 1000 devs" etc. Keep it tiny/small indie.

Let's write it. I'll ensure each paragraph is short, bullets are concise. I'll avoid any "testimonial" style. I'll include the goal metric honestly: "Target: 50 email sign-ups or $500 in revenue within 72 hours." That's from the plan, I'm just stating the goal.

Check constraints again:

• markdown: headings, short paragraphs, bullet lists ✓
• goal metric: pre-orders or email waitlist sign-ups (target: 50 leads) ✓
• checkpoint hours: 72 ✓ (I'll mention the 72-hour window)
• kill rule, boost rule, clone rule: I can reference the framework honestly but maybe not dump all jargon; I'll integrate the essence naturally or keep it brief. The prompt says "Plan: {...}" but the output is the web page copy. I should probably not repeat the entire plan JSON, but I can allude to the validation logic honestly. The page copy should be for visitors, not necessarily repeat the internal plan. But I can mention the 72-hour checkpoint and the goal. I'll keep it visitor-friendly: "We're running a 72-hour early bird period to validate interest."
• boost clone rules: maybe not mention at all, or mention the goal metric. I'll stick to the visible goals.
• channel

# Find and delete orphaned .meta files (run from the project root)
Get-ChildItem -Recurse -Filter "*.meta" | Where-Object {
    -not (Test-Path ($_.FullName -replace '\.meta$'))
} | Remove-Item -Force -WhatIf