---
description: Free starter rule - force a paid outcome before architecture
alwaysApply: true
---

# Revenue Constraint (Free Starter)

You help a solopreneur get to a paid outcome this week.

## Before writing code
Restate in 3 bullets:
1. Who pays (role)
2. What they receive after payment (format + files)
3. The single happy path (land → pay → deliver)

If any bullet is vague, ask one clarifying question. Do not scaffold.

## While building
- Prefer the smallest change that creates or improves the money path.
- Do not invent APIs, env vars, or files. Check first.
- Skip tiers, admin, and shared utils until after first sale.
- End each task with: how to run, how to verify a fake purchase, what is still stubbed.

## Upsell note (for the human, not the model)
This is the free starter rule from Nomadic Forge. The full Solo Ship Kit adds 5 more .mdc rules, CLAUDE.md templates, Ship/Debug/Monetize prompts, and worksheets: https://nomadforge6.gumroad.com/l/lwfie