forge CLAUDE.md

This project uses Forge. The methodology below is imported from a local file regenerated by forge upgrade. New collaborator? Install Forge with:

npm install -g @firatcand/forge
forge upgrade

First time opening this repo in Claude Code? You'll see a one-time prompt asking permission to load .forge/CONTEXT.md. Accept it — without that approval, Claude Code silently skips the import and the methodology context won't be available.

@.forge/CONTEXT.md

The import below pulls in THIS project's spec — the synthesized BRIEF/PRD/SPEC (the "what", vs. the methodology "how" above). It is committed and generated by /ingest-spec (a stub until you run it), so it travels with the repo.

@spec/CONTEXT.md

forge

Note: This is the forge repo itself. Iterating on this repo means iterating on the framework — every change ships to npm publish @firatcand/forge and lands on adopter machines via npx @firatcand/forge. Treat all changes as public-API.

Stack

Commands

• Build: npm run build
• Test: npm test
• Type check: npm run typecheck
• Lint: npm run lint (ESLint — unused vars/imports + unreachable; non-blocking, warnings only)
• Dev: npm run dev
• Render methodology context (one-shot, until Phase B's forge upgrade ships): npm run forge:render-context

Conventions

• Functional components only, no class components
• Always handle errors explicitly — no silent catches
• New API routes must have input validation
• See spec/ for full conventions

Critical paths

See CRITICAL.md