strapi-next-monorepo-starter

Use when adding a new CMS entity that needs its own REST endpoint and DB table — e.g. "add content type", "new content type", "create strapi collection", "new single type", "add strapi model", "new entity". Not for page-builder sections; use `create-content-component` for those.

Use when adding a new language/locale to the application — e.g. "add language", "add locale", "new language", "new translation", "internationalization". Touches Strapi admin config, Next.js i18n routing, and translation files.

Use when adding a generic UI primitive, elementary block, or form field in `apps/ui` — e.g. "new ui component", "add component", "create react component", "new shadcn component", "add form field". Not for Strapi page-builder sections; use `create-content-component`.

Use as a checkpoint after building several page-builder components, to remove duplication — e.g. "consolidate patterns", "extract reusable", "dedupe components", "review components for shared patterns". Extracts JSX/Tailwind repeated across 2+ components into shared elementary components. React-only — never touches Strapi schemas.

Use to replicate a page-builder section from a reference — a text description, a screenshot, or an HTML/code snippet. Triggers: "copy component", "replicate component", "recreate this section", "build from screenshot", "make a component like this", "convert this HTML/JSX into a component", "port this section". Not for generic UI primitives (use `add-ui-component`) or API resources (use `add-content-type`).

Use when adding a new CMS-driven page section that lives in the page builder's dynamic zone — e.g. "add page component", "new page section", "page builder component", "create content component", "add section", "new strapi component". Not for top-level API resources (use `add-content-type`) or generic React components (use `add-ui-component`).

Use when checking whether a page-builder component already exists before building one — e.g. "find component", "does a component exist for", "is there a component that", "match this screenshot", "identify this section", "reuse existing component", "what renders this". Searches existing Strapi page-builder components by description or by a UI screenshot, then recommends reuse or `create-content-component`.

Use when the user is ready to submit work for review and wants a GitHub pull request opened — e.g. "open PR", "create pull request", "prepare PR", "make PR", "submit for review".

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Uninstalls the entire Next.js cache revalidation feature (Strapi document middleware, revalidate API, on-demand UI route, cache tagging, admin revalidate button) AND the optional CDN purge layer it carries. Triggers: remove cache revalidation, remove revalidation feature, uninstall revalidation, drop revalidate, disable on-demand revalidation, remove strapi-revalidate.

Uninstalls the optional CDN purge integration (Azure Front Door example provider, CDN cache widget, /api/cdn-purge route) while keeping the core cache revalidation feature intact. Triggers: remove CDN purge, remove Front Door, uninstall CDN, drop cdn-purge, remove Azure Front Door integration, disable CDN cache widget.

Use when the user wants unresolved GitHub pull request review comments addressed and closed with the authenticated GitHub CLI (`gh`) — e.g. "resolve review suggestions", "address PR comments", "fix review comments", "handle requested changes", "apply review feedback", "/resolve-review-suggestions". GitHub-only; unsupported for GitLab, Bitbucket, Azure Repos, or local-only branches. Requires an explicit GitHub PR number or PR URL.

Use when the user wants a thorough review of a GitHub PR or a local feature branch's diff before merge — e.g. "review PR", "review pull request", "review this branch", "review the diff", "feature review", "/review-pr". Accepts a PR number/URL or runs against the current branch.

Use when populating the local Strapi with content programmatically through MCP — e.g. "seed content", "seed a page", "import content into strapi", "create demo content", "add a page with components". Schema-driven create/update of pages, navbar, and footer via the Strapi MCP server. For reproducible baseline content, use the native export/import seed flow instead.

Use when the user is ready to begin a new fix or feature and wants an isolated workspace — e.g. "start work on", "fix issue", "new feature", "begin task", "work on issue", "/start-work". Accepts a GitHub, Linear, or Jira issue (number, key, or URL) or a plain branch name.

Use any time a Strapi v5 schema file is edited — auto-loads on changes to `apps/strapi/src/api/**/schema.json` or `apps/strapi/src/components/**/*.json`. Also triggers on "strapi schema", "schema check", "strapi migration", "check schema", "did I break the schema". Flags renames, deletes, type changes, and tightened constraints that need a database migration.

Use when checking a branch for drift before merge — references or claims a diff left stale: renamed/moved paths, removed exports, changed signatures, dropped env vars, dead doc links, outdated commands or version/port numbers. Triggers: "validate references", "check stale refs", "validate branch", "fix outdated docs", "/validate-branch-refs". Compares current branch vs base (default `dev`) and writes fixes.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Use when asked to add or extend automated tests — e.g. "write test", "add test", "cover X with tests", "reproduce with a test", "test this", "e2e test", "playwright test". Covers Vitest (apps/ui, apps/strapi) and Playwright (qa/tests/playwright: e2e, visual, axe, seo).

Completely remove the Azure Monitor / Application Insights telemetry exporter from this monorepo while keeping pino structured logging (@repo/logging) and OpenTelemetry trace context intact. Use whenever the user wants to drop Azure Monitor, remove Application Insights, delete @azure/monitor-opentelemetry, remove the @repo/logging/azure target, or stop shipping logs/traces to Azure. The logger (logger/logError/withSpan) and all its call sites must keep working — only the Azure exporter goes.

Completely remove Sentry from this monorepo — both the Next.js UI (@sentry/nextjs) and Strapi (@strapi/plugin-sentry) — while keeping pino structured logging (@repo/logging) intact. Use whenever the user wants to drop Sentry, remove error tracking, stop using @sentry/nextjs, delete the Sentry provider/integration, or clean Sentry out of the starter. The logger (logger/logError/withSpan) and all its call sites must stay working.