[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F77PNVCJ50AP7KYC803VY7":3,"skill-same:01M7F77PNVCJ50AP7KYC803VY7":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},"01M7F77PNVCJ50AP7KYC803VY7","a11y-page-audit",null,"Run an accessibility and keyboard navigation audit on a web page or project, then fix what it finds — audit, fix, and verify, not just a report. Use whenever the user asks about accessibility, a11y, keyboard navigation, focus styles or focus management, screen readers, ARIA, WCAG compliance, skip links, tab order, or making a site keyboard-navigable before shipping.","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-前端与设计\u002Fa11y-page-audit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: a11y-page-audit\ndescription: >\n  Run an accessibility and keyboard navigation audit on a web page or project, then fix\n  what it finds — audit, fix, and verify, not just a report. Use whenever the user asks\n  about accessibility, a11y, keyboard navigation, focus styles or focus management,\n  screen readers, ARIA, WCAG compliance, skip links, tab order, or making a site\n  keyboard-navigable before shipping.\n---\n\n# Accessibility & Keyboard Navigation Audit\n\nAudit-then-fix workflow. The goal is to leave the codebase with working keyboard nav,\nvisible focus indicators, correct semantics, and proper ARIA — not just a report.\n\n## Phase 0 — Understand the target\n\n1. **Input type**: directory → scan components, layouts, global CSS. URL → fetch HTML and\n   flag that source fixes need the actual codebase.\n2. **Framework**: determines where layouts, head tags, and route changes live.\n3. **Design system**: tokens \u002F CSS custom properties \u002F Tailwind \u002F component library —\n   determines how to implement the focus ring.\n\nIf ambiguous, ask one focused question before proceeding.\n\n## Phase 1 — Audit & fix\n\nWork through each category: record file path, current state, verdict (✅ PASS \u002F ⚠️ WARN \u002F\n❌ FAIL), then apply the fix pattern for every ❌ and ⚠️.\n\n### 1.1 Global CSS resets\n\n**Check**: `* { outline: none }`, `*:focus { outline: none }`, or any blanket `outline: 0`\nwithout a paired visible alternative — the most common a11y regression.\n\n**Fix**: remove global outline resets. If a component legitimately needs a custom\nindicator (e.g. `box-shadow` ring on inputs), keep `outline: none` only when paired with a\nvisible alternative using the focus token.\n\n### 1.2 Focus ring system\n\n**Check**: is there a shared, theme-aware focus ring?\n- A design token \u002F custom property for focus color that adapts between light and dark mode\n- Passes WCAG AA contrast for UI components (3:1) against each mode's background\n- A global `:focus-visible` rule applying the ring\n- Components aliasing the token rather than hardcoding hex values\n\n**Fix** — if missing, build it:\n1. Add a system-level focus color token per theme. Pick from the existing palette when\n   possible; each mode's value must pass 3:1 against that mode's background. If the brand\n   palette has no passing color, use the closest passing color and document the override\n   — don't sacrifice visibility for brand consistency.\n2. Add component-level tokens aliasing it: `--focus-ring-color`, `--focus-ring-width: 2px`,\n   `--focus-ring-offset: 2px`.\n3. Add the global rule:\n   ```css\n   :focus-visible {\n     outline: var(--focus-ring-width) solid var(--focus-ring-color);\n     outline-offset: var(--focus-ring-offset);\n   }\n   ```\n   Do NOT set `border-radius` here — `outline` follows the element's existing radius\n   automatically; setting it changes the element's shape on focus.\n4. Re-point existing per-component focus tokens to alias the system color.\n\n### 1.3 Interactive elements\n\n**Check** focus visibility and keyboard operability for: buttons (real `\u003Cbutton>` vs\n`\u003Cdiv onClick>`), links (incl. anchor-wrapped cards), form inputs and custom checkboxes,\ncustom widgets (dropdowns, accordions, toggles, hamburger menus — keyboard operable?\n`aria-expanded`?), and persistent landmarks (header\u002Ffooter\u002Fnav tab order).\n\nWatch for: `:focus` used instead of `:focus-visible` (rings on mouse click);\n`outline: none` with no visible alternative; non-interactive elements with `onClick` but no\n`role`, `tabIndex`, or keyboard handler.\n\n**Fix**: replace `:focus` selectors with `:focus-visible` unless there's a documented\nreason (rare — e.g. a text input that should always show its ring). Make custom widgets\nkeyboard-operable.\n\n### 1.4 Skip link (WCAG 2.4.1)\n\n**Check**: exists; is the first focusable element; target `\u003Cmain>` has `tabIndex={-1}` so\nfocus actually moves; hidden with `transform` (not `display: none` — removes it from tab\norder); revealed on `:focus-visible` (not `:focus` — shows on mouse click).\n\n**Fix** — if missing:\n```jsx\n\u003Ca href=\"#main-content\" className=\"skip-to-content\">Skip to main content\u003C\u002Fa>\n\u003Cmain id=\"main-content\" tabIndex={-1}>...\u003C\u002Fmain>\n```\nHidden by default via `transform: translateY(-200%)`, revealed on `:focus-visible`, styled\nthrough design tokens, high z-index.\n\n### 1.5 Semantic HTML\n\n**Check**:\n- Exactly one `\u003Cmain>` per page (SPAs commonly nest multiples)\n- One `\u003Ch1>`, no skipped heading levels\n- Landmarks (`\u003Cheader>`, `\u003Cnav>`, `\u003Cmain>`, `\u003Cfooter>`, `\u003Caside>`) instead of `\u003Cdiv>` + role\n- Footer\u002Fsidebar section titles are headings, not `\u003Cp>`\u002F`\u003Cspan>`\n- No double-announcing: `alt=\"\"` on decorative images whose accessible name comes from a\n  sibling\n- `\u003Chtml lang=\"...\">` set\n\n**Fix**: collapse nested `\u003Cmain>`s (keep one, demote others to `\u003Cdiv>`); promote section\ntitles to headings with `font-family: inherit; margin-top: 0;` to preserve rendering; fix\nheading gaps; set decorative `alt=\"\"`; add `lang`.\n\n### 1.6 ARIA\n\n**Check & fix**:\n- Icon-only buttons (hamburger, theme toggle, close, search) → `aria-label`\n- Disclosure triggers (menus, accordions, collapsibles) → `aria-expanded` (with JS toggle\n  if needed)\n- Form errors → `aria-invalid` + `aria-describedby` linking to the message\n- Decorative SVGs\u002Femojis next to text → `aria-hidden=\"true\"`\n- Remove redundant ARIA (`\u003Cbutton role=\"button\">`, `\u003Cnav role=\"navigation\">`)\n\n### 1.7 SPA route-change focus (if applicable)\n\n**Check**: after client-side navigation, does focus reset so the next Tab starts from the\ntop? Does scroll reset?\n\n**Fix**: in the route-change\u002Fscroll-restoration hook, scroll to top and blur\n`document.activeElement` (when it's an HTMLElement other than `body`) on pathname change.\n\n### 1.8 Overflow-hidden focus clipping\n\n**Check**: parents with `overflow: hidden` (cards, pills, button groups) containing\nfocusable children — the parent clips an outline that extends beyond its bounds.\n\n**Fix**:\n- **Pill \u002F small element**: negative offset so the ring draws inside — `outline-offset: -2px`\n- **Card \u002F large target**: move the ring to the parent and suppress the inner one:\n  ```css\n  .card:has(a:focus-visible) {\n    outline: var(--focus-ring-width) solid var(--focus-ring-color);\n    outline-offset: var(--focus-ring-offset);\n  }\n  .card a:focus-visible { outline: none; }\n  ```\n  Use `:has(:focus-visible)`, not `:focus-within` — the latter triggers on mouse focus.\n\n## Phase 2 — Verify\n\n**Keyboard walkthrough** (repeat on every major route):\n1. Load the page, press Tab — first stop must be the skip link.\n2. Continue: skip-link → logo → nav → main CTAs → cards → footer links. Nothing silently\n   skipped; no focus trap (except modals with proper escape handling).\n3. Every focused element shows a clearly visible ring.\n4. Toggle dark mode, tab again — ring switches color and stays visible.\n5. Route changes reset focus to the top (next Tab hits skip-link again).\n\n**Forms**: tab into every input (indicator visible), Enter submits, error states expose\n`aria-invalid` + linked messages.\n\n**Automated smoke test**: run axe DevTools or Lighthouse a11y. Treat the score as a\nregression catch, not a substitute for the manual walkthrough.\n\n## Report\n\n```\n## Accessibility Audit Report — [Page\u002FProject]\n\nFocus System     [PASS \u002F BUILT \u002F NEEDS WORK]\nSkip Link        [PASS \u002F ADDED \u002F MISSING]\nKeyboard Nav     [score \u002F10] + findings\nSemantic HTML    [score \u002F10] + findings\nARIA             [score \u002F10] + findings\nSPA Focus Reset  [PASS \u002F FIXED \u002F N\u002FA]\n\n### Changes made\n- [files modified\u002Fcreated, one line each]\n\n### Still needs human attention\n- [manual testing, content decisions, visual review]\n\n### Conventions to document\n- [rules for AGENTS.md \u002F CLAUDE.md so future contributors maintain these patterns]\n```\n\n## Notes & edge cases\n\n- **Tailwind**: check for `outline-none` in the base layer; replace with\n  `focus-visible:ring-*` utilities tied to the token.\n- **Component libraries (Radix, Headless UI, shadcn)**: they handle ARIA internally — audit\n  the rendered DOM, not the source.\n- **CSS-in-JS**: focus resets may hide in `createGlobalStyle` or theme objects — search all\n  style definitions for `outline`.\n- **Next.js App Router**: route-change focus reset lives in a client component wrapping\n  `usePathname()`; the skip-link target goes on `\u003Cmain>` in `app\u002Flayout.tsx`.\n","# Accessibility & Keyboard Navigation Audit\n\nAudit-then-fix workflow. The goal is to leave the codebase with working keyboard nav,\nvisible focus indicators, correct semantics, and proper ARIA — not just a report.\n\n## Phase 0 — Understand the target\n\n1. **Input type**: directory → scan components, layouts, global CSS. URL → fetch HTML and\n   flag that source fixes need the actual codebase.\n2. **Framework**: determines where layouts, head tags, and route changes live.\n3. **Design system**: tokens \u002F CSS custom properties \u002F Tailwind \u002F component library —\n   determines how to implement the focus ring.\n\nIf ambiguous, ask one focused question before proceeding.\n\n## Phase 1 — Audit & fix\n\nWork through each category: record file path, current state, verdict (✅ PASS \u002F ⚠️ WARN \u002F\n❌ FAIL), then apply the fix pattern for every ❌ and ⚠️.\n\n### 1.1 Global CSS resets\n\n**Check**: `* { outline: none }`, `*:focus { outline: none }`, or any blanket `outline: 0`\nwithout a paired visible alternative — the most common a11y regression.\n\n**Fix**: remove global outline resets. If a component legitimately needs a custom\nindicator (e.g. `box-shadow` ring on inputs), keep `outline: none` only when paired with a\nvisible alternative using the focus token.\n\n### 1.2 Focus ring system\n\n**Check**: is there a shared, theme-aware focus ring?\n- A design token \u002F custom property for focus color that adapts between light and dark mode\n- Passes WCAG AA contrast for UI components (3:1) against each mode's background\n- A global `:focus-visible` rule applying the ring\n- Components aliasing the token rather than hardcoding hex values\n\n**Fix** — if missing, build it:\n1. Add a system-level focus color token per theme. Pick from the existing palette when\n   possible; each mode's value must pass 3:1 against that mode's background. If the brand\n   palette has no passing color, use the closest passing color and document the override\n   — don't sacrifice visibility for brand consistency.\n2. Add component-level tokens aliasing it: `--focus-ring-color`, `--focus-ring-width: 2px`,\n   `--focus-ring-offset: 2px`.\n3. Add the global rule:\n   ```css\n   :focus-visible {\n     outline: var(--focus-ring-width) solid var(--focus-ring-color);\n     outline-offset: var(--focus-ring-offset);\n   }\n   ```\n   Do NOT set `border-radius` here — `outline` follows the element's existing radius\n   automatically; setting it changes the element's shape on focus.\n4. Re-point existing per-component focus tokens to alias the system color.\n\n### 1.3 Interactive elements\n\n**Check** focus visibility and keyboard operability for: buttons (real `\u003Cbutton>` vs\n`\u003Cdiv onClick>`), links (incl. anchor-wrapped cards), form inputs and custom checkboxes,\ncustom widgets (dropdowns, accordions, toggles, hamburger menus — keyboard operable?\n`aria-expanded`?), and persistent landmarks (header\u002Ffooter\u002Fnav tab order).\n\nWatch for: `:focus` used instead of `:focus-visible` (rings on mouse click);\n`outline: none` with no visible alternative; non-interactive elements with `onClick` but no\n`role`, `tabIndex`, or keyboard handler.\n\n**Fix**: replace `:focus` selectors with `:focus-visible` unless there's a documented\nreason (rare — e.g. a text input that should always show its ring). Make custom widgets\nkeyboard-operable.\n\n### 1.4 Skip link (WCAG 2.4.1)\n\n**Check**: exists; is the first focusable element; target `\u003Cmain>` has `tabIndex={-1}` so\nfocus actually moves; hidden with `transform` (not `display: none` — removes it from tab\norder); revealed on `:focus-visible` (not `:focus` — shows on mouse click).\n\n**Fix** — if missing:\n```jsx\n\u003Ca href=\"#main-content\" className=\"skip-to-content\">Skip to main content\u003C\u002Fa>\n\u003Cmain id=\"main-content\" tabIndex={-1}>...\u003C\u002Fmain>\n```\nHidden by default via `transform: translateY(-200%)`, revealed on `:focus-visible`, styled\nthrough design tokens, high z-index.\n\n### 1.5 Semantic HTML\n\n**Check**:\n- Exactly one `\u003Cmain>` per page (SPAs commonly nest multiples)\n- One `\u003Ch1>`, no skipped heading levels\n- Landmarks (`\u003Cheader>`, `\u003Cnav>`, `\u003Cmain>`, `\u003Cfooter>`, `\u003Caside>`) instead of `\u003Cdiv>` + role\n- Footer\u002Fsidebar section titles are headings, not `\u003Cp>`\u002F`\u003Cspan>`\n- No double-announcing: `alt=\"\"` on decorative images whose accessible name comes from a\n  sibling\n- `\u003Chtml lang=\"...\">` set\n\n**Fix**: collapse nested `\u003Cmain>`s (keep one, demote others to `\u003Cdiv>`); promote section\ntitles to headings with `font-family: inherit; margin-top: 0;` to preserve rendering; fix\nheading gaps; set decorative `alt=\"\"`; add `lang`.\n\n### 1.6 ARIA\n\n**Check & fix**:\n- Icon-only buttons (hamburger, theme toggle, close, search) → `aria-label`\n- Disclosure triggers (menus, accordions, collapsibles) → `aria-expanded` (with JS toggle\n  if needed)\n- Form errors → `aria-invalid` + `aria-describedby` linking to the message\n- Decorative SVGs\u002Femojis next to text → `aria-hidden=\"true\"`\n- Remove redundant ARIA (`\u003Cbutton role=\"button\">`, `\u003Cnav role=\"navigation\">`)\n\n### 1.7 SPA route-change focus (if applicable)\n\n**Check**: after client-side navigation, does focus reset so the next Tab starts from the\ntop? Does scroll reset?\n\n**Fix**: in the route-change\u002Fscroll-restoration hook, scroll to top and blur\n`document.activeElement` (when it's an HTMLElement other than `body`) on pathname change.\n\n### 1.8 Overflow-hidden focus clipping\n\n**Check**: parents with `overflow: hidden` (cards, pills, button groups) containing\nfocusable children — the parent clips an outline that extends beyond its bounds.\n\n**Fix**:\n- **Pill \u002F small element**: negative offset so the ring draws inside — `outline-offset: -2px`\n- **Card \u002F large target**: move the ring to the parent and suppress the inner one:\n  ```css\n  .card:has(a:focus-visible) {\n    outline: var(--focus-ring-width) solid var(--focus-ring-color);\n    outline-offset: var(--focus-ring-offset);\n  }\n  .card a:focus-visible { outline: none; }\n  ```\n  Use `:has(:focus-visible)`, not `:focus-within` — the latter triggers on mouse focus.\n\n## Phase 2 — Verify\n\n**Keyboard walkthrough** (repeat on every major route):\n1. Load the page, press Tab — first stop must be the skip link.\n2. Continue: skip-link → logo → nav → main CTAs → cards → footer links. Nothing silently\n   skipped; no focus trap (except modals with proper escape handling).\n3. Every focused element shows a clearly visible ring.\n4. Toggle dark mode, tab again — ring switches color and stays visible.\n5. Route changes reset focus to the top (next Tab hits skip-link again).\n\n**Forms**: tab into every input (indicator visible), Enter submits, error states expose\n`aria-invalid` + linked messages.\n\n**Automated smoke test**: run axe DevTools or Lighthouse a11y. Treat the score as a\nregression catch, not a substitute for the manual walkthrough.\n\n## Report\n\n```\n## Accessibility Audit Report — [Page\u002FProject]\n\nFocus System     [PASS \u002F BUILT \u002F NEEDS WORK]\nSkip Link        [PASS \u002F ADDED \u002F MISSING]\nKeyboard Nav     [score \u002F10] + findings\nSemantic HTML    [score \u002F10] + findings\nARIA             [score \u002F10] + findings\nSPA Focus Reset  [PASS \u002F FIXED \u002F N\u002FA]\n\n### Changes made\n- [files modified\u002Fcreated, one line each]\n\n### Still needs human attention\n- [manual testing, content decisions, visual review]\n\n### Conventions to document\n- [rules for AGENTS.md \u002F CLAUDE.md so future contributors maintain these patterns]\n```\n\n## Notes & edge cases\n\n- **Tailwind**: check for `outline-none` in the base layer; replace with\n  `focus-visible:ring-*` utilities tied to the token.\n- **Component libraries (Radix, Headless UI, shadcn)**: they handle ARIA internally — audit\n  the rendered DOM, not the source.\n- **CSS-in-JS**: focus resets may hide in `createGlobalStyle` or theme objects — search all\n  style definitions for `outline`.\n- **Next.js App Router**: route-change focus reset lives in a client component wrapping\n  `usePathname()`; the skip-link target goes on `\u003Cmain>` in `app\u002Flayout.tsx`.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fa11y-page-audit",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 a11y-page-audit",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill a11y-page-audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill a11y-page-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fa11y-page-audit\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",[],[]]