Skip to main content
ZICQ

Skills ZICQ category:Documents react

React

Build, review, debug, migrate, or plan React applications and components using current React documentation. Use for React, React DOM, hooks, JSX, Server Components, Server Functions, Actions/forms, React Compiler, hydration, rendering roots, React 19/19.3 upgrades, View Transitions, Fragment refs, browser-only rendering, Trusted Types, or questions about modern React patterns and best practices.

43 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Build, review, debug, migrate, or plan React applications and components using current React documentation. Use for React, React DOM, hooks, JSX, Server Components, Server Functions, Actions/forms, React Compiler, hydration, rendering roots, React 19/19.3 upgrades, View Transitions, Fragment refs, browser-only rendering, Trusted Types, or questions about modern React patterns and best practices.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: React; Workflow; React Judgment. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/source-map.md, references/core-react.md, references/react-19.md, references/react-dom.md. Those resources load on demand.

ReactWorkflowReact Judgment

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
react
description
Build, review, debug, migrate, or plan React applications and components using current React documentation. Use for React, React DOM, hooks, JSX, Server Components, Server Functions, Actions/forms, React Compiler, hydration, rendering roots, React 19/19.3 upgrades, View Transitions, Fragment refs, browser-only rendering, Trusted Types, or questions about modern React patterns and best practices.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 4
  • references/source-map.md
  • references/core-react.md
  • references/react-19.md
  • references/react-dom.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "react" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-67fbc1ca4d1bb3d7-React.html
Save it as .cursor/skills/react/SKILL.md or .claude/skills/react/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/dobroslavradosavljevic/skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/dobroslavradosavljevic/skills' --list

npx skills add 'https://github.com/dobroslavradosavljevic/skills' --skill 'react'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: react description: Build, review, debug, migrate, or plan React applications and components using current React documentation. Use for React, React DOM, hooks, JSX, Server Components, Server Functions, Actions/forms, React Compiler, hydration, rendering roots, React 19/19.3 upgrades, View Transitions, Fragment refs, browser-only rendering, Trusted Types, or questions about modern React patterns and best practices. --- # React Use this skill to make React choices from current docs plus the local app's actual version, framework, and conventions. Snapshot: `[email protected]` / `[email protected]` (2026-09-18). Refresh from [source-map.md](references/source-map.md) if versions differ. ## Workflow 1. Identify the React surface before changing code: - Read the nearest project guidance files and package manifests. - Check installed or declared versions of `react`, `react-dom`, the framework, build tool, test stack, TypeScript, and ESLint. - Determine whether the target is a client-only app, SSR, framework-managed app, React Server Components app, React Native app, component library, or migration. 2. Refresh docs when the user asks for latest/current behavior, when versions are unclear, or when using React 19+ APIs: - Prefer current docs tooling or official docs pages. - Use [source-map.md](references/source-map.md) for the captured latest-version snapshot and official source links. 3. Load the focused reference file for the task: - [core-react.md](references/core-react.md): component design, JSX, state, effects, hooks, purity, performance, and testing judgment. - [react-19.md](references/react-19.md): React 19–19.3 APIs, upgrades, Actions, forms, Server Components, Server Functions, Compiler, View Transitions, Fragment refs, and release-channel caveats. - [react-dom.md](references/react-dom.md): `createRoot`, `hydrateRoot`, `browser()`, DOM forms, hydration, server/static rendering, Trusted Types, resources, and escape hatches. 4. Implement in the existing project style: - Prefer framework primitives over direct React DOM APIs when the framework owns routing, data fetching, SSR, RSC, or hydration. - Preserve local component boundaries, accessibility conventions, tests, and styling patterns. - Avoid introducing React 19.3-only or canary-only APIs unless the app's dependencies support them. 5. Verify the smallest meaningful surface: - Run the project's relevant typecheck, lint, test, build, story, or browser verification command. - For visible UI changes, inspect the real screen state when feasible. - Report any verification you could not run. ## React Judgment - Keep render pure and idempotent. Do not read time, randomness, browser-only globals, or mutate non-local values during render unless the value is safely isolated and repeatable. - Derive values during render when they can be calculated from props or state. Do not add state plus an Effect just to mirror another value. - Use Effects only to synchronize with external systems such as the DOM, subscriptions, timers, imperative widgets, analytics, or non-framework data fetching. - Keep Effect dependencies honest. Prove a value is non-reactive by moving it out of the component or into an Effect/Event boundary instead of suppressing the linter. - Put user-caused side effects in event handlers or Actions. Put render-caused external synchronization in Effects. - Prefer local state. Lift state only when multiple components need to coordinate. Use reducers for complex transitions and `useSyncExternalStore` for external stores. - On React 19.3 SSR, prefer `use(browser())` from `react-dom` over `typeof window` or a mounted-state Effect for Client Components that cannot produce matching HTML. - Treat `` as a Transition/Suspense animation boundary. Do not call the browser `startViewTransition` API for React-managed updates. - Treat Server Components, Server Functions, and React DOM server/static APIs as framework integration territory unless the task is explicitly building framework infrastructure. - Treat canary and experimental docs as unavailable in stable apps unless the project explicitly uses those channels.

Related skills

Documents

Ontology

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, …

Documents

Nano Pdf

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Documents

Word / DOCX

Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and co…

Documents

Api Gateway

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when…