vadimgaidai
UserReact Feature Kit — plan a feature into one file, build it in one pass, review the diff, with React 19, shadcn/ui and Feature-Sliced Design conventions
Categories
Indexed Skills (9)
structure
Feature-Sliced Design rules — layers, import direction, module anatomy, the model split, and a deterministic module scaffolder. Use when creating a module, deciding which layer code belongs to, or resolving an import-boundary question.
analyze
Plans a unit of work. Interactive Q&A in the main session (one question per turn, recommended answer first), then writes ONE `.planning/[name]/PLAN.md` covering every module of the request. Use when the user wants to plan, spec, scope or start a feature, module or refactor. Never delegate to a subagent — AskUserQuestion does not surface from one.
implement
Implements a planned unit of work end-to-end in one pass — types, data layer, schemas, UI, wiring — from `.planning/[name]/PLAN.md`. Use when the user wants to build, implement, or execute a plan, feature, module or issue. Runs in the main session; do not fan out to subagents.
review
Reviews the current diff against the plan's acceptance criteria, the API contract and the project's conventions. Takes an optional focus argument (`correctness`, `contract`, `consistency`, `perf`, comma-separated) to narrow the report. Reports findings; applies fixes only when asked. Use before opening a PR or merging, or when the user asks to review changes.
react-hook-form-zod
Repo-specific React Hook Form + Zod patterns — schema in model/schemas.ts, zodResolver, Field/FieldGroup layout, z.input === z.output rule. Use when building or fixing forms, validation schemas, resolver type errors, or multi-step/field-array forms.
react
React 19 and React Compiler rules — where state belongs, when memoization is warranted, what effects are actually for, refs and context, error boundaries, and how to split code with lazy + Suspense. Use when writing or reviewing React components, adding a route/modal/heavy widget, chasing a re-render problem, or reaching for useEffect/useMemo/useCallback/useRef/useContext.
shadcn-ui
shadcn/ui + Tailwind conventions — semantic tokens instead of raw colors, extending primitives via ComponentProps, compound components, icon and spacing rules that survive dark mode. Use when building or fixing UI on shadcn/Tailwind, wrapping a primitive, or deciding how to style a component.
tanstack-query
TanStack Query v5 policy for a client-rendered SPA — what the shared QueryClient already decides, what belongs in a query key, when to use enabled/select/useQueries/placeholderData, and how a mutation touches the cache. Use when writing or reviewing queries, mutations, cache invalidation, pagination, prefetching, or a data-fetching effect.
api-contract
Slices an OpenAPI/Swagger contract down to the endpoints one feature needs, with $refs inlined and required/optional/enums explicit, so request and response shapes are never guessed. Use when starting work against a backend contract, when types drift from the API, or when the user gives a Swagger/OpenAPI URL.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.