Claude Rules for Full-Stack Projects
CLAUDE.md rules for full-stack projects. Covers monorepo structure, shared type definitions, frontend/backend conventions, and cross-stack development patterns.
0 rules matching Full-Stack
Full-Stack CLAUDE.md Rules
Full-stack projects are where CLAUDE.md files earn their keep most. Spanning frontend, backend, database, and deployment infrastructure means there are dozens of conventions Claude needs to know — the monorepo layout, which package owns the shared types, how authentication flows across boundaries, which package manager runs at the repo root, and where API contracts live. Without it, Claude often reaches across boundaries it shouldn't cross, generating frontend code that imports from backend-only modules, or backend code that pulls in browser-specific dependencies. A full-stack CLAUDE.md sets the boundaries explicitly: it maps the monorepo, lists which packages communicate with which, identifies the shared type layer, and names the deployment targets. The community examples below come from real Turborepo, Nx, and pnpm-workspace projects — useful templates whether your stack is Next.js + Hono, T3, Remix + Drizzle, or something custom.
No Full-Stack rules yet
Share your CLAUDE.md and help other developers building Full-Stack projects with Claude.
Submit one →Why add Full-Stack rules to your CLAUDE.md?
Full-stack projects are where CLAUDE.md files earn their keep most. Spanning frontend, backend, database, and infrastructure means there are dozens of conventions Claude needs to know. A full-stack CLAUDE.md typically maps out the monorepo structure, explains which package handles what, defines the shared type layer, and clarifies where API contracts live — so Claude doesn't accidentally reach across boundaries it shouldn't cross.