[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WYSFFFQKTKKJS7G6RDHC69":3,"skill-same:01M6WYSFFFQKTKKJS7G6RDHC69":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":6,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M6WYSFFFQKTKKJS7G6RDHC69","react-expert",null,"Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups. Creates components, implements custom hooks, debugs rendering issues, migrates class components to functional, and implements state management. Invoke for Server Components, Suspense boundaries, useActionState forms, performance optimization, or React 19 features.","PIXARTSeu\u002FSynapse","PIXARTSeu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274446381?v=4","01M6RB4XPN9YBZCRY4FVN9PJCT","Pixarts ","01M6RB4XTF8G9KHQEMC21FGDKD",12,"MIT","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Freact-expert\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"react","react expert","expert","files","invoke","Server Components","functional","react 19","rendering","app","tanstack query","frontend","tsx","router","zustand","projects","server","create","component","components","2026-11-10 10:12:30",false,"---\nname: react-expert\ndescription: Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups. Creates components, implements custom hooks, debugs rendering issues, migrates class components to functional, and implements state management. Invoke for Server Components, Suspense boundaries, useActionState forms, performance optimization, or React 19 features.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: frontend\n  triggers: React, JSX, hooks, useState, useEffect, useContext, Server Components, React 19, Suspense, TanStack Query, Redux, Zustand, component, frontend\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: fullstack-guardian, playwright-expert, test-master\n---\n\n# React Expert\n\nSenior React specialist with deep expertise in React 19, Server Components, and production-grade application architecture.\n\n## When to Use This Skill\n\n- Building new React components or features\n- Implementing state management (local, Context, Redux, Zustand)\n- Optimizing React performance\n- Setting up React project architecture\n- Working with React 19 Server Components\n- Implementing forms with React 19 actions\n- Data fetching patterns with TanStack Query or `use()`\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify component hierarchy, state needs, data flow\n2. **Choose patterns** - Select appropriate state management, data fetching approach\n3. **Implement** - Write TypeScript components with proper types\n4. **Validate** - Run `tsc --noEmit`; if it fails, review reported errors, fix all type issues, and re-run until clean before proceeding\n5. **Optimize** - Apply memoization where needed, ensure accessibility; if new type errors are introduced, return to step 4\n6. **Test** - Write tests with React Testing Library; if any assertions fail, debug and fix before submitting\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Server Components | `references\u002Fserver-components.md` | RSC patterns, Next.js App Router |\n| React 19 | `references\u002Freact-19-features.md` | use() hook, useActionState, forms |\n| State Management | `references\u002Fstate-management.md` | Context, Zustand, Redux, TanStack |\n| Hooks | `references\u002Fhooks-patterns.md` | Custom hooks, useEffect, useCallback |\n| Performance | `references\u002Fperformance.md` | memo, lazy, virtualization |\n| Testing | `references\u002Ftesting-react.md` | Testing Library, mocking |\n| Class Migration | `references\u002Fmigration-class-to-modern.md` | Converting class components to hooks\u002FRSC |\n\n## Key Patterns\n\n### Server Component (Next.js App Router)\n```tsx\n\u002F\u002F app\u002Fusers\u002Fpage.tsx — Server Component, no \"use client\"\nimport { db } from '@\u002Flib\u002Fdb';\n\ninterface User {\n  id: string;\n  name: string;\n}\n\nexport default async function UsersPage() {\n  const users: User[] = await db.user.findMany();\n\n  return (\n    \u003Cul>\n      {users.map((user) => (\n        \u003Cli key={user.id}>{user.name}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  );\n}\n```\n\n### React 19 Form with `useActionState`\n```tsx\n'use client';\nimport { useActionState } from 'react';\n\nasync function submitForm(_prev: string, formData: FormData): Promise\u003Cstring> {\n  const name = formData.get('name') as string;\n  \u002F\u002F perform server action or fetch\n  return `Hello, ${name}!`;\n}\n\nexport function GreetForm() {\n  const [message, action, isPending] = useActionState(submitForm, '');\n\n  return (\n    \u003Cform action={action}>\n      \u003Cinput name=\"name\" required \u002F>\n      \u003Cbutton type=\"submit\" disabled={isPending}>\n        {isPending ? 'Submitting…' : 'Submit'}\n      \u003C\u002Fbutton>\n      {message && \u003Cp>{message}\u003C\u002Fp>}\n    \u003C\u002Fform>\n  );\n}\n```\n\n### Custom Hook with Cleanup\n```tsx\nimport { useState, useEffect } from 'react';\n\nfunction useWindowWidth(): number {\n  const [width, setWidth] = useState(() => window.innerWidth);\n\n  useEffect(() => {\n    const handler = () => setWidth(window.innerWidth);\n    window.addEventListener('resize', handler);\n    return () => window.removeEventListener('resize', handler); \u002F\u002F cleanup\n  }, []);\n\n  return width;\n}\n```\n\n## Constraints\n\n### MUST DO\n- Use TypeScript with strict mode\n- Implement error boundaries for graceful failures\n- Use `key` props correctly (stable, unique identifiers)\n- Clean up effects (return cleanup function)\n- Use semantic HTML and ARIA for accessibility\n- Memoize when passing callbacks\u002Fobjects to memoized children\n- Use Suspense boundaries for async operations\n\n### MUST NOT DO\n- Mutate state directly\n- Use array index as key for dynamic lists\n- Create functions inside JSX (causes re-renders)\n- Forget useEffect cleanup (memory leaks)\n- Ignore React strict mode warnings\n- Skip error boundaries in production\n\n## Output Templates\n\nWhen implementing React features, provide:\n1. Component file with TypeScript types\n2. Test file if non-trivial logic\n3. Brief explanation of key decisions\n\n## Knowledge Reference\n\nReact 19, Server Components, use() hook, Suspense, TypeScript, TanStack Query, Zustand, Redux Toolkit, React Router, React Testing Library, Vitest\u002FJest, Next.js App Router, accessibility (WCAG)\n","# React Expert\n\nSenior React specialist with deep expertise in React 19, Server Components, and production-grade application architecture.\n\n## When to Use This Skill\n\n- Building new React components or features\n- Implementing state management (local, Context, Redux, Zustand)\n- Optimizing React performance\n- Setting up React project architecture\n- Working with React 19 Server Components\n- Implementing forms with React 19 actions\n- Data fetching patterns with TanStack Query or `use()`\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify component hierarchy, state needs, data flow\n2. **Choose patterns** - Select appropriate state management, data fetching approach\n3. **Implement** - Write TypeScript components with proper types\n4. **Validate** - Run `tsc --noEmit`; if it fails, review reported errors, fix all type issues, and re-run until clean before proceeding\n5. **Optimize** - Apply memoization where needed, ensure accessibility; if new type errors are introduced, return to step 4\n6. **Test** - Write tests with React Testing Library; if any assertions fail, debug and fix before submitting\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Server Components | `references\u002Fserver-components.md` | RSC patterns, Next.js App Router |\n| React 19 | `references\u002Freact-19-features.md` | use() hook, useActionState, forms |\n| State Management | `references\u002Fstate-management.md` | Context, Zustand, Redux, TanStack |\n| Hooks | `references\u002Fhooks-patterns.md` | Custom hooks, useEffect, useCallback |\n| Performance | `references\u002Fperformance.md` | memo, lazy, virtualization |\n| Testing | `references\u002Ftesting-react.md` | Testing Library, mocking |\n| Class Migration | `references\u002Fmigration-class-to-modern.md` | Converting class components to hooks\u002FRSC |\n\n## Key Patterns\n\n### Server Component (Next.js App Router)\n```tsx\n\u002F\u002F app\u002Fusers\u002Fpage.tsx — Server Component, no \"use client\"\nimport { db } from '@\u002Flib\u002Fdb';\n\ninterface User {\n  id: string;\n  name: string;\n}\n\nexport default async function UsersPage() {\n  const users: User[] = await db.user.findMany();\n\n  return (\n    \u003Cul>\n      {users.map((user) => (\n        \u003Cli key={user.id}>{user.name}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  );\n}\n```\n\n### React 19 Form with `useActionState`\n```tsx\n'use client';\nimport { useActionState } from 'react';\n\nasync function submitForm(_prev: string, formData: FormData): Promise\u003Cstring> {\n  const name = formData.get('name') as string;\n  \u002F\u002F perform server action or fetch\n  return `Hello, ${name}!`;\n}\n\nexport function GreetForm() {\n  const [message, action, isPending] = useActionState(submitForm, '');\n\n  return (\n    \u003Cform action={action}>\n      \u003Cinput name=\"name\" required \u002F>\n      \u003Cbutton type=\"submit\" disabled={isPending}>\n        {isPending ? 'Submitting…' : 'Submit'}\n      \u003C\u002Fbutton>\n      {message && \u003Cp>{message}\u003C\u002Fp>}\n    \u003C\u002Fform>\n  );\n}\n```\n\n### Custom Hook with Cleanup\n```tsx\nimport { useState, useEffect } from 'react';\n\nfunction useWindowWidth(): number {\n  const [width, setWidth] = useState(() => window.innerWidth);\n\n  useEffect(() => {\n    const handler = () => setWidth(window.innerWidth);\n    window.addEventListener('resize', handler);\n    return () => window.removeEventListener('resize', handler); \u002F\u002F cleanup\n  }, []);\n\n  return width;\n}\n```\n\n## Constraints\n\n### MUST DO\n- Use TypeScript with strict mode\n- Implement error boundaries for graceful failures\n- Use `key` props correctly (stable, unique identifiers)\n- Clean up effects (return cleanup function)\n- Use semantic HTML and ARIA for accessibility\n- Memoize when passing callbacks\u002Fobjects to memoized children\n- Use Suspense boundaries for async operations\n\n### MUST NOT DO\n- Mutate state directly\n- Use array index as key for dynamic lists\n- Create functions inside JSX (causes re-renders)\n- Forget useEffect cleanup (memory leaks)\n- Ignore React strict mode warnings\n- Skip error boundaries in production\n\n## Output Templates\n\nWhen implementing React features, provide:\n1. Component file with TypeScript types\n2. Test file if non-trivial logic\n3. Brief explanation of key decisions\n\n## Knowledge Reference\n\nReact 19, Server Components, use() hook, Suspense, TypeScript, TanStack Query, Zustand, Redux Toolkit, React Router, React Testing Library, Vitest\u002FJest, Next.js App Router, accessibility (WCAG)\n",{"name":5,"license":15,"metadata":60,"description":7},{"role":61,"scope":62,"author":63,"domain":46,"version":64,"triggers":65,"output-format":66,"related-skills":67},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","React, JSX, hooks, useState, useEffect, useContext, Server Components, React 19, Suspense, TanStack Query, Redux, Zustand, component, frontend","code","fullstack-guardian, playwright-expert, test-master","main","c19c0bc0a04d25a849ce749fe88250e688f06437","packages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Freact-expert",1,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse","https:\u002F\u002Fgithub.com\u002FPIXARTSeu","https:\u002F\u002Fpixarts.eu\u002F","2026-09-24 06:30:45",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add PIXARTSeu\u002FSynapse --skill react-expert",{"tool":82,"command":83},"bunx","bunx skills add PIXARTSeu\u002FSynapse --skill react-expert",{"tool":85,"command":86},"pnpm","pnpm dlx skills add PIXARTSeu\u002FSynapse --skill react-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Freact-expert\u002FSKILL.md",true,[],[91,117,124,150,173,197],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":99,"publishedAt":55},"01M6X0ECZKGP44NP2JW588B9RG","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[97,98],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[35,100,101,102,103,104,105,54,106,107,108,66,109,110,111,112,113,114,115,116],"vercel react best practices","best practices","react best practices","vercel","writing","performance","react components","guidelines","tasks","Optimization","data","refactoring","patterns","next","triggers","data fetching","when",{"skillNo":118,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":123,"publishedAt":55},"01M6X05WCVH879XKZEAQ15PHQX","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Fskill\u002Fvercel-react-best-practices\u002FSKILL.md",[121,122],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[35,100,101,102,103,104,105,54,106,107,108,66,109,110,111,112,113,114,115,116],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":134,"publishedAt":55},"01M6WZ286AR2SYE9GZYVW0CNYG","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwordpress-pro\u002FSKILL.md",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[135,136,137,104,138,105,66,139,140,141,142,143,144,37,145,146,147,148,149,116],"wordpress","wordpress pro","pro","security","tuning","api","laravel","reviewer","hooks","filters","query","woocommerce","caching","themes","sanitization",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":158,"publishedAt":55},"01M6WZ1ZVG6PJ4PVN9RTK0BX7Z","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwebsocket-engineer\u002FSKILL.md",[156,157],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[159,160,161,162,66,163,164,140,142,165,37,166,167,168,169,170,171,172,39,116],"websocket","engineer","websocket engineer","architecture","messaging","monitoring","fastapi","time","scaling","io","communication systems","presence","updates","socket",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":55},"01M6WZ1G86ZR73H0WNM6CGNRGF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert\u002FSKILL.md",[179,180,181],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[183,37,184,46,104,185,54,186,187,188,50,189,190,48,191,192,193,194,195,196],"vue","vue expert","typescript","config","applications","Composition","pinia","use","workers","mobile","reusable","worker","apps","hybrid",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":205,"publishedAt":55},"01M6WZ1AP3GFCBAMD712X8KRP7","vue-expert-js","Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",[203,204],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[183,206,37,207,184,46,185,54,66,140,188,50,208,209,210,211,212,213,214,116],"js","vue expert js","coverage","only","up","modules","options","jsdoc","quick"]