feature-dev-kit

Wire the routing table and lazy page import in the app layer, with every route wrapped in a route error boundary. Use after a page slice is created to make it reachable.

Add translated copy with react-i18next — slice keys in <slice>/locales/en.json + keys.ts, app-wide keys in shared/lib/i18n/locales/common. Use whenever a slice needs a new user-facing string, label, placeholder, aria-label, toast, validation message, or enum label — no hardcoded UI strings and no string maps.

Scaffold an FSD entity slice (model + api + ui). Wraps add-api-domain logic into the entity's api segment (hooks, types, queryKeys, apiMap). Use for a new business entity (profile, document, client, file).

Scaffold an FSD feature (interaction) slice with typed handlers and mutations, wrapped in an error boundary with its own translated locales — one user action that delivers business value (create/edit/decline, filters). Use after the relevant entities exist.

Scaffold an FSD page slice — a route-level screen composed from widgets/features/entities. Default export allowed per repo convention. Use after the widgets/features it composes exist.

HUMAN-ONLY ship command. Run after the human approved the feature at station 12. Verifies gates are green, rebases over develop, force-with-lease pushes, and opens a PR via gh with a body templated from the feature spec. Never auto-triggers.

Scaffold a React component in the correct FSD layer — presentational (entities/ui, shared/ui) or smart container (features/ui, widgets/ui) — with matching styles, tests, and index export. Uses real app patterns.

Add a UI-kit item to shared/ui by pulling it from the shadcn registry via the shadcn MCP and re-homing it verbatim — same style, Radix parts, data-slot, and registry open/close animation (tw-animate-css), plus closed-set constants (ButtonVariant) and index.ts. Hand-write only when the registry has no fit. Use when a feature needs a new shared primitive.

Core FSD scaffold. Create a <layer>/<slice>/{ui,model,api,lib,config,index.ts} structure with a correct public API. Foundation for create-entity/feature/widget/page. Use when placing new code into an FSD slice.

Scaffold an FSD widget slice — a large self-contained UI block composing features and entities. Assembles shadcn blocks via the shadcn MCP. Use after the composed features/entities exist.

Builds a complete React feature end-to-end from a request or an existing spec, following Feature-Sliced Design. Runs the full feature-dev-kit hub-and-spoke pipeline — scoped intake from spec-dev-kit plus an optional html prototype, codebase discovery, architecture-audit, bottom-up slice construction (shared → entities → features → widgets/pages → app), tests, quality gates, and auto-review — then stops at a mandatory human review gate. Never opens a pull request. Use when implementing any new feature, screen, or user interaction in a React + TypeScript codebase.

Turn a raw feature request or a scoped spec-dev-kit YAML slice into a structured, testable blackboard at intake with clarifying questions returned as a CLARIFY_PACKET. Produces .spec/features/<slug>.md per the feature-spec-format. Never AskUserQuestion, never self-finalizes blackboard status.

Given a capability need, resolve the library via context7, fetch version-accurate docs, and summarize integration approach + risks (bundle size, license, maintenance, alternatives). Emits a dependency proposal for human approval. NEVER runs yarn add.

Wrap typecheck → lint → FSD-boundary → conventions (missing tests, comments, hardcoded strings, unused exports, inline classes/handlers, JSX ternaries, magic props) → build → coverage into one structured pass/fail gate, returning only failures with remediation hints. Use between build stations to block progression.

Add sidebar menu, navigation, and breadcrumb entries in the app layer for an already-routed screen. Use with add-route so the screen appears in the nav UI. Not for scaffolding the page slice.