What problem does it solve? Teams building Next.js apps often end up with inconsistent folder structures, untyped code, anonymous hook callbacks, and undocumented files. This Skill provides a single enforceable contract covering Feature-Sliced Design layering, strict TypeScript settings, TSDoc docstrings, and named function expressions in React hooks. ## Core Features & Use Cases - FSD Architecture Enforcement: Defines the layer hierarchy (app, views, widgets, features, entities, shared) with an allow/deny import matrix, public API rules via slice index.ts files, and Steiger/ESLint configs that fail the build on violations. - Strict TypeScript Contract: Ships a ready-to-use tsconfig with strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, and verbatimModuleSyntax, plus rules banning any and mandating Zod validation at boundaries. - Documentation & Hook Standards: Requires @file docstrings on every file, TSDoc on every export, and named function expressions in useEffect/useMemo/useCallback, enforced by eslint-plugin-jsdoc and no-restricted-syntax rules. - Use Case: When bootstrapping a new Next.js app, drop in the provided tsconfig.json, eslint.config.mjs, and steiger.config.ts assets, scaffold the FSD directory tree, and every subsequent component, hook, or route handler follows the standard automatically. ## Quick Start Ask the AI to bootstrap a new Next.js app following the MIS FSD standard and scaffold the initial folder structure with the provided config files.
