8fb170c5e4
Document development/main branch strategy. Remove stale note about components/ directory not existing. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
Commands
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); notailwind.config.*file; theme tokens defined inapp/globals.cssusing@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
developmentis the working branch — all new work starts heremainis deployment-only — never commit directly tomain- Merge
development→mainonly 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