biomeBiome 2.5 setup and rules for Nuvraxis monorepos — root biome.json with pinned $schema, VCS ignore, formatter settings, the recommended preset with a11y and the react/next domains, nursery policy, organize imports, overrides, nested per-package configs ("extends": "//"), biome check --write locally,
docker-nextjsDockerfile rules for Next.js standalone apps in a pnpm + Turborepo monorepo — multi-stage build (turbo prune → pnpm fetch/offline install → turbo build → minimal runner), pinned Node 26 Alpine by digest, checksum-verified pnpm binary, non-root uid 1001, read-only root filesystem with a writable .nex
github-actionsGitHub Actions conventions for Nuvraxis Next.js apps — exactly three workflows: pr.yaml (every PR to any branch: Biome, stylelint, typecheck/test/build with turbo --affected, Docker build + health check, helm lint + kubeconform; publishes nothing), main.yaml (push to main: one multi-arch image to GH
helm-nextjsHelm chart rules for Nuvraxis Next.js apps — one chart per app in charts/ (named after the app), published to oci://ghcr.io/nuvraxis/charts and synced by Argo CD; Chart.yaml version/appVersion set only by release.yaml; Deployment with startup/liveness/readiness probes on /api/health, non-root read-o
nextjs-productionProduction rules for Next.js 16 App Router apps at Nuvraxis — Server/Client Component boundaries, Cache Components ("use cache", cacheLife, cacheTag, updateTag), Server Actions, route handlers, env handling, instrumentation, output standalone and the /api/health route. Use when the project has "next
nextjs-securitySecurity rules for Next.js 16 App Router apps — authentication and authorisation in every Server Action and route handler, session cookies, nonce-based Content Security Policy in proxy.ts (with nuvui's requirements), security headers, server-only and secret handling, CSRF/origin checks, open redirec
nuvuiBuilds React interfaces with nuvui, the @nuvui/* component library for business software (forms, tables, charts, dashboards, chat, kanban, editor, maps, icons). Use when the project has an @nuvui package in its package.json, imports from "@nuvui/react" or another "@nuvui/" package, has classes that
pnpm-turborepoNuvraxis monorepo conventions on pnpm 12 and Turborepo 2.11 — packageManager pin without Corepack, pnpm-workspace.yaml as the only config (catalog, allowBuilds, minimumReleaseAge, trustPolicy), apps/* and packages/* layout with @repo/* source-only packages, workspace:* links, turbo.json tasks (input
scaffold-frontend-appCreates a new Nuvraxis frontend repo — pnpm + Turborepo monorepo with a Next.js 16 app, nuvui, Biome, SCSS + stylelint, a Dockerfile, a Helm chart and the pr/main/release workflows — from the plugin's tested templates, then proves it with typecheck, lint, build, docker build and helm lint.
scss-bemWrites and reviews SCSS for Nuvraxis Next.js apps with BEM class names (block__element--modifier), nuvui design tokens and stylelint. Use when creating or editing .scss files, adding styles to a React component, theming or dark mode, breakpoints, or a stylelint.config.mjs; also when package.json has
turborepoConfigure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
typescript-productionTypeScript 7 rules for Nuvraxis monorepos — strict tsconfig layering (packages/tsconfig), exactOptionalPropertyTypes and noUncheckedIndexedAccess, discriminated unions, branded ids, unknown over any, import type, as-const objects instead of enums, valibot parsing at the edges, Result types at bounda