Skip to content
Skills Library
Programming · Building & coding

react-typescript

/react-typescript

Use when modifying a frontend that actually uses React and TypeScript, including components, hooks, routing, state, forms, and client-side tests.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when modifying a frontend that actually uses React and TypeScript, including components, hooks, routing, state, forms, and client-side tests.

Original author description

Use when modifying a frontend that actually uses React and TypeScript, including components, hooks, routing, state, forms, and client-side tests.

How it works

  1. Supported scope
  2. When to load
  3. Before implementation
  4. Implementation standards
  5. Testing and verification
  6. Completion checklist
  7. References
Original SKILL.md headings · 47 lines, 415 words
SKILL.md preview
---
name: react-typescript
description: Use when modifying a frontend that actually uses React and TypeScript, including components, hooks, routing, state, forms, and client-side tests.
---

# React and TypeScript Skill — Starter Guidance

## Supported scope

- Technology and version range: React 18/19+ with TypeScript 5+ (inspect `package.json` and `tsconfig.json` for exact versions, strictness flags, and bundler/framework setup).
- Last reviewed: 2026-11
- Runtime/build tooling: Vite, Next.js, Remix/React Router, or custom Webpack/Rspack toolchains via `npm`, `pnpm`, `yarn`, or `bun`.
- Framework modules covered: components, hooks, client/server state management, forms, routing, accessibility semantics, and client/component testing.
- Out-of-scope / unsupported versions: Legacy class-component-only React (< 16.8), non-React frontend frameworks (Vue, Angular, Svelte), and backend-only Node.js services.

## When to load

Load when modifying a frontend application or UI library that uses React and TypeScript, including components, hooks, routing, state, forms, styling, and client-side tests. Do not load for backend-only or infrastructure tasks.

## Before implementation

- Detect React, TypeScript, router, bundler, state/data-fetching library (TanStack Query, Redux Toolkit, Zustand, SWR), form library, styling system, and test runner from `package.json` and lockfiles.
- Inspect existing component organization, design-system primitives, error boundaries, and accessibility conventions before creating new components.
- Check `package.json` scripts (`typecheck`, `lint`, `test`, `build`) before running verification commands.

## Implementation standards

- Keep components focused on a clear responsibility; compute derived values during render rather than synchronizing duplicate state in `useEffect`.
- Model asynchronous and UI flows with strict TypeScript types and discriminated unions; avoid `any`, unsafe `as` casts, and non-null assertions (`!`) on untrusted data.
- Handle complete user-facing states where relevant: initial loading, empty data, validation errors, server/network failure, unauthorized state, retry, and in-flight submission disabling.
- Use semantic HTML elements (`<button>`, `<form>`, `<label>`, `<dialog>`, `<nav>`, landmarks), explicit accessible names, keyboard navigation, and visible focus management.
- Prevent XSS by avoiding `dangerouslySetInnerHTML` with unsanitized content; never embed secrets in client bundles or treat client-side checks as authoritative authorization.

## Testing and verification

- Test user-visible behavior and accessibility roles (`getByRole`, `getByLabelText`, `userEvent`) using the repository's configured runner (Vitest, Jest, React Testing Library, Playwright) rather than asserting internal hook or state implementation details.
- Verify keyboard submission, validation error messages, loading/error states, and TypeScript compilation (`tsc --noEmit` or project `typecheck` script).

## Completion checklist

- [ ] Implementation follows the installed React/TypeScript versions and existing project conventions.
- [ ] Typecheck, lint, and component/E2E tests executed and passing.
- [ ] Semantic markup, keyboard interaction, and UI error/loading states verified.
- [ ] No unapproved UI/state dependencies or client-side secret exposures introduced.

## References

- React official documentation: https://react.dev/reference/react
- TypeScript handbook: https://www.typescriptlang.org/docs/
- WAI-ARIA Authoring Practices Guide (APG): https://www.w3.org/WAI/ARIA/apg/

Versions

RepositoryScoreLicence
This page · yvssdheeraj/opencode-engineering-harness90MIT
HoangNguyen0403/agent-skills-standard100MIT
sudeeppatgar/fullstack-skills100MIT

Database snapshot: 13.11.2026 · package version e0421a0898e8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100react-frontend
    React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
  • 100react-frontend-patterns
    React 19+, TypeScript, Tailwind CSS, shadcn/ui component patterns, accessibility, forms, state management. Use when building or reviewing React components, pages, or frontend architecture.
  • 100frontend-module-standards
    Enforce this repository's React and TypeScript frontend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing frontend code under `src/`, including feature modules, components, hooks, contexts, shared UI, API access, state, utilities, and…
  • 100frontend-typescript-rules
    Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
  • 96react-dev
    This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing…
  • 90frontend-engineering
    Build, refactor, or review accessible, responsive web frontends using React, TypeScript, and other modern frameworks. Use for UI architecture, component design, routing, forms, state, API integration, browser behavior, performance, and visual quality.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.