[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBT45ABTZGGY3Z79883MEG":3,"skill-same:01M7FBT45ABTZGGY3Z79883MEG":46},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FBT45ABTZGGY3Z79883MEG","react",null,"React renderer for json-render that turns JSON specs into React components. Use when working with @json-render\u002Freact, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Freact\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: react\ndescription: React renderer for json-render that turns JSON specs into React components. Use when working with @json-render\u002Freact, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.\n---\n\n# @json-render\u002Freact\n\nReact renderer that converts JSON specs into React component trees.\n\n## Quick Start\n\n```typescript\nimport { defineRegistry, Renderer } from \"@json-render\u002Freact\";\nimport { catalog } from \".\u002Fcatalog\";\n\nconst { registry } = defineRegistry(catalog, {\n  components: {\n    Card: ({ props, children }) => \u003Cdiv>{props.title}{children}\u003C\u002Fdiv>,\n  },\n});\n\nfunction App({ spec }) {\n  return \u003CRenderer spec={spec} registry={registry} \u002F>;\n}\n```\n\n## Creating a Catalog\n\n```typescript\nimport { defineCatalog } from \"@json-render\u002Fcore\";\nimport { schema } from \"@json-render\u002Freact\u002Fschema\";\nimport { defineRegistry } from \"@json-render\u002Freact\";\nimport { z } from \"zod\";\n\n\u002F\u002F Create catalog with props schemas\nexport const catalog = defineCatalog(schema, {\n  components: {\n    Button: {\n      props: z.object({\n        label: z.string(),\n        variant: z.enum([\"primary\", \"secondary\"]).nullable(),\n      }),\n      description: \"Clickable button\",\n    },\n    Card: {\n      props: z.object({ title: z.string() }),\n      slots: [\"default\"],\n      description: \"Card container with title\",\n    },\n    Layout: {\n      props: z.object({}),\n      slots: [\"default\", \"header\", \"footer\"],\n      description: \"Layout with named content regions\",\n    },\n  },\n});\n\n\u002F\u002F Define component implementations with type-safe props\nconst { registry } = defineRegistry(catalog, {\n  components: {\n    Button: ({ props }) => (\n      \u003Cbutton className={props.variant}>{props.label}\u003C\u002Fbutton>\n    ),\n    Card: ({ props, children }) => (\n      \u003Cdiv className=\"card\">\n        \u003Ch2>{props.title}\u003C\u002Fh2>\n        {children}\n      \u003C\u002Fdiv>\n    ),\n    Layout: ({ children, slots }) => (\n      \u003Cdiv>\n        \u003Cheader>{slots?.header}\u003C\u002Fheader>\n        \u003Cmain>{children}\u003C\u002Fmain>\n        \u003Cfooter>{slots?.footer}\u003C\u002Ffooter>\n      \u003C\u002Fdiv>\n    ),\n  },\n});\n```\n\n## Spec Structure (Element Tree)\n\nThe React schema uses an element tree format:\n\n```json\n{\n  \"root\": {\n    \"type\": \"Card\",\n    \"props\": { \"title\": \"Hello\" },\n    \"children\": [{ \"type\": \"Button\", \"props\": { \"label\": \"Click me\" } }]\n  }\n}\n```\n\n## Named Slots\n\nUse `children` for the `\"default\"` slot. Use the element's top-level `slots` object for other slot names declared by the catalog:\n\n```json\n{\n  \"type\": \"Layout\",\n  \"props\": {},\n  \"children\": [\"main\"],\n  \"slots\": {\n    \"header\": [\"heading\"],\n    \"footer\": [\"actions\"]\n  }\n}\n```\n\nRegistry components receive named content as `slots?.header`, `slots?.footer`, and so on. Do not use `slots.default`.\n\n## Visibility Conditions\n\nUse `visible` on elements to show\u002Fhide based on state. New syntax: `{ \"$state\": \"\u002Fpath\" }`, `{ \"$state\": \"\u002Fpath\", \"eq\": value }`, `{ \"$state\": \"\u002Fpath\", \"not\": true }`, `{ \"$and\": [cond1, cond2] }` for AND, `{ \"$or\": [cond1, cond2] }` for OR. Helpers: `visibility.when(\"\u002Fpath\")`, `visibility.unless(\"\u002Fpath\")`, `visibility.eq(\"\u002Fpath\", val)`, `visibility.and(cond1, cond2)`, `visibility.or(cond1, cond2)`.\n\n## Providers\n\n| Provider             | Purpose                                                                                                |\n| -------------------- | ------------------------------------------------------------------------------------------------------ |\n| `StateProvider`      | Share state across components (JSON Pointer paths). Accepts optional `store` prop for controlled mode. |\n| `ActionProvider`     | Handle actions dispatched via the event system                                                         |\n| `VisibilityProvider` | Enable conditional rendering based on state                                                            |\n| `ValidationProvider` | Form field validation                                                                                  |\n\n### External Store (Controlled Mode)\n\nPass a `StateStore` to `StateProvider` (or `JSONUIProvider` \u002F `createRenderer`) to use external state management (Redux, Zustand, XState, etc.):\n\n```tsx\nimport { createStateStore, type StateStore } from \"@json-render\u002Freact\";\n\nconst store = createStateStore({ count: 0 });\n\n\u003CStateProvider store={store}>{children}\u003C\u002FStateProvider>;\n\n\u002F\u002F Mutate from anywhere — React re-renders automatically:\nstore.set(\"\u002Fcount\", 1);\n```\n\nWhen `store` is provided, `initialState` and `onStateChange` are ignored.\n\n## Dynamic Prop Expressions\n\nAny prop value can be a data-driven expression resolved by the renderer before components receive props:\n\n- **`{ \"$state\": \"\u002Fstate\u002Fkey\" }`** - reads from state model (one-way read)\n- **`{ \"$bindState\": \"\u002Fpath\" }`** - two-way binding: reads from state and enables write-back. Use on the natural value prop (value, checked, pressed, etc.) of form components.\n- **`{ \"$bindItem\": \"field\" }`** - two-way binding to a repeat item field. Use inside repeat scopes.\n- **Filtered lists**: `repeat` plus an `$item` visible condition on the same container renders only matching items: `{ \"repeat\": { \"statePath\": \"\u002Ftasks\", \"key\": \"id\" }, \"visible\": { \"$item\": \"status\", \"eq\": \"todo\" }, \"children\": [\"task-card\"] }`. AND-composed `$state` conjuncts gate the container shell; `$item`\u002F`$index` conjuncts filter items.\n- **Nested lists**: inside a repeat, use `{ \"repeat\": { \"statePath\": { \"$item\": \"comments\" }, \"key\": \"id\" } }` to iterate an array on the enclosing item.\n- **`{ \"$cond\": \u003Ccondition>, \"$then\": \u003Cvalue>, \"$else\": \u003Cvalue> }`** - conditional value\n- **`{ \"$template\": \"Hello, ${\u002Fname}!\" }`** - interpolates state values into strings\n- **`{ \"$computed\": \"fn\", \"args\": { ... } }`** - calls registered functions with resolved args\n\n```json\n{\n  \"type\": \"Input\",\n  \"props\": {\n    \"value\": { \"$bindState\": \"\u002Fform\u002Femail\" },\n    \"placeholder\": \"Email\"\n  }\n}\n```\n\nComponents do not use a `statePath` prop for two-way binding. Use `{ \"$bindState\": \"\u002Fpath\" }` on the natural value prop instead.\n\nComponents receive already-resolved props. For two-way bound props, use the `useBoundProp` hook with the `bindings` map the renderer provides.\n\nRegister `$computed` functions via the `functions` prop on `JSONUIProvider` or `createRenderer`:\n\n```tsx\n\u003CJSONUIProvider\n  functions={{ fullName: (args) => `${args.first} ${args.last}` }}\n>\n```\n\n## Event System\n\nComponents use `emit` to fire named events, or `on()` to get an event handle with metadata. The element's `on` field maps events to action bindings:\n\n```tsx\n\u002F\u002F Simple event firing\nButton: ({ props, emit }) => (\n  \u003Cbutton onClick={() => emit(\"press\")}>{props.label}\u003C\u002Fbutton>\n),\n\n\u002F\u002F Event handle with metadata (e.g. preventDefault)\nLink: ({ props, on }) => {\n  const click = on(\"click\");\n  return (\n    \u003Ca href={props.href} onClick={(e) => {\n      if (click.shouldPreventDefault) e.preventDefault();\n      click.emit();\n    }}>{props.label}\u003C\u002Fa>\n  );\n},\n```\n\n```json\n{\n  \"type\": \"Button\",\n  \"props\": { \"label\": \"Submit\" },\n  \"on\": { \"press\": { \"action\": \"submit\" } }\n}\n```\n\nThe `EventHandle` returned by `on()` has: `emit()`, `shouldPreventDefault` (boolean), and `bound` (boolean).\n\n## State Watchers\n\nElements can declare a `watch` field (top-level, sibling of type\u002Fprops\u002Fchildren) to trigger actions when state values change:\n\n```json\n{\n  \"type\": \"Select\",\n  \"props\": {\n    \"value\": { \"$bindState\": \"\u002Fform\u002Fcountry\" },\n    \"options\": [\"US\", \"Canada\"]\n  },\n  \"watch\": { \"\u002Fform\u002Fcountry\": { \"action\": \"loadCities\" } },\n  \"children\": []\n}\n```\n\n## Built-in Actions\n\nThe `setState`, `pushState`, `removeState`, and `validateForm` actions are built into the React schema and handled automatically by `ActionProvider`. They are injected into AI prompts without needing to be declared in catalog `actions`:\n\n```json\n{ \"action\": \"setState\", \"params\": { \"statePath\": \"\u002FactiveTab\", \"value\": \"home\" } }\n{ \"action\": \"pushState\", \"params\": { \"statePath\": \"\u002Fitems\", \"value\": { \"text\": \"New\" } } }\n{ \"action\": \"removeState\", \"params\": { \"statePath\": \"\u002Fitems\", \"index\": 0 } }\n{ \"action\": \"validateForm\", \"params\": { \"statePath\": \"\u002FformResult\" } }\n```\n\n`validateForm` validates all registered fields and writes `{ valid, errors }` to state.\n\nNote: `statePath` in action params (e.g. `setState.statePath`) targets the mutation path. Two-way binding in component props uses `{ \"$bindState\": \"\u002Fpath\" }` on the value prop, not `statePath`.\n\n## useBoundProp\n\nFor form components that need two-way binding, use `useBoundProp` with the `bindings` map the renderer provides when a prop uses `{ \"$bindState\": \"\u002Fpath\" }` or `{ \"$bindItem\": \"field\" }`:\n\n```tsx\nimport { useBoundProp } from \"@json-render\u002Freact\";\n\nInput: ({ element, bindings }) => {\n  const [value, setValue] = useBoundProp\u003Cstring>(\n    element.props.value,\n    bindings?.value\n  );\n  return (\n    \u003Cinput\n      value={value ?? \"\"}\n      onChange={(e) => setValue(e.target.value)}\n    \u002F>\n  );\n},\n```\n\n`useBoundProp(propValue, bindingPath)` returns `[value, setValue]`. The `value` is the resolved prop; `setValue` writes back to the bound state path (no-op if not bound).\n\n## BaseComponentProps\n\nFor building reusable component libraries not tied to a specific catalog (e.g. `@json-render\u002Fshadcn`):\n\n```typescript\nimport type { BaseComponentProps } from \"@json-render\u002Freact\";\n\nconst Card = ({ props, children }: BaseComponentProps\u003C{ title?: string }>) => (\n  \u003Cdiv>{props.title}{children}\u003C\u002Fdiv>\n);\n```\n\n## defineRegistry\n\n`defineRegistry` conditionally requires the `actions` field only when the catalog declares actions. Catalogs with `actions: {}` can omit it.\n\n## Key Exports\n\n| Export                  | Purpose                                                                                               |\n| ----------------------- | ----------------------------------------------------------------------------------------------------- |\n| `defineRegistry`        | Create a type-safe component registry from a catalog                                                  |\n| `Renderer`              | Render a spec using a registry                                                                        |\n| `schema`                | Element tree schema (includes built-in state actions: setState, pushState, removeState, validateForm) |\n| `useStateStore`         | Access state context                                                                                  |\n| `useStateValue`         | Get single value from state                                                                           |\n| `useBoundProp`          | Two-way binding for `$bindState`\u002F`$bindItem` expressions                                              |\n| `useActions`            | Access actions context                                                                                |\n| `useAction`             | Get a single action dispatch function                                                                 |\n| `useOptionalValidation` | Non-throwing variant of useValidation (returns null if no provider)                                   |\n| `useUIStream`           | Stream specs from an API endpoint                                                                     |\n| `createStateStore`      | Create a framework-agnostic in-memory `StateStore`                                                    |\n| `StateStore`            | Interface for plugging in external state management                                                   |\n| `BaseComponentProps`    | Catalog-agnostic base type for reusable component libraries                                           |\n| `EventHandle`           | Event handle type (`emit`, `shouldPreventDefault`, `bound`)                                           |\n| `ComponentContext`      | Typed component context (catalog-aware)                                                               |\n","# @json-render\u002Freact\n\nReact renderer that converts JSON specs into React component trees.\n\n## Quick Start\n\n```typescript\nimport { defineRegistry, Renderer } from \"@json-render\u002Freact\";\nimport { catalog } from \".\u002Fcatalog\";\n\nconst { registry } = defineRegistry(catalog, {\n  components: {\n    Card: ({ props, children }) => \u003Cdiv>{props.title}{children}\u003C\u002Fdiv>,\n  },\n});\n\nfunction App({ spec }) {\n  return \u003CRenderer spec={spec} registry={registry} \u002F>;\n}\n```\n\n## Creating a Catalog\n\n```typescript\nimport { defineCatalog } from \"@json-render\u002Fcore\";\nimport { schema } from \"@json-render\u002Freact\u002Fschema\";\nimport { defineRegistry } from \"@json-render\u002Freact\";\nimport { z } from \"zod\";\n\n\u002F\u002F Create catalog with props schemas\nexport const catalog = defineCatalog(schema, {\n  components: {\n    Button: {\n      props: z.object({\n        label: z.string(),\n        variant: z.enum([\"primary\", \"secondary\"]).nullable(),\n      }),\n      description: \"Clickable button\",\n    },\n    Card: {\n      props: z.object({ title: z.string() }),\n      slots: [\"default\"],\n      description: \"Card container with title\",\n    },\n    Layout: {\n      props: z.object({}),\n      slots: [\"default\", \"header\", \"footer\"],\n      description: \"Layout with named content regions\",\n    },\n  },\n});\n\n\u002F\u002F Define component implementations with type-safe props\nconst { registry } = defineRegistry(catalog, {\n  components: {\n    Button: ({ props }) => (\n      \u003Cbutton className={props.variant}>{props.label}\u003C\u002Fbutton>\n    ),\n    Card: ({ props, children }) => (\n      \u003Cdiv className=\"card\">\n        \u003Ch2>{props.title}\u003C\u002Fh2>\n        {children}\n      \u003C\u002Fdiv>\n    ),\n    Layout: ({ children, slots }) => (\n      \u003Cdiv>\n        \u003Cheader>{slots?.header}\u003C\u002Fheader>\n        \u003Cmain>{children}\u003C\u002Fmain>\n        \u003Cfooter>{slots?.footer}\u003C\u002Ffooter>\n      \u003C\u002Fdiv>\n    ),\n  },\n});\n```\n\n## Spec Structure (Element Tree)\n\nThe React schema uses an element tree format:\n\n```json\n{\n  \"root\": {\n    \"type\": \"Card\",\n    \"props\": { \"title\": \"Hello\" },\n    \"children\": [{ \"type\": \"Button\", \"props\": { \"label\": \"Click me\" } }]\n  }\n}\n```\n\n## Named Slots\n\nUse `children` for the `\"default\"` slot. Use the element's top-level `slots` object for other slot names declared by the catalog:\n\n```json\n{\n  \"type\": \"Layout\",\n  \"props\": {},\n  \"children\": [\"main\"],\n  \"slots\": {\n    \"header\": [\"heading\"],\n    \"footer\": [\"actions\"]\n  }\n}\n```\n\nRegistry components receive named content as `slots?.header`, `slots?.footer`, and so on. Do not use `slots.default`.\n\n## Visibility Conditions\n\nUse `visible` on elements to show\u002Fhide based on state. New syntax: `{ \"$state\": \"\u002Fpath\" }`, `{ \"$state\": \"\u002Fpath\", \"eq\": value }`, `{ \"$state\": \"\u002Fpath\", \"not\": true }`, `{ \"$and\": [cond1, cond2] }` for AND, `{ \"$or\": [cond1, cond2] }` for OR. Helpers: `visibility.when(\"\u002Fpath\")`, `visibility.unless(\"\u002Fpath\")`, `visibility.eq(\"\u002Fpath\", val)`, `visibility.and(cond1, cond2)`, `visibility.or(cond1, cond2)`.\n\n## Providers\n\n| Provider             | Purpose                                                                                                |\n| -------------------- | ------------------------------------------------------------------------------------------------------ |\n| `StateProvider`      | Share state across components (JSON Pointer paths). Accepts optional `store` prop for controlled mode. |\n| `ActionProvider`     | Handle actions dispatched via the event system                                                         |\n| `VisibilityProvider` | Enable conditional rendering based on state                                                            |\n| `ValidationProvider` | Form field validation                                                                                  |\n\n### External Store (Controlled Mode)\n\nPass a `StateStore` to `StateProvider` (or `JSONUIProvider` \u002F `createRenderer`) to use external state management (Redux, Zustand, XState, etc.):\n\n```tsx\nimport { createStateStore, type StateStore } from \"@json-render\u002Freact\";\n\nconst store = createStateStore({ count: 0 });\n\n\u003CStateProvider store={store}>{children}\u003C\u002FStateProvider>;\n\n\u002F\u002F Mutate from anywhere — React re-renders automatically:\nstore.set(\"\u002Fcount\", 1);\n```\n\nWhen `store` is provided, `initialState` and `onStateChange` are ignored.\n\n## Dynamic Prop Expressions\n\nAny prop value can be a data-driven expression resolved by the renderer before components receive props:\n\n- **`{ \"$state\": \"\u002Fstate\u002Fkey\" }`** - reads from state model (one-way read)\n- **`{ \"$bindState\": \"\u002Fpath\" }`** - two-way binding: reads from state and enables write-back. Use on the natural value prop (value, checked, pressed, etc.) of form components.\n- **`{ \"$bindItem\": \"field\" }`** - two-way binding to a repeat item field. Use inside repeat scopes.\n- **Filtered lists**: `repeat` plus an `$item` visible condition on the same container renders only matching items: `{ \"repeat\": { \"statePath\": \"\u002Ftasks\", \"key\": \"id\" }, \"visible\": { \"$item\": \"status\", \"eq\": \"todo\" }, \"children\": [\"task-card\"] }`. AND-composed `$state` conjuncts gate the container shell; `$item`\u002F`$index` conjuncts filter items.\n- **Nested lists**: inside a repeat, use `{ \"repeat\": { \"statePath\": { \"$item\": \"comments\" }, \"key\": \"id\" } }` to iterate an array on the enclosing item.\n- **`{ \"$cond\": \u003Ccondition>, \"$then\": \u003Cvalue>, \"$else\": \u003Cvalue> }`** - conditional value\n- **`{ \"$template\": \"Hello, ${\u002Fname}!\" }`** - interpolates state values into strings\n- **`{ \"$computed\": \"fn\", \"args\": { ... } }`** - calls registered functions with resolved args\n\n```json\n{\n  \"type\": \"Input\",\n  \"props\": {\n    \"value\": { \"$bindState\": \"\u002Fform\u002Femail\" },\n    \"placeholder\": \"Email\"\n  }\n}\n```\n\nComponents do not use a `statePath` prop for two-way binding. Use `{ \"$bindState\": \"\u002Fpath\" }` on the natural value prop instead.\n\nComponents receive already-resolved props. For two-way bound props, use the `useBoundProp` hook with the `bindings` map the renderer provides.\n\nRegister `$computed` functions via the `functions` prop on `JSONUIProvider` or `createRenderer`:\n\n```tsx\n\u003CJSONUIProvider\n  functions={{ fullName: (args) => `${args.first} ${args.last}` }}\n>\n```\n\n## Event System\n\nComponents use `emit` to fire named events, or `on()` to get an event handle with metadata. The element's `on` field maps events to action bindings:\n\n```tsx\n\u002F\u002F Simple event firing\nButton: ({ props, emit }) => (\n  \u003Cbutton onClick={() => emit(\"press\")}>{props.label}\u003C\u002Fbutton>\n),\n\n\u002F\u002F Event handle with metadata (e.g. preventDefault)\nLink: ({ props, on }) => {\n  const click = on(\"click\");\n  return (\n    \u003Ca href={props.href} onClick={(e) => {\n      if (click.shouldPreventDefault) e.preventDefault();\n      click.emit();\n    }}>{props.label}\u003C\u002Fa>\n  );\n},\n```\n\n```json\n{\n  \"type\": \"Button\",\n  \"props\": { \"label\": \"Submit\" },\n  \"on\": { \"press\": { \"action\": \"submit\" } }\n}\n```\n\nThe `EventHandle` returned by `on()` has: `emit()`, `shouldPreventDefault` (boolean), and `bound` (boolean).\n\n## State Watchers\n\nElements can declare a `watch` field (top-level, sibling of type\u002Fprops\u002Fchildren) to trigger actions when state values change:\n\n```json\n{\n  \"type\": \"Select\",\n  \"props\": {\n    \"value\": { \"$bindState\": \"\u002Fform\u002Fcountry\" },\n    \"options\": [\"US\", \"Canada\"]\n  },\n  \"watch\": { \"\u002Fform\u002Fcountry\": { \"action\": \"loadCities\" } },\n  \"children\": []\n}\n```\n\n## Built-in Actions\n\nThe `setState`, `pushState`, `removeState`, and `validateForm` actions are built into the React schema and handled automatically by `ActionProvider`. They are injected into AI prompts without needing to be declared in catalog `actions`:\n\n```json\n{ \"action\": \"setState\", \"params\": { \"statePath\": \"\u002FactiveTab\", \"value\": \"home\" } }\n{ \"action\": \"pushState\", \"params\": { \"statePath\": \"\u002Fitems\", \"value\": { \"text\": \"New\" } } }\n{ \"action\": \"removeState\", \"params\": { \"statePath\": \"\u002Fitems\", \"index\": 0 } }\n{ \"action\": \"validateForm\", \"params\": { \"statePath\": \"\u002FformResult\" } }\n```\n\n`validateForm` validates all registered fields and writes `{ valid, errors }` to state.\n\nNote: `statePath` in action params (e.g. `setState.statePath`) targets the mutation path. Two-way binding in component props uses `{ \"$bindState\": \"\u002Fpath\" }` on the value prop, not `statePath`.\n\n## useBoundProp\n\nFor form components that need two-way binding, use `useBoundProp` with the `bindings` map the renderer provides when a prop uses `{ \"$bindState\": \"\u002Fpath\" }` or `{ \"$bindItem\": \"field\" }`:\n\n```tsx\nimport { useBoundProp } from \"@json-render\u002Freact\";\n\nInput: ({ element, bindings }) => {\n  const [value, setValue] = useBoundProp\u003Cstring>(\n    element.props.value,\n    bindings?.value\n  );\n  return (\n    \u003Cinput\n      value={value ?? \"\"}\n      onChange={(e) => setValue(e.target.value)}\n    \u002F>\n  );\n},\n```\n\n`useBoundProp(propValue, bindingPath)` returns `[value, setValue]`. The `value` is the resolved prop; `setValue` writes back to the bound state path (no-op if not bound).\n\n## BaseComponentProps\n\nFor building reusable component libraries not tied to a specific catalog (e.g. `@json-render\u002Fshadcn`):\n\n```typescript\nimport type { BaseComponentProps } from \"@json-render\u002Freact\";\n\nconst Card = ({ props, children }: BaseComponentProps\u003C{ title?: string }>) => (\n  \u003Cdiv>{props.title}{children}\u003C\u002Fdiv>\n);\n```\n\n## defineRegistry\n\n`defineRegistry` conditionally requires the `actions` field only when the catalog declares actions. Catalogs with `actions: {}` can omit it.\n\n## Key Exports\n\n| Export                  | Purpose                                                                                               |\n| ----------------------- | ----------------------------------------------------------------------------------------------------- |\n| `defineRegistry`        | Create a type-safe component registry from a catalog                                                  |\n| `Renderer`              | Render a spec using a registry                                                                        |\n| `schema`                | Element tree schema (includes built-in state actions: setState, pushState, removeState, validateForm) |\n| `useStateStore`         | Access state context                                                                                  |\n| `useStateValue`         | Get single value from state                                                                           |\n| `useBoundProp`          | Two-way binding for `$bindState`\u002F`$bindItem` expressions                                              |\n| `useActions`            | Access actions context                                                                                |\n| `useAction`             | Get a single action dispatch function                                                                 |\n| `useOptionalValidation` | Non-throwing variant of useValidation (returns null if no provider)                                   |\n| `useUIStream`           | Stream specs from an API endpoint                                                                     |\n| `createStateStore`      | Create a framework-agnostic in-memory `StateStore`                                                    |\n| `StateStore`            | Interface for plugging in external state management                                                   |\n| `BaseComponentProps`    | Catalog-agnostic base type for reusable component libraries                                           |\n| `EventHandle`           | Event handle type (`emit`, `shouldPreventDefault`, `bound`)                                           |\n| `ComponentContext`      | Typed component context (catalog-aware)                                                               |\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Freact",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill react",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill react",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill react","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Freact\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]