React TypeScript: type-safe patterns for React 18-19 (hooks, Server Components, routing)
Type-safe React patterns: typed hooks, ref-as-prop, Server Components, Server Actions, TanStack Router and React Router v7
- What
- Type-safe React patterns: typed hooks, ref-as-prop, Server Components, Server Actions, TanStack Router and React Router v7
- Cost
- Free
- Needs
- nothing to install — the skill is a reference your agent follows when writing React + TypeScript; works best with React 18-19 projects
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @softaworks' deep reference skill for type-safe React with TypeScript, covering React 18–19: typed component and event-handler patterns (specific event types, discriminated unions for variant props, ComponentPropsWithoutRef), hook typing (explicit useState unions, useRef null-vs-mutable, custom-hook tuple returns with `as const`, useContext null guards), generic components with type inference, and the React 19 changes (ref as a regular prop instead of forwardRef, useActionState replacing useFormState, the `use()` promise-unwrapping API) — plus async Server Components, Server Actions, and type-safe routing with TanStack Router (Zod-validated search params) and React Router v7 (framework-mode type generation). Every section states ALWAYS/NEVER rules and points to dedicated reference files. Honest caveats: React-only — nothing for Vue, Svelte or vanilla TS; the bundled reference files are part of the skill, so the agent should fetch the whole skill directory, not just SKILL.md. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is a reference your agent follows when writing React + TypeScript; works best with React 18-19 projects Install "React TypeScript: type-safe patterns for React 18-19 (hooks, Server Components, routing)" for me. It gives my agent @softaworks' type-safe React patterns: typed components and event handlers, hook typing (useState, useRef, useReducer, useContext, custom hooks), generic components with inference, React 19 migration patterns (ref as prop, useActionState, use()), async Server Components and Server Actions, and type-safe routing with TanStack Router and React Router v7 — each with ALWAYS/NEVER rules and reference files. MIT-licensed. Repository: https://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/react-dev/skills/react-dev/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "react-dev". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — invoke it when writing or reviewing React + TypeScript code). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.