React stack pack

Frontend-focused additions on top of Node-TS or Node-JS. Component patterns, accessibility, testing-library conventions, build-performance heuristics. Designed to compose, not stand alone.

Audience #

Pick React if:

Your project ships a React UI (Vite, Next.js, Remix, Astro-with- React, a plain webpack/SWC build, or a React component library).
You want skills that nudge toward accessibility, Testing-Library patterns, and component-shape discipline.

React is not a standalone pack. Combine it with Node-TS or Node-JS:

aidokit init --stack node-ts,react
# or
aidokit init --stack node-js,react

If you init --stack react alone, aidokit will warn and add Node-TS automatically (the most common case).

Auto-detection triggers #

aidokit init detects this pack when:

package.json declares react as a dependency
A tsconfig.json references jsx, react, or react-jsx
.jsx or .tsx files exist under src/components/, app/, or similar conventional locations
A next.config.*, vite.config.*, or remix.config.* is present

Force it:

aidokit init --stack react   # also adds node-ts

What you get (on top of Node-TS / Node-JS) #

Component	Provided
Suggested skills	`react-component-conventions`, `testing-library-patterns`, `accessibility-checks`, `build-performance-hints`, `state-management-discipline`
Suggested MCPs	Playwright (escalated from optional → suggested for React projects), Chrome DevTools MCP (when present in catalog)
Validation commands	Inherits from underlying pack; adds `npm run build` to the validation step at Strict so CI catches type/JSX breakage early
Architecture hint (Strict)	Container/Presentational separation, Server Components only when `next/server` patterns are detected, Hooks-only state

Composition #

Required base: Node-TS or Node-JS.
Plays nice with: Python (for the backend), Go (for the backend).
Conflicts: none — but combining React with non-React UI packs in the same --stack is not supported.

Honest limitations #

Framework-specific patterns are shallow. Next.js App Router, Remix routing conventions, and Astro islands all get some coverage, but framework-specific deep dives are deferred to project-local skills.
CSS / styling is hands-off. Tailwind, CSS Modules, styled- components — no opinion forced. Your project's own conventions stand.
Server-side rendering edges. The pack assumes a clear client/ server split. Mixed RSC / Server Actions / API Routes projects work but get less validation-command guidance.
No design-system integration. Storybook configuration is detected but not configured; that's a project-local skill.