Files
Portfolio/CLAUDE.md
Jonathan 8fb170c5e4 Add git workflow and tidy CLAUDE.md
Document development/main branch strategy. Remove stale note about
components/ directory not existing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-26 22:43:34 +01:00

44 lines
1.6 KiB
Markdown

# CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
## Commands
```bash
npm run dev # Start development server
npm run build # Production build
npm run start # Start production server
npm run lint # Run ESLint
```
No test runner is configured.
## Stack
- **Next.js 16** with App Router — read `node_modules/next/dist/docs/` before writing any Next.js code; APIs may differ from training data
- **Tailwind CSS v4** — configured via PostCSS (`postcss.config.mjs`); no `tailwind.config.*` file; theme tokens defined in `app/globals.css` using `@theme inline`
- **TypeScript** — strict mode, path alias `@/*` maps to project root
## Architecture
This is a portfolio site built with the Next.js App Router. All routes live under `app/`. Global styles and theme variables are in `app/globals.css`. Fonts (Geist Sans/Mono) are loaded in `app/layout.tsx` and injected as CSS variables.
Reusable UI components live in `components/`. Project data (e.g. `projects.json`) lives in `content/`.
## Git Workflow
- **`development`** is the working branch — all new work starts here
- **`main`** is deployment-only — never commit directly to `main`
- Merge `development``main` only when code is ready to deploy
## Project Rules
- Functional components only — no class components
- All styling via Tailwind utility classes — no CSS modules or inline styles
- Dark mode by default; use Tailwind dark-mode utilities
- Keep components small and single-purpose
- Prefer readability over cleverness
- Do not add features unless explicitly asked