[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AZ4ZQHTNWFRZVYHKQFP08":3,"skill-same:01M71AZ4ZQHTNWFRZVYHKQFP08":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf",null,"Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"web","perf","web perf","knowledge","when","vitals","re","render","resources","layout","caching","optimize","never","MCP","chrome devtools","devtools","qa","issues","documentation","performance","2026-11-10 10:12:30",false,"---\nname: web-perf\ndescription: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.\nmetadata:\n  vendored: In-tree copy so \u002Fqa-full Step 6 and \u002Fdaily-qa never depend on an external skill. If an upstream source is identified, record it here and re-sync.\n---\n\n# Web Performance Audit\n\nYour knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. **Prefer retrieval over pre-training** when citing specific numbers or recommendations.\n\n## Retrieval Sources\n\n| Source | How to retrieve | Use for |\n|--------|----------------|---------|\n| web.dev | `https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals` | Core Web Vitals thresholds, definitions |\n| Chrome DevTools docs | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fdevtools\u002Fperformance` | Tooling APIs, trace analysis |\n| Lighthouse scoring | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Flighthouse\u002Fperformance\u002Fperformance-scoring` | Score weights, metric thresholds |\n\n## FIRST: Verify MCP Tools Available\n\n**Run this before starting.** Try calling `navigate_page` or `performance_start_trace`. If unavailable, STOP—the chrome-devtools MCP server isn't configured.\n\nAsk the user to add this to their MCP config:\n\n```json\n\"chrome-devtools\": {\n  \"type\": \"local\",\n  \"command\": [\"npx\", \"-y\", \"chrome-devtools-mcp@latest\"]\n}\n```\n\n## Key Guidelines\n\n- **Be assertive**: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.\n- **Verify before recommending**: Confirm something is unused before suggesting removal.\n- **Quantify impact**: Use estimated savings from insights. Don't prioritize changes with 0ms impact.\n- **Skip non-issues**: If render-blocking resources have 0ms estimated impact, note but don't recommend action.\n- **Be specific**: Say \"compress hero.png (450KB) to WebP\" not \"optimize images\".\n- **Prioritize ruthlessly**: A site with 200ms LCP and 0 CLS is already excellent—say so.\n\n## Quick Reference\n\n| Task | Tool Call |\n|------|-----------|\n| Load page | `navigate_page(url: \"...\")` |\n| Start trace | `performance_start_trace(autoStop: true, reload: true)` |\n| Analyze insight | `performance_analyze_insight(insightSetId: \"...\", insightName: \"...\")` |\n| List requests | `list_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", ...])` |\n| Request details | `get_network_request(reqid: \u003Cid>)` |\n| A11y snapshot | `take_snapshot(verbose: true)` |\n\n## Workflow\n\nCopy this checklist to track progress:\n\n```\nAudit Progress:\n- [ ] Phase 1: Performance trace (navigate + record)\n- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)\n- [ ] Phase 3: Network analysis\n- [ ] Phase 4: Accessibility snapshot\n- [ ] Phase 5: Codebase analysis (skip if third-party site)\n```\n\n### Phase 1: Performance Trace\n\n1. Navigate to the target URL:\n   ```\n   navigate_page(url: \"\u003Ctarget-url>\")\n   ```\n\n2. Start a performance trace with reload to capture cold-load metrics:\n   ```\n   performance_start_trace(autoStop: true, reload: true)\n   ```\n\n3. Wait for trace completion, then retrieve results.\n\n**Troubleshooting:**\n- If trace returns empty or fails, verify the page loaded correctly with `navigate_page` first\n- If insight names don't match, inspect the trace response to list available insights\n\n### Phase 2: Core Web Vitals Analysis\n\nUse `performance_analyze_insight` to extract key metrics.\n\n**Note:** Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the `insightSetId` from the trace response to discover available insights.\n\nCommon insight names:\n\n| Metric | Insight Name | What to Look For |\n|--------|--------------|------------------|\n| LCP | `LCPBreakdown` | Time to largest contentful paint; breakdown of TTFB, resource load, render delay |\n| CLS | `CLSCulprits` | Elements causing layout shifts (images without dimensions, injected content, font swaps) |\n| Render Blocking | `RenderBlocking` | CSS\u002FJS blocking first paint |\n| Document Latency | `DocumentLatency` | Server response time issues |\n| Network Dependencies | `NetworkRequestsDepGraph` | Request chains delaying critical resources |\n\nExample:\n```\nperformance_analyze_insight(insightSetId: \"\u003Cid-from-trace>\", insightName: \"LCPBreakdown\")\n```\n\n**Key thresholds (good\u002Fneeds-improvement\u002Fpoor):**\n- TTFB: \u003C 800ms \u002F \u003C 1.8s \u002F > 1.8s\n- FCP: \u003C 1.8s \u002F \u003C 3s \u002F > 3s\n- LCP: \u003C 2.5s \u002F \u003C 4s \u002F > 4s\n- INP: \u003C 200ms \u002F \u003C 500ms \u002F > 500ms\n- TBT: \u003C 200ms \u002F \u003C 600ms \u002F > 600ms\n- CLS: \u003C 0.1 \u002F \u003C 0.25 \u002F > 0.25\n- Speed Index: \u003C 3.4s \u002F \u003C 5.8s \u002F > 5.8s\n\n### Phase 3: Network Analysis\n\nList all network requests to identify optimization opportunities:\n```\nlist_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", \"Document\", \"Font\", \"Image\"])\n```\n\n**Look for:**\n\n1. **Render-blocking resources**: JS\u002FCSS in `\u003Chead>` without `async`\u002F`defer`\u002F`media` attributes\n2. **Network chains**: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)\n3. **Missing preloads**: Critical resources (fonts, hero images, key scripts) not preloaded\n4. **Caching issues**: Missing or weak `Cache-Control`, `ETag`, or `Last-Modified` headers\n5. **Large payloads**: Uncompressed or oversized JS\u002FCSS bundles\n6. **Unused preconnects**: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.\n\nFor detailed request info:\n```\nget_network_request(reqid: \u003Cid>)\n```\n\n### Phase 4: Accessibility Snapshot\n\nTake an accessibility tree snapshot:\n```\ntake_snapshot(verbose: true)\n```\n\n**Flag high-level gaps:**\n- Missing or duplicate ARIA IDs\n- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)\n- Focus traps or missing focus indicators\n- Interactive elements without accessible names\n\n## Phase 5: Codebase Analysis\n\n**Skip if auditing a third-party site without codebase access.**\n\nAnalyze the codebase to understand where improvements can be made.\n\n### Detect Framework & Bundler\n\nSearch for configuration files to identify the stack:\n\n| Tool | Config Files |\n|------|--------------|\n| Webpack | `webpack.config.js`, `webpack.*.js` |\n| Vite | `vite.config.js`, `vite.config.ts` |\n| Rollup | `rollup.config.js`, `rollup.config.mjs` |\n| esbuild | `esbuild.config.js`, build scripts with `esbuild` |\n| Parcel | `.parcelrc`, `package.json` (parcel field) |\n| Next.js | `next.config.js`, `next.config.mjs` |\n| Nuxt | `nuxt.config.js`, `nuxt.config.ts` |\n| SvelteKit | `svelte.config.js` |\n| Astro | `astro.config.mjs` |\n\nAlso check `package.json` for framework dependencies and build scripts.\n\n### Tree-Shaking & Dead Code\n\n- **Webpack**: Check for `mode: 'production'`, `sideEffects` in package.json, `usedExports` optimization\n- **Vite\u002FRollup**: Tree-shaking enabled by default; check for `treeshake` options\n- **Look for**: Barrel files (`index.js` re-exports), large utility libraries imported wholesale (lodash, moment)\n\n### Unused JS\u002FCSS\n\n- Check for CSS-in-JS vs. static CSS extraction\n- Look for PurgeCSS\u002FUnCSS configuration (Tailwind's `content` config)\n- Identify dynamic imports vs. eager loading\n\n### Polyfills\n\n- Check for `@babel\u002Fpreset-env` targets and `useBuiltIns` setting\n- Look for `core-js` imports (often oversized)\n- Check `browserslist` config for overly broad targeting\n\n### Compression & Minification\n\n- Check for `terser`, `esbuild`, or `swc` minification\n- Look for gzip\u002Fbrotli compression in build output or server config\n- Check for source maps in production builds (should be external or disabled)\n\n## Output Format\n\nPresent findings as:\n\n1. **Core Web Vitals Summary** - Table with metric, value, and rating (good\u002Fneeds-improvement\u002Fpoor)\n2. **Top Issues** - Prioritized list of problems with estimated impact (high\u002Fmedium\u002Flow)\n3. **Recommendations** - Specific, actionable fixes with code snippets or config changes\n4. **Codebase Findings** - Framework\u002Fbundler detected, optimization opportunities (omit if no codebase access)\n","# Web Performance Audit\n\nYour knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. **Prefer retrieval over pre-training** when citing specific numbers or recommendations.\n\n## Retrieval Sources\n\n| Source | How to retrieve | Use for |\n|--------|----------------|---------|\n| web.dev | `https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals` | Core Web Vitals thresholds, definitions |\n| Chrome DevTools docs | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fdevtools\u002Fperformance` | Tooling APIs, trace analysis |\n| Lighthouse scoring | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Flighthouse\u002Fperformance\u002Fperformance-scoring` | Score weights, metric thresholds |\n\n## FIRST: Verify MCP Tools Available\n\n**Run this before starting.** Try calling `navigate_page` or `performance_start_trace`. If unavailable, STOP—the chrome-devtools MCP server isn't configured.\n\nAsk the user to add this to their MCP config:\n\n```json\n\"chrome-devtools\": {\n  \"type\": \"local\",\n  \"command\": [\"npx\", \"-y\", \"chrome-devtools-mcp@latest\"]\n}\n```\n\n## Key Guidelines\n\n- **Be assertive**: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.\n- **Verify before recommending**: Confirm something is unused before suggesting removal.\n- **Quantify impact**: Use estimated savings from insights. Don't prioritize changes with 0ms impact.\n- **Skip non-issues**: If render-blocking resources have 0ms estimated impact, note but don't recommend action.\n- **Be specific**: Say \"compress hero.png (450KB) to WebP\" not \"optimize images\".\n- **Prioritize ruthlessly**: A site with 200ms LCP and 0 CLS is already excellent—say so.\n\n## Quick Reference\n\n| Task | Tool Call |\n|------|-----------|\n| Load page | `navigate_page(url: \"...\")` |\n| Start trace | `performance_start_trace(autoStop: true, reload: true)` |\n| Analyze insight | `performance_analyze_insight(insightSetId: \"...\", insightName: \"...\")` |\n| List requests | `list_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", ...])` |\n| Request details | `get_network_request(reqid: \u003Cid>)` |\n| A11y snapshot | `take_snapshot(verbose: true)` |\n\n## Workflow\n\nCopy this checklist to track progress:\n\n```\nAudit Progress:\n- [ ] Phase 1: Performance trace (navigate + record)\n- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)\n- [ ] Phase 3: Network analysis\n- [ ] Phase 4: Accessibility snapshot\n- [ ] Phase 5: Codebase analysis (skip if third-party site)\n```\n\n### Phase 1: Performance Trace\n\n1. Navigate to the target URL:\n   ```\n   navigate_page(url: \"\u003Ctarget-url>\")\n   ```\n\n2. Start a performance trace with reload to capture cold-load metrics:\n   ```\n   performance_start_trace(autoStop: true, reload: true)\n   ```\n\n3. Wait for trace completion, then retrieve results.\n\n**Troubleshooting:**\n- If trace returns empty or fails, verify the page loaded correctly with `navigate_page` first\n- If insight names don't match, inspect the trace response to list available insights\n\n### Phase 2: Core Web Vitals Analysis\n\nUse `performance_analyze_insight` to extract key metrics.\n\n**Note:** Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the `insightSetId` from the trace response to discover available insights.\n\nCommon insight names:\n\n| Metric | Insight Name | What to Look For |\n|--------|--------------|------------------|\n| LCP | `LCPBreakdown` | Time to largest contentful paint; breakdown of TTFB, resource load, render delay |\n| CLS | `CLSCulprits` | Elements causing layout shifts (images without dimensions, injected content, font swaps) |\n| Render Blocking | `RenderBlocking` | CSS\u002FJS blocking first paint |\n| Document Latency | `DocumentLatency` | Server response time issues |\n| Network Dependencies | `NetworkRequestsDepGraph` | Request chains delaying critical resources |\n\nExample:\n```\nperformance_analyze_insight(insightSetId: \"\u003Cid-from-trace>\", insightName: \"LCPBreakdown\")\n```\n\n**Key thresholds (good\u002Fneeds-improvement\u002Fpoor):**\n- TTFB: \u003C 800ms \u002F \u003C 1.8s \u002F > 1.8s\n- FCP: \u003C 1.8s \u002F \u003C 3s \u002F > 3s\n- LCP: \u003C 2.5s \u002F \u003C 4s \u002F > 4s\n- INP: \u003C 200ms \u002F \u003C 500ms \u002F > 500ms\n- TBT: \u003C 200ms \u002F \u003C 600ms \u002F > 600ms\n- CLS: \u003C 0.1 \u002F \u003C 0.25 \u002F > 0.25\n- Speed Index: \u003C 3.4s \u002F \u003C 5.8s \u002F > 5.8s\n\n### Phase 3: Network Analysis\n\nList all network requests to identify optimization opportunities:\n```\nlist_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", \"Document\", \"Font\", \"Image\"])\n```\n\n**Look for:**\n\n1. **Render-blocking resources**: JS\u002FCSS in `\u003Chead>` without `async`\u002F`defer`\u002F`media` attributes\n2. **Network chains**: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)\n3. **Missing preloads**: Critical resources (fonts, hero images, key scripts) not preloaded\n4. **Caching issues**: Missing or weak `Cache-Control`, `ETag`, or `Last-Modified` headers\n5. **Large payloads**: Uncompressed or oversized JS\u002FCSS bundles\n6. **Unused preconnects**: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.\n\nFor detailed request info:\n```\nget_network_request(reqid: \u003Cid>)\n```\n\n### Phase 4: Accessibility Snapshot\n\nTake an accessibility tree snapshot:\n```\ntake_snapshot(verbose: true)\n```\n\n**Flag high-level gaps:**\n- Missing or duplicate ARIA IDs\n- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)\n- Focus traps or missing focus indicators\n- Interactive elements without accessible names\n\n## Phase 5: Codebase Analysis\n\n**Skip if auditing a third-party site without codebase access.**\n\nAnalyze the codebase to understand where improvements can be made.\n\n### Detect Framework & Bundler\n\nSearch for configuration files to identify the stack:\n\n| Tool | Config Files |\n|------|--------------|\n| Webpack | `webpack.config.js`, `webpack.*.js` |\n| Vite | `vite.config.js`, `vite.config.ts` |\n| Rollup | `rollup.config.js`, `rollup.config.mjs` |\n| esbuild | `esbuild.config.js`, build scripts with `esbuild` |\n| Parcel | `.parcelrc`, `package.json` (parcel field) |\n| Next.js | `next.config.js`, `next.config.mjs` |\n| Nuxt | `nuxt.config.js`, `nuxt.config.ts` |\n| SvelteKit | `svelte.config.js` |\n| Astro | `astro.config.mjs` |\n\nAlso check `package.json` for framework dependencies and build scripts.\n\n### Tree-Shaking & Dead Code\n\n- **Webpack**: Check for `mode: 'production'`, `sideEffects` in package.json, `usedExports` optimization\n- **Vite\u002FRollup**: Tree-shaking enabled by default; check for `treeshake` options\n- **Look for**: Barrel files (`index.js` re-exports), large utility libraries imported wholesale (lodash, moment)\n\n### Unused JS\u002FCSS\n\n- Check for CSS-in-JS vs. static CSS extraction\n- Look for PurgeCSS\u002FUnCSS configuration (Tailwind's `content` config)\n- Identify dynamic imports vs. eager loading\n\n### Polyfills\n\n- Check for `@babel\u002Fpreset-env` targets and `useBuiltIns` setting\n- Look for `core-js` imports (often oversized)\n- Check `browserslist` config for overly broad targeting\n\n### Compression & Minification\n\n- Check for `terser`, `esbuild`, or `swc` minification\n- Look for gzip\u002Fbrotli compression in build output or server config\n- Check for source maps in production builds (should be external or disabled)\n\n## Output Format\n\nPresent findings as:\n\n1. **Core Web Vitals Summary** - Table with metric, value, and rating (good\u002Fneeds-improvement\u002Fpoor)\n2. **Top Issues** - Prioritized list of problems with estimated impact (high\u002Fmedium\u002Flow)\n3. **Recommendations** - Specific, actionable fixes with code snippets or config changes\n4. **Codebase Findings** - Framework\u002Fbundler detected, optimization opportunities (omit if no codebase access)\n",{"name":5,"metadata":49,"description":7},{"vendored":50},"In-tree copy so \u002Fqa-full Step 6 and \u002Fdaily-qa never depend on an external skill. If an upstream source is identified, record it here and re-sync.","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","skills\u002Fweb-perf",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 15:29:19",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add ariadoss\u002Fsuperskills --skill web-perf",{"tool":67,"command":68},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill web-perf",{"tool":70,"command":71},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill web-perf","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",true,[],[76,102,127,146,162,178],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":44},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[78,86,28,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"download","user","transcripts","subtitles","use","transcribe","write","read","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[92,109,110,111,112,113,114,115,116,28,117,118,119,120,121,122,123,124,125,126],"plan","write plan","verification","dry","review","tasks","code","you","auto","eng","coverage","yagni","complete","section","for","test plan","target","as",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":44},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[129,134,135,136,137,138,139,90,140,141,142,111,143,28,144,145],"isolation","with","git","feature","plans","implementation","workspace","directory","work","git worktrees","selection","Safety",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":44},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[148,153,154,155,142,111,156,28,157,90,158,159,121,160,161],"output","commands","about","claims","assertions","claim","prs","evidence","running",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[169,170,171,172,28,173,90,174,175,176,177],"idea","validate","validate idea","test","business","before building","minimalist","framework","it",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":187,"publishedAt":44},"01M71AYVHKX89YAFQA2Y7S4ZRP","test-coverage","Finds complex business logic, edge cases, corner cases, and past regressions\nthat lack tests, then writes the missing unit tests (and integration\u002FE2E\ntests when the risk genuinely crosses a boundary) — enforcing Google's\nTesting on the Toilet best practices (real > fake > mock, don't mock types\nyou don't own, verify state not queries, avoid change-detector tests, DAMP\nover DRY in tests, limit mocks per test). Use when asked to \"add tests\",\n\"cover edge cases\", \"check test coverage\", \"write missing tests\", \"harden\nthe tests\", \"test this properly\", or \"make sure this is tested\".","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Ftest-coverage\u002FSKILL.md",[184],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[188,172,119,189,190,191,92,93,192,193,194,112,96,116,28,195,196,197,198,199],"test coverage","change","paths","edit","past","e2e tests","sure","toilet","testing","scope","types","unit"]