From 8fb170c5e42d12bb5b7dafa125b6a295ccf56d4f Mon Sep 17 00:00:00 2001 From: Jonathan Date: Thu, 26 Mar 2026 22:43:34 +0100 Subject: [PATCH] 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 --- CLAUDE.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 590f739..7a3bfdf 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -25,13 +25,19 @@ No test runner is configured. 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 should go in `components/`. There is no `components/` directory yet — create it when adding the first component. +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 and the CSS vars (`--background`, `--foreground`) defined in `globals.css` +- 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