[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBVGD5BHDCHDGYAC95C2PM":3,"skill-same:01M7FBVGD5BHDCHDGYAC95C2PM":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7FBVGD5BHDCHDGYAC95C2PM","react-best-practices",null,"Modern React best practices and anti-pattern catalog (2025-26). Use when writing, reviewing, or refactoring React components, hooks, and state management. Covers component design, state patterns, hooks misuse, performance, data fetching, and code organization.","marynabieliaieva\u002Fdev-ai-harness-marketplace","marynabieliaieva","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7878548?v=4","01M7FBT0ZD7GRRYKNENTZ5EH2T","01M7FBT101PH91MN21MJ7XTKMY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Freact-best-practices\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: react-best-practices\ndescription: \"Modern React best practices and anti-pattern catalog (2025-26). Use when writing, reviewing, or refactoring React components, hooks, and state management. Covers component design, state patterns, hooks misuse, performance, data fetching, and code organization.\"\n---\n\n# React Best Practices & Anti-Patterns\n\nModern React conventions (2025-26). Covers what to do and what to avoid. For code examples, see [examples.md](examples.md).\n\n## Severity Levels\n\nEach rule is tagged with a severity for use by consuming agents:\n\n- **CRITICAL** — Will cause bugs, broken reconciliation, or maintenance nightmares\n- **HIGH** — Will cause performance issues or scaling problems\n- **MEDIUM** — Will hurt maintainability or developer experience\n\n---\n\n## Component Design (CRITICAL)\n\n- Components must be pure — same inputs = same outputs, no side effects during render\n- Business logic in hooks\u002Fhelpers, NOT in component bodies\n- Container components fetch data; presentational components receive props and render UI\n- Helper functions extracted OUTSIDE the component body\n- Max 200 lines per component — split if larger\n- Max 5-7 props — more suggests the component does too much\n- One component per file (small colocated internal helpers are fine)\n\n### Composition Patterns\n\n- Compose small focused components over monolithic ones\n- \"Lift Content Up\" — move children to the parent when the wrapper doesn't use them for logic\n- \"Push State Down\" — keep state in the component that actually needs it\n- Prefer `children` prop and composition over deep prop drilling\n\n## Derive, Don't Store (CRITICAL)\n\nThe #1 React anti-pattern. Look for it in every review.\n\n- NEVER store derived values in `useState` — compute during render\n- NEVER use `useState` + `useEffect` to sync a computed value — just compute it\n- Use `useMemo` ONLY if the computation is expensive (measured, not assumed)\n- If a value can be calculated from existing props\u002Fstate, calculate it inline\n\n## State Management (HIGH)\n\n### State Location\n- Colocate state with the components that use it\n- Don't lift state higher than necessary — it causes unnecessary re-renders\n- Don't duplicate state across components\n\n### Context API\n- Context is for dependency injection (auth, theme), NOT global state management\n- Context changes re-render ALL consumers — split contexts by concern\n- Prefer hook return values over Context when only one subtree needs the data\n\n### State Hygiene\n- Not everything needs to be in `useState` — only values that change over time and affect the UI\n- Combine related state with `useReducer` instead of multiple `useState` calls\n- URL-dependent state (filters, pagination, search) belongs in URL search params, not component state\n\n## Hooks (HIGH)\n\n### useEffect Rules\nBefore each `useEffect`, ask: **Is there an external system being synchronized?** If no, it's misused.\n\n- NEVER use `useEffect` for derived state — compute during render\n- NEVER use `useEffect` for event handling — put logic in the event handler\n- NEVER chain `useEffect`s that trigger each other — usually means derived state\n- ALWAYS declare all dependencies correctly\n- ALWAYS clean up subscriptions, timers, and event listeners\n\n### Memoization Rules\nMost `useMemo`\u002F`useCallback` calls are unnecessary. Be skeptical:\n\n- `useMemo` — only for actually expensive computations (sorting large datasets, complex transforms)\n- `useCallback` — only when the function is passed to a `React.memo` child\n- Simple string concatenation, arithmetic, or boolean checks do NOT need memoization\n\n## Render Factories (CRITICAL)\n\ncamelCase functions returning JSX are NOT React components. They break reconciliation, hooks, and dev tools.\n\n- NEVER use `renderThing()` pattern — use `\u003CThing \u002F>` component syntax\n- ALWAYS use PascalCase for anything that returns JSX\n- Render factories lose component identity on every render, causing full unmount\u002Fremount\n\n## Inline Creation in JSX (HIGH)\n\nNew arrays, objects, and functions created inline in JSX props break `React.memo` on children.\n\n- Extract static arrays\u002Fobjects to module-level constants\n- Extract dynamic arrays\u002Fobjects to `useMemo`\n- Extract inline functions to `useCallback` (only when passed to memoized children)\n\n## Over-Engineering (CRITICAL)\n\n### Premature Abstraction\n- Abstractions with only one consumer are premature — inline it\n- \"Reusable\" hooks with hardcoded field names are not reusable — accept config as parameters\n- Context storing state that could be computed locally is over-engineered\n\n### Wrapper Components\n- Components that only call a hook and return `null` are unnecessary — call the hook directly\n- Wrappers that only pass props through add indirection without value\n\n## Data Fetching (HIGH)\n\n- ALL data fetching in custom hooks, never in component bodies\n- Use the project's `useApiQuery`\u002F`useApiMutation` core hooks\n- Handle loading, error, and empty states in the container component\n- Use try-catch in async functions within hooks\n\n## Tailwind CSS (MEDIUM)\n\n- Use utility classes for all styling — no inline `style={}` objects\n- Use responsive prefixes (`sm:`, `md:`, `lg:`) for responsive design\n- Extract repeated class combinations into reusable components (Button, Card, Badge)\n- Prefer the project's `components\u002Fui\u002F` over recreating common elements\n\n## Error Boundaries (HIGH)\n\n- Use `react-error-boundary` package for function component-friendly API\n- Include `resetKeys={[location.pathname]}` so boundaries reset on navigation\n- Provide a \"Try again\" button that calls `resetErrorBoundary` in fallback UI\n- Error boundaries do NOT catch errors in event handlers, async code, or SSR — use try\u002Fcatch there\n\n## Key Prop Patterns (CRITICAL)\n\n- NEVER use array index as `key` when lists can be reordered, filtered, or modified\n- NEVER use `Math.random()` or other unstable values as keys — causes full unmount\u002Fremount\n- When mapping Fragments, put `key` on `\u003CReact.Fragment key={id}>`, not on a child\n\n## Conditional Rendering (HIGH)\n\n- NEVER use `{count && \u003CComponent \u002F>}` when `count` can be `0` — renders literal `0`\n- Use `{count > 0 && \u003CComponent \u002F>}` or ternary instead\n- Replace nested ternaries with early returns or extracted components\n- For multiple UI states (loading\u002Ferror\u002Fempty\u002Fsuccess), use early returns pattern\n\n## Accessibility (HIGH)\n\n- Add `aria-label` to icon-only buttons — without it, they're invisible to screen readers\n- Link error messages to fields with `aria-describedby` and `aria-invalid`\n- Use `aria-live=\"polite\"` for dynamic content updates (search results, notifications, toasts)\n- Trap focus inside modals; provide escape path (Escape key + visible Close button)\n- Announce route changes for screen readers (SPA navigation is silent by default)\n\n## Performance Beyond Memoization (MEDIUM)\n\n- Use `React.lazy()` + `\u003CSuspense>` for route-level code splitting\n- Use Vite `manualChunks` to split vendor bundles for better caching\n- Use top-level static paths in `lazy(() => import('.\u002FX'))` — dynamic paths break build analysis\n\n## Axios + React Patterns (HIGH)\n\n- Cancel in-flight requests in `useEffect` cleanup using `AbortController`\n- Use centralized Axios instance with `baseURL`, default headers, and interceptors\n- Use request interceptors for auth tokens, response interceptors for 401\u002F403 handling\n\n## React 19 Patterns (MEDIUM)\n\n- Accept `ref` as a regular prop instead of using `forwardRef` (React 19+)\n- With React Compiler enabled, avoid adding `memo`\u002F`useMemo`\u002F`useCallback` unless measured\n\n## Code Organization (MEDIUM)\n\n### Feature-Based Structure\n- Colocate component + hook + helpers + tests per feature\n- Shared utilities go in `utils\u002F` or `components\u002Fui\u002F`\n\n### File Quality\n- Order: imports, constants, helpers, component, exports\n- Reuse existing types and constants over creating new ones\n","# React Best Practices & Anti-Patterns\n\nModern React conventions (2025-26). Covers what to do and what to avoid. For code examples, see [examples.md](examples.md).\n\n## Severity Levels\n\nEach rule is tagged with a severity for use by consuming agents:\n\n- **CRITICAL** — Will cause bugs, broken reconciliation, or maintenance nightmares\n- **HIGH** — Will cause performance issues or scaling problems\n- **MEDIUM** — Will hurt maintainability or developer experience\n\n---\n\n## Component Design (CRITICAL)\n\n- Components must be pure — same inputs = same outputs, no side effects during render\n- Business logic in hooks\u002Fhelpers, NOT in component bodies\n- Container components fetch data; presentational components receive props and render UI\n- Helper functions extracted OUTSIDE the component body\n- Max 200 lines per component — split if larger\n- Max 5-7 props — more suggests the component does too much\n- One component per file (small colocated internal helpers are fine)\n\n### Composition Patterns\n\n- Compose small focused components over monolithic ones\n- \"Lift Content Up\" — move children to the parent when the wrapper doesn't use them for logic\n- \"Push State Down\" — keep state in the component that actually needs it\n- Prefer `children` prop and composition over deep prop drilling\n\n## Derive, Don't Store (CRITICAL)\n\nThe #1 React anti-pattern. Look for it in every review.\n\n- NEVER store derived values in `useState` — compute during render\n- NEVER use `useState` + `useEffect` to sync a computed value — just compute it\n- Use `useMemo` ONLY if the computation is expensive (measured, not assumed)\n- If a value can be calculated from existing props\u002Fstate, calculate it inline\n\n## State Management (HIGH)\n\n### State Location\n- Colocate state with the components that use it\n- Don't lift state higher than necessary — it causes unnecessary re-renders\n- Don't duplicate state across components\n\n### Context API\n- Context is for dependency injection (auth, theme), NOT global state management\n- Context changes re-render ALL consumers — split contexts by concern\n- Prefer hook return values over Context when only one subtree needs the data\n\n### State Hygiene\n- Not everything needs to be in `useState` — only values that change over time and affect the UI\n- Combine related state with `useReducer` instead of multiple `useState` calls\n- URL-dependent state (filters, pagination, search) belongs in URL search params, not component state\n\n## Hooks (HIGH)\n\n### useEffect Rules\nBefore each `useEffect`, ask: **Is there an external system being synchronized?** If no, it's misused.\n\n- NEVER use `useEffect` for derived state — compute during render\n- NEVER use `useEffect` for event handling — put logic in the event handler\n- NEVER chain `useEffect`s that trigger each other — usually means derived state\n- ALWAYS declare all dependencies correctly\n- ALWAYS clean up subscriptions, timers, and event listeners\n\n### Memoization Rules\nMost `useMemo`\u002F`useCallback` calls are unnecessary. Be skeptical:\n\n- `useMemo` — only for actually expensive computations (sorting large datasets, complex transforms)\n- `useCallback` — only when the function is passed to a `React.memo` child\n- Simple string concatenation, arithmetic, or boolean checks do NOT need memoization\n\n## Render Factories (CRITICAL)\n\ncamelCase functions returning JSX are NOT React components. They break reconciliation, hooks, and dev tools.\n\n- NEVER use `renderThing()` pattern — use `\u003CThing \u002F>` component syntax\n- ALWAYS use PascalCase for anything that returns JSX\n- Render factories lose component identity on every render, causing full unmount\u002Fremount\n\n## Inline Creation in JSX (HIGH)\n\nNew arrays, objects, and functions created inline in JSX props break `React.memo` on children.\n\n- Extract static arrays\u002Fobjects to module-level constants\n- Extract dynamic arrays\u002Fobjects to `useMemo`\n- Extract inline functions to `useCallback` (only when passed to memoized children)\n\n## Over-Engineering (CRITICAL)\n\n### Premature Abstraction\n- Abstractions with only one consumer are premature — inline it\n- \"Reusable\" hooks with hardcoded field names are not reusable — accept config as parameters\n- Context storing state that could be computed locally is over-engineered\n\n### Wrapper Components\n- Components that only call a hook and return `null` are unnecessary — call the hook directly\n- Wrappers that only pass props through add indirection without value\n\n## Data Fetching (HIGH)\n\n- ALL data fetching in custom hooks, never in component bodies\n- Use the project's `useApiQuery`\u002F`useApiMutation` core hooks\n- Handle loading, error, and empty states in the container component\n- Use try-catch in async functions within hooks\n\n## Tailwind CSS (MEDIUM)\n\n- Use utility classes for all styling — no inline `style={}` objects\n- Use responsive prefixes (`sm:`, `md:`, `lg:`) for responsive design\n- Extract repeated class combinations into reusable components (Button, Card, Badge)\n- Prefer the project's `components\u002Fui\u002F` over recreating common elements\n\n## Error Boundaries (HIGH)\n\n- Use `react-error-boundary` package for function component-friendly API\n- Include `resetKeys={[location.pathname]}` so boundaries reset on navigation\n- Provide a \"Try again\" button that calls `resetErrorBoundary` in fallback UI\n- Error boundaries do NOT catch errors in event handlers, async code, or SSR — use try\u002Fcatch there\n\n## Key Prop Patterns (CRITICAL)\n\n- NEVER use array index as `key` when lists can be reordered, filtered, or modified\n- NEVER use `Math.random()` or other unstable values as keys — causes full unmount\u002Fremount\n- When mapping Fragments, put `key` on `\u003CReact.Fragment key={id}>`, not on a child\n\n## Conditional Rendering (HIGH)\n\n- NEVER use `{count && \u003CComponent \u002F>}` when `count` can be `0` — renders literal `0`\n- Use `{count > 0 && \u003CComponent \u002F>}` or ternary instead\n- Replace nested ternaries with early returns or extracted components\n- For multiple UI states (loading\u002Ferror\u002Fempty\u002Fsuccess), use early returns pattern\n\n## Accessibility (HIGH)\n\n- Add `aria-label` to icon-only buttons — without it, they're invisible to screen readers\n- Link error messages to fields with `aria-describedby` and `aria-invalid`\n- Use `aria-live=\"polite\"` for dynamic content updates (search results, notifications, toasts)\n- Trap focus inside modals; provide escape path (Escape key + visible Close button)\n- Announce route changes for screen readers (SPA navigation is silent by default)\n\n## Performance Beyond Memoization (MEDIUM)\n\n- Use `React.lazy()` + `\u003CSuspense>` for route-level code splitting\n- Use Vite `manualChunks` to split vendor bundles for better caching\n- Use top-level static paths in `lazy(() => import('.\u002FX'))` — dynamic paths break build analysis\n\n## Axios + React Patterns (HIGH)\n\n- Cancel in-flight requests in `useEffect` cleanup using `AbortController`\n- Use centralized Axios instance with `baseURL`, default headers, and interceptors\n- Use request interceptors for auth tokens, response interceptors for 401\u002F403 handling\n\n## React 19 Patterns (MEDIUM)\n\n- Accept `ref` as a regular prop instead of using `forwardRef` (React 19+)\n- With React Compiler enabled, avoid adding `memo`\u002F`useMemo`\u002F`useCallback` unless measured\n\n## Code Organization (MEDIUM)\n\n### Feature-Based Structure\n- Colocate component + hook + helpers + tests per feature\n- Shared utilities go in `utils\u002F` or `components\u002Fui\u002F`\n\n### File Quality\n- Order: imports, constants, helpers, component, exports\n- Reuse existing types and constants over creating new ones\n",{"name":5,"description":7},"main","3bcf689e2951ea8cef76e93d0e9a96a8443cec13","plugins\u002Fengineering-paved-path\u002Fskills\u002Freact-best-practices","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva","2026-10-27 00:55:00",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add marynabieliaieva\u002Fdev-ai-harness-marketplace --skill react-best-practices",{"tool":35,"command":36},"bunx","bunx skills add marynabieliaieva\u002Fdev-ai-harness-marketplace --skill react-best-practices",{"tool":38,"command":39},"pnpm","pnpm dlx skills add marynabieliaieva\u002Fdev-ai-harness-marketplace --skill react-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Freact-best-practices\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"examples.md","REFERENCE","参考文档",8580,"https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Freact-best-practices\u002Fexamples.md",[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7FBX6FAH2MGVNNE4RGG2RPF","workflow-retro","Retrospective of a finished multi-agent workflow run (e.g. \u002Fsdd-engineering:run-plan, a code review, spec → plan → execution) — collects run facts (agents spawned, spawn order and waves, tokens per agent and per type, fix rounds, caps hit, human interventions), extracts insights per agent type (what was hard, what was easy, what information was duplicated, what each gate missed and who caught it later) and turns them into concrete, evidence-backed proposals for agent\u002Fskill\u002Fplan changes. Writes a ledger entry to docs\u002Fretro\u002Fledger\u002F and a summary in chat. Data source is the current conversation by default; --deep also parses the session transcripts on disk. Invoked only by the user as \u002Fsdd-engineering:workflow-retro — never automatically, never by another skill or agent.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdd-engineering\u002Fskills\u002Fworkflow-retro\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7FBX11WK2ZEC50W955GVJ87","run-plan","Runs the Spec Driven Development execution workflow for an already-written Implementation Plan (docs\u002Fplans\u002F\u003Cslug>.md) — implementer tasks wave by wave along the plan's DAG, one plan-verifier pass with a fix loop, an architecture-review loop (review → fix → re-review until clean or the round cap), then one full test run. Accepts the plan, optionally the spec, extra requirements text and design files. Does NOT run spec-creator or implementation-planner (those are run manually first). Invoked only by the user as \u002Fsdd-engineering:run-plan.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdd-engineering\u002Fskills\u002Frun-plan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7FBWWYCS5F001B95Z8YXX3Q","engineering-insights","Captures a non-obvious engineering insight (a working pattern, an antipattern\u002Fdead end, a decision with its reason, or a recurring error and fix) found while working in this repo, and files it into the INSIGHTS.md of the package the session touched. Use at the end of a session that learned something substantial, or immediately when something surprising comes up — skip when nothing non-obvious happened.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fsdd-engineering\u002Fskills\u002Fengineering-insights\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7FBWSMXJGXS3KSHKSVCZR8V","flaky-patterns","Reference catalogue of flaky-test causes — for each class, how it shows up in a stack trace, the real fix, the masking fixes to reject, and how to reproduce it deterministically without running the test many times. Use when diagnosing or reviewing a fix for a test that passes and fails on the same code.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fflaky-fix\u002Fskills\u002Fflaky-patterns\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7FBWKCDZNTQE9AW5PYA47KS","flaky-fix","Triage and fix one flaky test without extra pipeline or test runs — from the test name, a stack trace, the date it became flaky and its failure rate to a Jira issue, a fix branch, a reviewed commit and a PR, with verification left to the normal runs of main after merge. Invoked only by the user as \u002Fflaky-fix:flaky-fix.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fflaky-fix\u002Fskills\u002Fflaky-fix\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7FBWDF214X5KZ4YKD2XDJD8","zod","Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover form-library integration (e.g. React Hook Form resolvers) or OpenAPI client generation.","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fzod\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmarynabieliaieva\u002Fdev-ai-harness-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-paved-path\u002Fskills\u002Fzod\u002FSKILL.md",[],[]]