[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8T6S7ACFG0KB593N50AQA":3,"skill-same:01M7F8T6S7ACFG0KB593N50AQA":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},"01M7F8T6S7ACFG0KB593N50AQA","devtools",null,"Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include \"add devtools\", \"debug json-render\", \"inspect the spec\", \"why is this element not rendering\", \"see the state at runtime\", or requests to tap streams \u002F capture action logs for `@json-render\u002Fdevtools`.","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-前端与设计\u002Fdevtools\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: devtools\ndescription: Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include \"add devtools\", \"debug json-render\", \"inspect the spec\", \"why is this element not rendering\", \"see the state at runtime\", or requests to tap streams \u002F capture action logs for `@json-render\u002Fdevtools`.\n---\n\n# @json-render\u002Fdevtools\n\nA floating inspector panel for json-render apps. Framework-agnostic core + per-framework adapters (React, Vue, Svelte, Solid).\n\nProduction-safe: the component renders `null` when `NODE_ENV === \"production\"`.\n\n## Install\n\nInstall the core package plus the adapter that matches the host app's renderer.\n\n```bash\n# React\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-react\n\n# Vue\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-vue\n\n# Svelte\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-svelte\n\n# Solid\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-solid\n```\n\n## Drop-in usage\n\nPlace `\u003CJsonRenderDevtools \u002F>` anywhere inside the existing `\u003CJSONUIProvider>` (or framework equivalent). No other wiring required.\n\n### React\n\n```tsx\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-react\";\n\n\u003CJSONUIProvider registry={registry} handlers={handlers}>\n  \u003CRenderer spec={spec} registry={registry} \u002F>\n  \u003CJsonRenderDevtools spec={spec} catalog={catalog} messages={messages} \u002F>\n\u003C\u002FJSONUIProvider>;\n```\n\n### Vue\n\n```vue\n\u003Cscript setup>\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-vue\";\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003CJSONUIProvider :registry=\"registry\">\n    \u003CRenderer :spec=\"spec\" :registry=\"registry\" \u002F>\n    \u003CJsonRenderDevtools :spec=\"spec\" :catalog=\"catalog\" :messages=\"messages\" \u002F>\n  \u003C\u002FJSONUIProvider>\n\u003C\u002Ftemplate>\n```\n\n### Svelte\n\n```svelte\n\u003Cscript>\n  import { JsonRenderDevtools } from \"@json-render\u002Fdevtools-svelte\";\n\u003C\u002Fscript>\n\n\u003CJSONUIProvider {registry}>\n  \u003CRenderer {spec} {registry} \u002F>\n  \u003CJsonRenderDevtools {spec} {catalog} {messages} \u002F>\n\u003C\u002FJSONUIProvider>\n```\n\n### Solid\n\n```tsx\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-solid\";\n\n\u003CJSONUIProvider registry={registry}>\n  \u003CRenderer spec={spec()} registry={registry} \u002F>\n  \u003CJsonRenderDevtools\n    spec={spec()}\n    catalog={catalog}\n    messages={messages()}\n  \u002F>\n\u003C\u002FJSONUIProvider>;\n```\n\n## Controls\n\n- Floating toggle appears bottom-right.\n- Hotkey: `Ctrl`\u002F`Cmd` + `Shift` + `J` (configurable via `hotkey` prop).\n- Drawer is resizable; height persists to localStorage.\n\n## Props\n\n- `spec` (`Spec | null`) — current spec.\n- `catalog` (`Catalog | null`) — catalog definition; required for the Catalog panel.\n- `messages` (`UIMessage[]`) — AI SDK `useChat` messages; scanned for spec data parts.\n- `initialOpen` (`boolean`) — start open.\n- `position` (`\"bottom-right\" | \"bottom-left\" | \"right\"`) — dock + toggle corner. `\"bottom-*\"` docks at the bottom; `\"right\"` docks at the right edge full-height (recommended for app-shells that already use `100vh` or fixed bottom bars).\n- `hotkey` (`string | false`) — `\"mod+shift+j\"` by default.\n- `bufferSize` (`number`) — event ring-buffer cap, default 500.\n- `reserveSpace` (`boolean`, default `true`) — when true the panel pushes the host app by applying `padding-bottom` \u002F `padding-right` on `body`. Set to `false` to keep the panel as a pure overlay.\n- `allowDockToggle` (`boolean`, default `true`) — show a toolbar button so the user can flip the panel between bottom-dock and right-dock. User choice persists to `localStorage` and overrides `position` on subsequent mounts. Pass `false` to lock the dock to `position`.\n- `onEvent` (`(DevtoolsEvent) => void`) — optional tap.\n\n## Panels\n\n- **Spec** — element tree rooted at `spec.root`; props\u002Fvisibility\u002Fevents\u002Fwatchers detail; integrated `validateSpec` warnings.\n- **State** — every JSON Pointer path with inline edit via `store.set`.\n- **Actions** — dispatched actions timeline (name, params, result\u002Ferror, duration).\n- **Stream** — spec patches, text chunks, token usage, lifecycle markers grouped by generation.\n- **Catalog** — components + actions declared in the catalog with prop chips.\n\n## Picker (toolbar)\n\nThe element picker is a toolbar button in the panel header (Chrome-DevTools-style), not a tab. Click it to activate pick mode, then click any rendered element in the page — selection jumps to the Spec tab with that element focused. `Esc` cancels.\n\n## Reserved space & docking\n\nThe panel can dock at the bottom or the right edge, and by default the user can flip between the two with a toolbar button (the choice persists to `localStorage`). Set `allowDockToggle={false}` if the host app only works with one dock — the button is hidden and the dock is locked to `position`.\n\nPick an initial dock that fits your layout:\n\n- **Bottom dock (default)** — works best for docs \u002F marketing \u002F content-flow sites and for app shells built with a `height: 100%` chain (`html { height: 100% }` → `body { height: 100% }` → `.app { height: 100% }`). The panel writes its height to `--jr-devtools-offset-bottom` and applies matching `padding-bottom` to `body`, so non-fixed content naturally makes room.\n- **Right dock** (`position=\"right\"`) — recommended for app-shell layouts that use `100vh` or `position: fixed; bottom: 0`. Right docking sidesteps the bottom edge entirely and writes its width to `--jr-devtools-offset-right` instead.\n\nApps that use `100vh`, `position: fixed`, or `position: sticky` can opt specific elements in with the published CSS custom properties:\n\n```css\n.composer   { bottom: var(--jr-devtools-offset-bottom, 0); }\n.sidebar    { right:  var(--jr-devtools-offset-right,  0); }\n.app-shell  { height: calc(100vh - var(--jr-devtools-offset-bottom, 0)); }\n```\n\nIf the automatic body padding causes problems with a particular layout, pass `reserveSpace={false}` to make the panel a pure overlay — the CSS custom properties are still published so you can reserve space manually.\n\n(`--jr-devtools-offset` is kept as a back-compat alias for whichever edge is currently active.)\n\n## Multiple renderers on one page (e.g. a chat)\n\nA single `\u003CJsonRenderDevtools \u002F>` can inspect many `\u003CRenderer \u002F>` instances at once — a chat where each assistant message renders its own spec, a dashboard made of several independent widgets, etc. The recipe:\n\n1. **One top-level `\u003CJSONUIProvider>`** so every renderer shares one state store and one action dispatcher. Devtools lives inside this provider and sees everything through it.\n2. **Per-renderer specs, shared state** — each assistant message renders `\u003CRenderer spec={msgSpec} registry={registry} \u002F>` directly, not wrapped in its own `StateProvider`. State paths from different messages must not collide.\n3. **Namespace state per turn** — when the source is an AI stream, hand the agent a unique `messageId` and require every element key (`\u003Cid>-root`) and state path (`\u002F\u003Cid>\u002Fcount`) to be prefixed with it.\n4. **Pass `spec={latest}` + `messages={all}`** — `spec` drives the Spec panel (usually the newest assistant message's spec), while `messages` feeds the Stream panel with patches from every turn.\n5. **Actions and the picker are already global** — `registerActionObserver` captures dispatches from any `ActionProvider` in the tree, and `data-jr-key` is written by the renderer itself, so Pick works across every rendered element regardless of which message produced it.\n\nSee `examples\u002Fdevtools` for a full AI chat wired this way.\n\n## Imperative API (React only)\n\n```tsx\nimport { useJsonRenderDevtools } from \"@json-render\u002Fdevtools-react\";\n\nconst devtools = useJsonRenderDevtools();\ndevtools?.open();\ndevtools?.toggle();\ndevtools?.recordEvent({ kind: \"stream-text\", at: Date.now(), text: \"hi\" });\n```\n\nReturns `null` in production or before the component mounts.\n\n## Server-side stream tap\n\nCapture spec patches at the API route so events persist server-side or flow into your own telemetry.\n\n```ts\nimport { tapJsonRenderStream, createEventStore } from \"@json-render\u002Fdevtools\";\nimport { pipeJsonRender } from \"@json-render\u002Fcore\";\n\nconst events = createEventStore({ bufferSize: 1000 });\nconst tapped = tapJsonRenderStream(result.toUIMessageStream(), events);\nwriter.merge(pipeJsonRender(tapped));\n```\n\nYAML equivalent: `tapYamlStream`.\n\n## Under the hood\n\n- **Shadow-DOM isolated panel** — the panel's styles never leak into the host app and vice versa.\n- **Ring-buffered event store** — capped log of devtools events (state changes, action dispatches, stream patches, etc.).\n- **Action observer registry** — each framework's `ActionProvider` reports via `notifyActionDispatch` \u002F `notifyActionSettle` in `@json-render\u002Fcore`; devtools subscribes via `registerActionObserver`.\n- **Picker element tagging** — while devtools is mounted, `ElementRenderer` wraps each rendered element in `\u003Cspan data-jr-key=\"...\" style=\"display:contents\">` so the picker can map DOM → spec key. No layout impact.\n","# @json-render\u002Fdevtools\n\nA floating inspector panel for json-render apps. Framework-agnostic core + per-framework adapters (React, Vue, Svelte, Solid).\n\nProduction-safe: the component renders `null` when `NODE_ENV === \"production\"`.\n\n## Install\n\nInstall the core package plus the adapter that matches the host app's renderer.\n\n```bash\n# React\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-react\n\n# Vue\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-vue\n\n# Svelte\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-svelte\n\n# Solid\nnpm install @json-render\u002Fdevtools @json-render\u002Fdevtools-solid\n```\n\n## Drop-in usage\n\nPlace `\u003CJsonRenderDevtools \u002F>` anywhere inside the existing `\u003CJSONUIProvider>` (or framework equivalent). No other wiring required.\n\n### React\n\n```tsx\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-react\";\n\n\u003CJSONUIProvider registry={registry} handlers={handlers}>\n  \u003CRenderer spec={spec} registry={registry} \u002F>\n  \u003CJsonRenderDevtools spec={spec} catalog={catalog} messages={messages} \u002F>\n\u003C\u002FJSONUIProvider>;\n```\n\n### Vue\n\n```vue\n\u003Cscript setup>\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-vue\";\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003CJSONUIProvider :registry=\"registry\">\n    \u003CRenderer :spec=\"spec\" :registry=\"registry\" \u002F>\n    \u003CJsonRenderDevtools :spec=\"spec\" :catalog=\"catalog\" :messages=\"messages\" \u002F>\n  \u003C\u002FJSONUIProvider>\n\u003C\u002Ftemplate>\n```\n\n### Svelte\n\n```svelte\n\u003Cscript>\n  import { JsonRenderDevtools } from \"@json-render\u002Fdevtools-svelte\";\n\u003C\u002Fscript>\n\n\u003CJSONUIProvider {registry}>\n  \u003CRenderer {spec} {registry} \u002F>\n  \u003CJsonRenderDevtools {spec} {catalog} {messages} \u002F>\n\u003C\u002FJSONUIProvider>\n```\n\n### Solid\n\n```tsx\nimport { JsonRenderDevtools } from \"@json-render\u002Fdevtools-solid\";\n\n\u003CJSONUIProvider registry={registry}>\n  \u003CRenderer spec={spec()} registry={registry} \u002F>\n  \u003CJsonRenderDevtools\n    spec={spec()}\n    catalog={catalog}\n    messages={messages()}\n  \u002F>\n\u003C\u002FJSONUIProvider>;\n```\n\n## Controls\n\n- Floating toggle appears bottom-right.\n- Hotkey: `Ctrl`\u002F`Cmd` + `Shift` + `J` (configurable via `hotkey` prop).\n- Drawer is resizable; height persists to localStorage.\n\n## Props\n\n- `spec` (`Spec | null`) — current spec.\n- `catalog` (`Catalog | null`) — catalog definition; required for the Catalog panel.\n- `messages` (`UIMessage[]`) — AI SDK `useChat` messages; scanned for spec data parts.\n- `initialOpen` (`boolean`) — start open.\n- `position` (`\"bottom-right\" | \"bottom-left\" | \"right\"`) — dock + toggle corner. `\"bottom-*\"` docks at the bottom; `\"right\"` docks at the right edge full-height (recommended for app-shells that already use `100vh` or fixed bottom bars).\n- `hotkey` (`string | false`) — `\"mod+shift+j\"` by default.\n- `bufferSize` (`number`) — event ring-buffer cap, default 500.\n- `reserveSpace` (`boolean`, default `true`) — when true the panel pushes the host app by applying `padding-bottom` \u002F `padding-right` on `body`. Set to `false` to keep the panel as a pure overlay.\n- `allowDockToggle` (`boolean`, default `true`) — show a toolbar button so the user can flip the panel between bottom-dock and right-dock. User choice persists to `localStorage` and overrides `position` on subsequent mounts. Pass `false` to lock the dock to `position`.\n- `onEvent` (`(DevtoolsEvent) => void`) — optional tap.\n\n## Panels\n\n- **Spec** — element tree rooted at `spec.root`; props\u002Fvisibility\u002Fevents\u002Fwatchers detail; integrated `validateSpec` warnings.\n- **State** — every JSON Pointer path with inline edit via `store.set`.\n- **Actions** — dispatched actions timeline (name, params, result\u002Ferror, duration).\n- **Stream** — spec patches, text chunks, token usage, lifecycle markers grouped by generation.\n- **Catalog** — components + actions declared in the catalog with prop chips.\n\n## Picker (toolbar)\n\nThe element picker is a toolbar button in the panel header (Chrome-DevTools-style), not a tab. Click it to activate pick mode, then click any rendered element in the page — selection jumps to the Spec tab with that element focused. `Esc` cancels.\n\n## Reserved space & docking\n\nThe panel can dock at the bottom or the right edge, and by default the user can flip between the two with a toolbar button (the choice persists to `localStorage`). Set `allowDockToggle={false}` if the host app only works with one dock — the button is hidden and the dock is locked to `position`.\n\nPick an initial dock that fits your layout:\n\n- **Bottom dock (default)** — works best for docs \u002F marketing \u002F content-flow sites and for app shells built with a `height: 100%` chain (`html { height: 100% }` → `body { height: 100% }` → `.app { height: 100% }`). The panel writes its height to `--jr-devtools-offset-bottom` and applies matching `padding-bottom` to `body`, so non-fixed content naturally makes room.\n- **Right dock** (`position=\"right\"`) — recommended for app-shell layouts that use `100vh` or `position: fixed; bottom: 0`. Right docking sidesteps the bottom edge entirely and writes its width to `--jr-devtools-offset-right` instead.\n\nApps that use `100vh`, `position: fixed`, or `position: sticky` can opt specific elements in with the published CSS custom properties:\n\n```css\n.composer   { bottom: var(--jr-devtools-offset-bottom, 0); }\n.sidebar    { right:  var(--jr-devtools-offset-right,  0); }\n.app-shell  { height: calc(100vh - var(--jr-devtools-offset-bottom, 0)); }\n```\n\nIf the automatic body padding causes problems with a particular layout, pass `reserveSpace={false}` to make the panel a pure overlay — the CSS custom properties are still published so you can reserve space manually.\n\n(`--jr-devtools-offset` is kept as a back-compat alias for whichever edge is currently active.)\n\n## Multiple renderers on one page (e.g. a chat)\n\nA single `\u003CJsonRenderDevtools \u002F>` can inspect many `\u003CRenderer \u002F>` instances at once — a chat where each assistant message renders its own spec, a dashboard made of several independent widgets, etc. The recipe:\n\n1. **One top-level `\u003CJSONUIProvider>`** so every renderer shares one state store and one action dispatcher. Devtools lives inside this provider and sees everything through it.\n2. **Per-renderer specs, shared state** — each assistant message renders `\u003CRenderer spec={msgSpec} registry={registry} \u002F>` directly, not wrapped in its own `StateProvider`. State paths from different messages must not collide.\n3. **Namespace state per turn** — when the source is an AI stream, hand the agent a unique `messageId` and require every element key (`\u003Cid>-root`) and state path (`\u002F\u003Cid>\u002Fcount`) to be prefixed with it.\n4. **Pass `spec={latest}` + `messages={all}`** — `spec` drives the Spec panel (usually the newest assistant message's spec), while `messages` feeds the Stream panel with patches from every turn.\n5. **Actions and the picker are already global** — `registerActionObserver` captures dispatches from any `ActionProvider` in the tree, and `data-jr-key` is written by the renderer itself, so Pick works across every rendered element regardless of which message produced it.\n\nSee `examples\u002Fdevtools` for a full AI chat wired this way.\n\n## Imperative API (React only)\n\n```tsx\nimport { useJsonRenderDevtools } from \"@json-render\u002Fdevtools-react\";\n\nconst devtools = useJsonRenderDevtools();\ndevtools?.open();\ndevtools?.toggle();\ndevtools?.recordEvent({ kind: \"stream-text\", at: Date.now(), text: \"hi\" });\n```\n\nReturns `null` in production or before the component mounts.\n\n## Server-side stream tap\n\nCapture spec patches at the API route so events persist server-side or flow into your own telemetry.\n\n```ts\nimport { tapJsonRenderStream, createEventStore } from \"@json-render\u002Fdevtools\";\nimport { pipeJsonRender } from \"@json-render\u002Fcore\";\n\nconst events = createEventStore({ bufferSize: 1000 });\nconst tapped = tapJsonRenderStream(result.toUIMessageStream(), events);\nwriter.merge(pipeJsonRender(tapped));\n```\n\nYAML equivalent: `tapYamlStream`.\n\n## Under the hood\n\n- **Shadow-DOM isolated panel** — the panel's styles never leak into the host app and vice versa.\n- **Ring-buffered event store** — capped log of devtools events (state changes, action dispatches, stream patches, etc.).\n- **Action observer registry** — each framework's `ActionProvider` reports via `notifyActionDispatch` \u002F `notifyActionSettle` in `@json-render\u002Fcore`; devtools subscribes via `registerActionObserver`.\n- **Picker element tagging** — while devtools is mounted, `ElementRenderer` wraps each rendered element in `\u003Cspan data-jr-key=\"...\" style=\"display:contents\">` so the picker can map DOM → spec key. No layout impact.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fdevtools",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 devtools",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill devtools",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill devtools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdevtools\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",[],[]]