[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FA2QKKMTWMNNRXGKJM76P5":3,"skill-same:01M7FA2QKKMTWMNNRXGKJM76P5":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FA2QKKMTWMNNRXGKJM76P5","inspector-workbench",null,"Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit\u002Fweb-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.","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-前端与设计\u002Finspector-workbench\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: inspector-workbench\ndescription: >\n  Runs Inspector UI work on the standalone Threads state lab so the agent\n  can see the overlay. Use when a CopilotKit employee asks an agent to\n  fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions,\n  launcher, Home, Threads, Playground, Memory, or any visual behavior in\n  @copilotkit\u002Fweb-inspector. Don't use for docs-only Callout updates (load\n  inspector-docs), runtime or core changes with no Inspector UI, showcase\n  cell work, or reading Inspector as a consumer inside an app.\nversion: 1.0.0\n---\n\n# Inspector Workbench\n\nThe Inspector overlay is a visual product. Code that compiles is not proof.\nThe agent must run the standalone workbench and look at screenshots after\neach visual change.\n\nThis skill does not replace `inspector-docs`. If a pane is added, renamed,\nor removed, load `inspector-docs` as well.\n\n## When To Use\n\nLoad this skill at the start of any task that changes\n`packages\u002Fweb-inspector` UI, chrome, or overlay behavior.\n\nDo not load it for docs-only Callout work. Do not load it for showcase\ncells. If the host app is the bug (z-index against host CSS, CopilotChat\nlayout), use that host, then still take screenshots.\n\n## Default host\n\nThe default host is the standalone Threads state lab:\n\n- Command, from the repo root: `nx run @copilotkit\u002Fweb-inspector:dev:standalone`\n- URL: `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&reset=1`\n- The lab mounts the real `cpk-web-inspector` and opens the overlay.\n\nDo not start a showcase app, an example app, or Storybook as the default\nhost. Those are slower and hide Inspector-only faults.\n\nThe Nx target runs Vite and the CSS watch together. Do not run Vite alone.\nDo not run `pnpm --filter @copilotkit\u002Fweb-inspector run dev`. That watch\nserves consumers, not this lab.\n\n## Procedures\n\n### Procedure 1: Start the workbench\n\n1. If the change adds, renames, or removes a pane, load `inspector-docs` too.\n2. From the repo root, start `nx run @copilotkit\u002Fweb-inspector:dev:standalone`.\n3. Wait until `http:\u002F\u002F127.0.0.1:5177` serves.\n4. Open the browser tool this session has (Playwright MCP, Claude browser, or Codex computer use).\n5. Go to `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&reset=1`.\n6. If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.\n7. Wait until the overlay is open on Home or Threads. The lab clicks the launcher.\n8. Take a baseline screenshot. Look at it before any edit.\n\n### Procedure 2: Edit, screenshot, look\n\n1. Edit Inspector source under `packages\u002Fweb-inspector\u002Fsrc`.\n2. Wait for Vite to reload the lab.\n3. If the page did not pick up the change, reload the lab URL, then wait for the overlay.\n4. Take a screenshot of the pane that must change.\n5. If the browser tool writes a file, write it under `.inspector-workbench\u002F\u003Ctask>\u002F`. Never write a PNG at the repo root.\n6. Look at the screenshot. If the change is not visible, the work is not done.\n7. Repeat steps 1–6 after every visual change.\n8. If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.\n9. If theme or contrast is in scope, take light and dark screenshots.\n\nUnit tests still belong in the same change. Screenshots do not replace tests.\n\n### Procedure 3: Stop the workbench\n\n1. After the Inspector task is done, stop the `dev:standalone` process tree.\n2. Do not leave Vite or the CSS watch running.\n3. Do not commit files under `.inspector-workbench\u002F`.\n4. Do not commit PNG files at the repo root.\n\n## Decision Tree\n\n- Inspector UI, chrome, overlay, launcher, or pane visuals:\n  - Start: Procedure 1\n  - While editing: Procedure 2\n  - After the task: Procedure 3\n  - If a pane is added, renamed, or removed: also load `inspector-docs`\n- Docs Callout only: stop. Load `inspector-docs` instead.\n- Bug exists only inside a host app: use that host, then still follow Procedure 2 screenshots.\n- Runtime or core change with no Inspector UI: this skill does not apply.\n\n## Red Flags\n\n| Signal                                              | What it means                        | Do instead                                            |\n| --------------------------------------------------- | ------------------------------------ | ----------------------------------------------------- |\n| Showcase, example, or Storybook is the first server | The agent skipped the workbench      | Stop that server. Run Procedure 1                     |\n| No screenshot after a visual edit                   | The agent is guessing from CSS       | Take a screenshot. Look at it                         |\n| PNG files at the repo root (`inspector-open.png`)   | The screenshot path is wrong         | Write under `.inspector-workbench\u002F\u003Ctask>\u002F`            |\n| \"The CSS looks correct, so the UI is done\"          | Overlay bugs do not show in source   | Screenshot the lab. Fix what the image shows          |\n| Vite started without the Nx target                  | CSS watch is missing                 | Use `nx run @copilotkit\u002Fweb-inspector:dev:standalone` |\n| Port 5178 or a random port                          | The lab pins 5177                    | Free 5177. Do not pick another port                   |\n| Workbench still running after the task              | Watchers leak memory on this machine | Run Procedure 3                                       |\n| Pane added with no `inspector-docs` pass            | Docs Callout will drift              | Load `inspector-docs` in the same change              |\n\n## Error Handling\n\n- **Port 5177 is in use**: stop the leftover Inspector workbench on that port, then retry Procedure 1. Do not pick another port. The lab uses `strictPort`.\n- **No browser tool in this session**: tell the user the session cannot see Inspector. Do not guess visual results from CSS or unit tests alone.\n- **Lab is blank or the overlay is closed**: wait for boot. Then screenshot the lab console Runtime line. If Runtime is not connected, fix the lab before UI edits.\n- **Screenshot does not show the intended change**: do not claim done. Reload, screenshot again, then fix the source.\n- **HMR did not apply a source edit**: reload `http:\u002F\u002F127.0.0.1:5177` with the same scenario query. Then screenshot.\n- **Need a closed launcher or unread halo**: open `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&replay-notification=1`.\n- **Any unexpected error**: halt and surface the raw error. Do not switch to a showcase app to work around the lab.\n","# Inspector Workbench\n\nThe Inspector overlay is a visual product. Code that compiles is not proof.\nThe agent must run the standalone workbench and look at screenshots after\neach visual change.\n\nThis skill does not replace `inspector-docs`. If a pane is added, renamed,\nor removed, load `inspector-docs` as well.\n\n## When To Use\n\nLoad this skill at the start of any task that changes\n`packages\u002Fweb-inspector` UI, chrome, or overlay behavior.\n\nDo not load it for docs-only Callout work. Do not load it for showcase\ncells. If the host app is the bug (z-index against host CSS, CopilotChat\nlayout), use that host, then still take screenshots.\n\n## Default host\n\nThe default host is the standalone Threads state lab:\n\n- Command, from the repo root: `nx run @copilotkit\u002Fweb-inspector:dev:standalone`\n- URL: `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&reset=1`\n- The lab mounts the real `cpk-web-inspector` and opens the overlay.\n\nDo not start a showcase app, an example app, or Storybook as the default\nhost. Those are slower and hide Inspector-only faults.\n\nThe Nx target runs Vite and the CSS watch together. Do not run Vite alone.\nDo not run `pnpm --filter @copilotkit\u002Fweb-inspector run dev`. That watch\nserves consumers, not this lab.\n\n## Procedures\n\n### Procedure 1: Start the workbench\n\n1. If the change adds, renames, or removes a pane, load `inspector-docs` too.\n2. From the repo root, start `nx run @copilotkit\u002Fweb-inspector:dev:standalone`.\n3. Wait until `http:\u002F\u002F127.0.0.1:5177` serves.\n4. Open the browser tool this session has (Playwright MCP, Claude browser, or Codex computer use).\n5. Go to `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&reset=1`.\n6. If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.\n7. Wait until the overlay is open on Home or Threads. The lab clicks the launcher.\n8. Take a baseline screenshot. Look at it before any edit.\n\n### Procedure 2: Edit, screenshot, look\n\n1. Edit Inspector source under `packages\u002Fweb-inspector\u002Fsrc`.\n2. Wait for Vite to reload the lab.\n3. If the page did not pick up the change, reload the lab URL, then wait for the overlay.\n4. Take a screenshot of the pane that must change.\n5. If the browser tool writes a file, write it under `.inspector-workbench\u002F\u003Ctask>\u002F`. Never write a PNG at the repo root.\n6. Look at the screenshot. If the change is not visible, the work is not done.\n7. Repeat steps 1–6 after every visual change.\n8. If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.\n9. If theme or contrast is in scope, take light and dark screenshots.\n\nUnit tests still belong in the same change. Screenshots do not replace tests.\n\n### Procedure 3: Stop the workbench\n\n1. After the Inspector task is done, stop the `dev:standalone` process tree.\n2. Do not leave Vite or the CSS watch running.\n3. Do not commit files under `.inspector-workbench\u002F`.\n4. Do not commit PNG files at the repo root.\n\n## Decision Tree\n\n- Inspector UI, chrome, overlay, launcher, or pane visuals:\n  - Start: Procedure 1\n  - While editing: Procedure 2\n  - After the task: Procedure 3\n  - If a pane is added, renamed, or removed: also load `inspector-docs`\n- Docs Callout only: stop. Load `inspector-docs` instead.\n- Bug exists only inside a host app: use that host, then still follow Procedure 2 screenshots.\n- Runtime or core change with no Inspector UI: this skill does not apply.\n\n## Red Flags\n\n| Signal                                              | What it means                        | Do instead                                            |\n| --------------------------------------------------- | ------------------------------------ | ----------------------------------------------------- |\n| Showcase, example, or Storybook is the first server | The agent skipped the workbench      | Stop that server. Run Procedure 1                     |\n| No screenshot after a visual edit                   | The agent is guessing from CSS       | Take a screenshot. Look at it                         |\n| PNG files at the repo root (`inspector-open.png`)   | The screenshot path is wrong         | Write under `.inspector-workbench\u002F\u003Ctask>\u002F`            |\n| \"The CSS looks correct, so the UI is done\"          | Overlay bugs do not show in source   | Screenshot the lab. Fix what the image shows          |\n| Vite started without the Nx target                  | CSS watch is missing                 | Use `nx run @copilotkit\u002Fweb-inspector:dev:standalone` |\n| Port 5178 or a random port                          | The lab pins 5177                    | Free 5177. Do not pick another port                   |\n| Workbench still running after the task              | Watchers leak memory on this machine | Run Procedure 3                                       |\n| Pane added with no `inspector-docs` pass            | Docs Callout will drift              | Load `inspector-docs` in the same change              |\n\n## Error Handling\n\n- **Port 5177 is in use**: stop the leftover Inspector workbench on that port, then retry Procedure 1. Do not pick another port. The lab uses `strictPort`.\n- **No browser tool in this session**: tell the user the session cannot see Inspector. Do not guess visual results from CSS or unit tests alone.\n- **Lab is blank or the overlay is closed**: wait for boot. Then screenshot the lab console Runtime line. If Runtime is not connected, fix the lab before UI edits.\n- **Screenshot does not show the intended change**: do not claim done. Reload, screenshot again, then fix the source.\n- **HMR did not apply a source edit**: reload `http:\u002F\u002F127.0.0.1:5177` with the same scenario query. Then screenshot.\n- **Need a closed launcher or unread halo**: open `http:\u002F\u002F127.0.0.1:5177\u002F?scenario=pro-enabled-existing&replay-notification=1`.\n- **Any unexpected error**: halt and surface the raw error. Do not switch to a showcase app to work around the lab.\n",{"name":5,"version":24,"description":25},"1.0.0","Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit\u002Fweb-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.\n","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Finspector-workbench",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill inspector-workbench",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill inspector-workbench",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill inspector-workbench","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Finspector-workbench\u002FSKILL.md",true,[],[49,56,61,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]