Free Me Guide.

## Project
- **Stack**: Next.js 15, TypeScript, Tailwind CSS
- **Deploy**: Vercel

## Conventions
- Use App Router (not Pages Router)
- Prefer server components by default
- Use `cn()` from lib/utils for class merging
- UK English in all copy

## Structure
- app/ — routes and layouts
- components/ — reusable components
- lib/ — utilities, types, constants

## Rules
- Never modify .env files
- Always run the build before committing
- Use semantic commit messages

{
  "permissions": {
    "allow": [
      "Bash(npm run build)",
      "Bash(npm run lint)",
      "Bash(npm run dev)",
      "Bash(git status)",
      "Bash(git diff)",
      "Bash(git log:*)",
      "Bash(ls:*)",
      "Bash(cat:*)",
      "Bash(find:*)",
      "Bash(grep:*)"
    ]
  }
}

## Decisions
- **2025-01-15**: Use Supabase for auth, not NextAuth — simpler setup, row-level security built in.
- **2025-01-20**: All API routes return { data, error } shape — consistent error handling.
- **2025-02-01**: Images stored in /public/images/, never external URLs — offline dev works.

project-root/
├── CLAUDE.md              # Project instructions (loaded every session)
├── .claude/
│   └── settings.json      # Permissions and local config
├── app/                   # Routes (Next.js) or src/
├── components/            # Reusable UI
├── lib/                   # Utilities, types, constants
├── public/                # Static assets
├── package.json
└── tsconfig.json

Read my CLAUDE.md (if it exists), .claude/settings.json (if it exists), and package.json. Then report:

1. What project instructions exist and whether they cover: tech stack, conventions, file structure, and rules.
2. What permissions are configured and whether they match the scripts in package.json.
3. What MCP servers are connected (check .claude.json and .mcp.json).
4. What is missing or could be improved.

Do not change anything. Just report what you find in a clear summary.

Analyze this project:
1. Read package.json for the tech stack and scripts.
2. Read tsconfig.json or equivalent for language config.
3. Scan the top-level folder structure.
4. Look at 2-3 existing source files to understand patterns and conventions.

Then generate a CLAUDE.md file that covers:
- Project name and what it does (one line)
- Tech stack with versions
- Coding conventions you can infer from the existing code
- Folder structure explanation
- Any rules worth codifying (import style, component patterns, naming)

Show me the generated CLAUDE.md and ask for approval before writing it.

Read my package.json scripts and my current .claude/settings.json (if it exists).

For each script in package.json, suggest whether it should be added to the permissions allowlist and explain what the command does and why it is safe or unsafe to auto-approve.

Group your suggestions into:
- SAFE TO ALLOW: read-only commands, build commands, lint commands
- ALLOW WITH CAUTION: commands that modify files or state
- DO NOT ALLOW: commands that delete data, push to remote, or access secrets

Show me the complete .claude/settings.json you would write, with comments explaining each permission. Ask for my approval before writing anything.

Analyze this codebase and help me plan my next task:

1. Read the CLAUDE.md for project context.
2. Check git status and recent commits to understand what was done last.
3. Look at any TODO.md, open issues, or task comments in the code.

Then create a structured task plan:
- What needs to be done (broken into 3-7 concrete steps)
- Which files will likely be touched
- Any dependencies between the steps
- Estimated complexity (simple / moderate / complex)

Present the plan and ask what I want to start with.