[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SRJ36HWMTQ9ZMQ2RB008S":3,"skill-same:01M71SRJ36HWMTQ9ZMQ2RB008S":71},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M71SRJ36HWMTQ9ZMQ2RB008S","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.","sanurb\u002F.dotfiles","sanurb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60886336?v=4","01M71SKJS17F5YPRE27CVMEH1X","Santiago U","01M71SKJSTGEXEQ82HMAQP4ZAF",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\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],"perf","web","web perf","network","dependency","audit","layout","optimize","documentation","caching","when","MCP","knowledge","devtools","issues","render","performance","chrome devtools","vitals","resources","2026-11-10 13:02:02",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.\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,"description":7},"main","5acbba39180bbea80204d1a58db40ccbd813a13a","config\u002Fpi\u002Fagent\u002Fskills\u002Fweb-perf",0,"https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles","https:\u002F\u002Fgithub.com\u002Fsanurb","Building things","2026-11-12 05:25:20",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add sanurb\u002F.dotfiles --skill web-perf",{"tool":63,"command":64},"bunx","bunx skills add sanurb\u002F.dotfiles --skill web-perf",{"tool":66,"command":67},"pnpm","pnpm dlx skills add sanurb\u002F.dotfiles --skill web-perf","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fweb-perf\u002FSKILL.md",true,[],[72,97,125,152,169,193],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":86,"publishedAt":44},"01M71SS19VAM2YZ2SA7HD0PT2P","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[78,81],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,96],"writing great skills","writing","principles","for","editing","a skill","true","reference","make","vocabulary",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":44},"01M71SRXKJN6RYXPN9GFRVYSR3","write-discoverable-code","Rules for writing code that coding agents (and humans) can find and understand through\nplain-text search. Apply whenever writing or renaming code: functions, types, constants,\nfiles, error messages, doc comments.\n\nGrounded in measurement: agents navigate by plain-text search, not by AST or\nlanguage server, so every identifier is a search query and every search miss\ncosts wasted reads.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwrite-discoverable-code\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师",[107,108,109,110,111,112,113,114,90,115,116,117,118,119,88,120,121,122,123,124],"write discoverable code","code","discoverable code","write","measurement","error","types","error messages","search","messages","constants","plain-text","files","Rules","query","apply","comments","can",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":134,"publishedAt":44},"01M71SRT760335ES5WSEAAQDN2","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwrangler\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[127,135,136,36,137,138,139,140,141,142,143,144,145,90,146,147,148,149,150,151],"cloudflare","d1","workflows","cli","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":44},"01M71SRPHE452V400HD2EZC4XG","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[159,149,150,160,161,162,90,135,163,36,164,127,88,148,34,108,165,166,167,168],"workers best practices","observability","reviews","promises","worker","new","common","streaming","state","anti-patterns",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":44},"01M71SREWXFKFN6DM80YCCQZ46","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[171,176,177,178,179,180,181,93,182,183,184,185,124,186,187,188,189,190,191,192],"shared","as","chunk","time","session","decision","more","map","one","one at a time","agent session","work","plan","tracker","tickets","at","destination",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":202,"publishedAt":44},"01M71SRB1QH4KP19DWM87M42TS","turnstile-spin","Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com\u002Fturnstile\u002Fspin.","https:\u002F\u002Fgithub.com\u002Fsanurb\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fpi\u002Fagent\u002Fskills\u002Fturnstile-spin\u002FSKILL.md",[199],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[203,204,205,206,207,208,209,210,211,135,212,213,163,34,214,215,216,217,110,218],"turnstile spin","SET","app","bots","nextjs","project","end","up","fix","managed","frontend","api","create","astro","persist","snippets"]