CLAUDE.md Starter

# Project Rules

## About this project
[Describe your app in one or two sentences. What does it do, and who is it for?]

## The stack
These are the tools this project uses. Stick to them unless I say otherwise.
- Next.js (App Router) for the website and its backend, in one project.
- Vercel for hosting and deploys.
- Clerk for sign-in and accounts.
- Neon Postgres for the database.
- Vercel Blob for file and image storage.
- QStash for background jobs that run after a request finishes.
- Creem or Stripe for taking payments.
- Resend for sending email.
- PostHog for product analytics.
- Sentry for catching errors in production.
- Tailwind CSS for styling.
- GitHub Actions for running checks and deploying.

## How to work with me
- I am not a coder. Do not assume I can read code.
- Explain every change in plain language. Tell me what changed and why.
- Do not over-engineer, and do not add things I did not ask for.
- Keep changes small and focused. One thing at a time.
- Ask me first before anything destructive or hard to undo: deleting data, force-pushing, or deploying.
- Show me a feature works by describing what it does, not by asking me to read the code.

## Rules
- Never put secrets or API keys in the code. Always keep them in the .env file.
- Never commit the .env file. It stays on my machine only.
- Prefer the stack listed above unless I tell you to use something else.
- When you are unsure what I want, ask me before you build it.

Stack recipes

Not every project needs the full stack. To swap the tools, replace the ## The stack section in your CLAUDE.md with one of these.

## The stack
Use this for a full product: real users, a database, and payments.
- Next.js (App Router) for the website and its backend, in one project.
- Vercel for hosting and deploys.
- Clerk for sign-in and accounts.
- Neon Postgres for the database.
- Vercel Blob for file and image storage.
- QStash for background jobs that run after a request finishes.
- Creem or Stripe for taking payments.
- Resend for sending email.
- PostHog for product analytics.
- Sentry for catching errors in production.
- Tailwind CSS for styling.
- GitHub Actions for running checks and deploying.

## The stack
Use this for a content or marketing site: landing pages, a blog, no sign-in, no payments.
- Astro for the pages, kept fast and mostly static.
- Cloudflare Pages for hosting and deploys.
- Tailwind CSS for styling.
- Resend for sending email, only if you add a contact or newsletter form.
- PostHog for visitor analytics, if you want it.
Keep it minimal. No accounts, no database, and no payments unless I ask.

## The stack
Use this for an internal tool: an app your own team logs into, with no public sign-up and no payments.
- Next.js (App Router) for the app and its backend, in one project.
- Vercel for hosting and deploys.
- Clerk for sign-in, locked to your team only.
- Neon Postgres for the database.
- Sentry for catching errors.
- Tailwind CSS for styling.
- GitHub Actions for running checks and deploying.
No payments, and no public marketing pages. This app is for your team.