Solo Founder

Your project

Live preview — CLAUDE.md

# My Product

TailorMD recipe: **Solo Founder**

## One-liner

Helps solo founders ship faster

## Audience

Indie hackers and solo founders

## Stack

Next.js + Vercel

## Engineering principles

- Ship small, vertical slices — one user-visible outcome per PR
- Prefer boring, proven tools over new dependencies
- Delete code aggressively; YAGNI unless a customer asked for it
- Every feature needs a way to verify it works (test or manual checklist)

## Folder map (adapt to your repo)

```
app/ or src/       # product code
content/           # marketing copy, blog drafts
docs/              # internal notes only — not user-facing
```

## Non-negotiables

- No scope creep in "quick fixes"
- Document env vars in `.env.example`
- Never ship without trying the happy path yourself
- Keep `main` deployable at all times

## Brand voice — Direct and helpful

When writing copy (UI, emails, landing pages, tweets):

- Tone: **Direct and helpful**
- Lead with the outcome for Indie hackers and solo founders, not feature lists
- Short sentences. No jargon unless the audience expects it
- Avoid hype words: "revolutionary", "game-changing", "disruptive"
- CTA should be specific: "Start free trial" not "Get started"

## Launch copy rules

- Headline: problem → outcome in under 10 words
- Subhead: who it's for + how it's different
- Social posts: one insight or one outcome, not a feature dump
- Email subjects: under 50 characters, no ALL CAPS

## Ship checklist

- [ ] Happy path works end-to-end
- [ ] Error states don't leak internals
- [ ] Copy matches brand tone above
- [ ] Analytics/event for the key conversion (if applicable)
- [ ] Changelog or "what's new" note drafted

## Commands

Use whatever your stack provides — common patterns:

```bash
npm run dev
npm run build
npm run test
```

Adjust for Next.js + Vercel.