agentleFS
notum-cznotum-cz/strapi-next-monorepo-starter/CLAUDE.md

strapi-next-monorepo-starter

CLAUDE.md316 starsChanged 5 months agoMITView on GitHub

Monorepo starter with Strapi v5 CMS, Next.js 16 UI, Docusaurus docs, pnpm workspaces, and Turborepo. Config-only workspaces (@repo/eslint-config, @repo/typescript-config, @repo/semantic-release-config) are omitted from the table. Run commands from the monorepo root unless a docs page says otherwise. See Commands Reference for the full command list, package filters, worktrees, testing, and cleanup scripts. @repo/strapi-types is generated from the Strapi schemas and regenerates automatically when Strapi restarts after a schema or component change — no manual step in normal dev. If you…

The file

We split this CLAUDE.md into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run commands from the monorepo root unless a docs page says otherwise.

    line 22
  2. Distinctive:

    Start with Documentation Overview for the stack, included capabilities, and links across the docs.

    line 43
  3. Distinctive:

    Use these pages for common coding-agent tasks:

    line 45
  4. Distinctive:

    Use Conventional Commits. The repo enforces branch naming and commit messages through Lefthook and commitlint.

    line 65
  5. Very specific:

    When adding environment variables, mention them in the commit body as env.VARIABLE_NAME or VARIABLE_NAME in CONSTANT_CASE so the Auto PR …

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Strapi + Next.js Monorepo

Monorepo starter with Strapi v5 CMS, Next.js 16 UI, Docusaurus docs, pnpm workspaces, and Turborepo.

Workspaces

PathDescription
apps/uiNext.js 16 App Router, React 19, TailwindCSS v4, shadcn/ui
apps/strapiStrapi v5 CMS with PostgreSQL through Docker
apps/docsDocusaurus documentation site (port 3300)
packages/strapi-typesAuto-generated TypeScript types from Strapi schemas
packages/design-systemShared TailwindCSS tokens, CKEditor and TipTap editor styles
packages/shared-dataShared constants and types
packages/loggingStructured pino logging + OpenTelemetry trace context (@repo/logging)
qa/tests/playwrightE2E, accessibility, SEO, visual, and Lighthouse tests

Config-only workspaces (@repo/eslint-config, @repo/typescript-config, @repo/semantic-release-config) are omitted from the table.

Essential Commands

Run commands from the monorepo root unless a docs page says otherwise.

pnpm dev              # Start all apps
pnpm dev:strapi       # Start Strapi only
pnpm dev:ui           # Start Next.js only
pnpm dev:docs         # Start Docusaurus only on port 3300
pnpm build            # Build all
pnpm lint             # ESLint all packages
pnpm typecheck        # Typecheck all packages
pnpm test             # Vitest in all apps

See Commands Reference for the full command list, package filters, worktrees, testing, and cleanup scripts.

Generated types

@repo/strapi-types is generated from the Strapi schemas and regenerates automatically when Strapi restarts after a schema or component change — no manual step in normal dev. If you need fresh types without restarting Strapi, run pnpm generate:types. See Strapi Types.

Documentation Routing

Start with Documentation Overview for the stack, included capabilities, and links across the docs.

Use these pages for common coding-agent tasks:

  • Commands Reference — Root scripts, package filters, worktrees, tests, and cleanup commands
  • Workflow — Git hooks, branch naming, Conventional Commits, env vars in commits, and release notes
  • Quick Start — Local setup flow
  • Add Content Type — Strapi schema-to-UI implementation workflow
  • Page Builder — Dynamic zones, component registry, rendering, and population rules
  • Pages Hierarchy — URL structure, redirects, breadcrumbs, and page relationships
  • UI Project Structure — Next.js app layout and route organization
  • Strapi API Client — Fetching Strapi content from server and browser-safe clients
  • Authentication — Better Auth session handling and Strapi JWT integration
  • Strapi Schemas — Content types, components, relations, localization, and document middlewares
  • Strapi Types — Generated type utilities and usage patterns
  • Design System — Tokens, typography, rich text styles, and CMS component design guidance
  • Testing — Unit, Playwright, accessibility, visual, SEO, and Lighthouse coverage
  • Deployment — GitHub Actions, Heroku, Vercel, and Docker notes
  • AI Skills — Agent skills catalog, per-skill What/How/When, and workflow diagrams

Commits

Use Conventional Commits. The repo enforces branch naming and commit messages through Lefthook and commitlint.

pnpm commit    # Interactive Commitizen flow

Manual format:

type(scope): subject

When adding environment variables, mention them in the commit body as env.VARIABLE_NAME or VARIABLE_NAME in CONSTANT_CASE so the Auto PR workflow can surface them. See Workflow for details.

Agent skills

Reusable agent instructions live in .claude/skills/ — the single source of truth, auto-discovered by Claude Code. A committed symlink at .agents/skills/ exposes the same set to any agent following the agentskills.io standard (Codex, Copilot CLI, Gemini). Vendored community skills are installed via skills.sh and tracked in skills-lock.json.

See .claude/skills/README.md for the authoring guide and full catalog, and the AI → Skills docs (with workflow diagrams) for what each skill does and how they chain. Worktree-based isolation is wired through the start-work skill.

This file (CLAUDE.md) is mirrored as AGENTS.md (a symlink) for non-Claude agents; the same pairing exists in apps/ui and apps/strapi.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.