Project Context

Indexed automatically:
├── Source code files (.ts, .js, .py, etc.)
├── Configuration files (package.json, etc.)
├── Documentation (README, docs/)
├── Test files
└── Type definitions

Not indexed (by default):
├── node_modules/
├── .git/
├── Build outputs (dist/, build/)
├── Binary files
└── Large data files

# Dependencies
node_modules/
vendor/
.venv/

# Build outputs
dist/
build/
.next/
out/

# Large files
*.csv
*.sql
data/

# Sensitive files
.env*
secrets/
*.pem

# Generated code
*.generated.ts
coverage/

# Project: E-Commerce Platform

## Overview
This is a Next.js 14 e-commerce application with Stripe payments.

## Tech Stack
- Next.js 14 (App Router)
- TypeScript (strict mode)
- Tailwind CSS + shadcn/ui
- Prisma + PostgreSQL
- NextAuth.js for auth
- Stripe for payments

## Project Structure
- `/app` - Next.js pages and API routes
- `/components` - React components
- `/lib` - Shared utilities
- `/prisma` - Database schema

## Coding Conventions

### Components
- Use Server Components by default
- Add 'use client' only when needed
- Follow the component structure in /components/ui

### API Routes
- Validate input with Zod
- Use try/catch for error handling
- Return consistent response shapes

### Database
- Use Prisma for all database access
- Never write raw SQL
- Include relations in queries when needed

## Common Tasks

### Adding a new page
1. Create file in /app/[route]/page.tsx
2. Add server-side data fetching
3. Use components from /components

### Adding an API endpoint
1. Create route.ts in /app/api/[route]
2. Add Zod schema for validation
3. Include auth check if needed

## Important Notes
- All prices are in cents
- User IDs are UUIDs, not integers
- Use UTC for all timestamps

/context

/read src/lib/auth.ts
/read package.json

/search authentication

/tree

/tree src/components

You: Fix the bug in the checkout flow

Claude Code: [Automatically reads]
- src/app/checkout/page.tsx
- src/components/CheckoutForm.tsx
- src/lib/stripe.ts
- src/app/api/checkout/route.ts

Analyzing the checkout flow...

Look at @src/lib/utils.ts and @src/types/index.ts

Claude Code: Context is getting full. Would you like me to:
1. Summarize and compact the conversation
2. Focus on specific files only
3. Start a fresh conversation

[1/2/3]?

# ❌ Too verbose
Here is every detail about the project...
[2000 lines of documentation]

# ✅ Focused
## Tech Stack
[Key technologies]

## Conventions
[Important patterns]

## Notes
[Critical information]

# ❌ Walls of text
The project uses Next.js which is a React framework and we also use TypeScript for type safety and Tailwind CSS for styling and Prisma for the database and...

# ✅ Scannable structure
## Tech Stack
- **Frontend**: Next.js 14, React 18
- **Styling**: Tailwind CSS
- **Database**: Prisma + PostgreSQL
- **Auth**: NextAuth.js

## API Response Format

All API routes return:
```json
{
  "success": true,
  "data": { ... }
}

{
  "success": false,
  "error": "Error message"
}

## Multiple Projects

### Workspace Configuration

For monorepos or multi-project setups:

### Switching Context

Or start in a specific directory:

```bash
cd backend
claude

# E-Commerce Platform

A Next.js application selling digital products with subscription plans.

## Key Flows
1. User browses products
2. User adds to cart
3. User checks out (Stripe)
4. User accesses purchased content

## Business Rules

- Free users limited to 3 downloads/month
- Pro users get unlimited downloads
- Enterprise users can add team members
- Refunds allowed within 7 days

## Database Notes

- `users.plan` is denormalized for query speed
- Soft delete: check `deleted_at` is null
- All timestamps are UTC

# Add to your workflow
git commit -am "Add subscription feature"
# Also update .claude/instructions.md