[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQJ5E89MS8C5K3GZTY4B48":3,"skill-same:01M7AQJ5E89MS8C5K3GZTY4B48":42},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":5,"forksCount":13,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":27,"install":28,"resources":41},"01M7AQJ5E89MS8C5K3GZTY4B48","web-performance-audit",null,"Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.","davidanthonyn\u002Fclaude-skills","davidanthonyn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55152980?v=4","01M7AJ4MY8S5C2RJCGX6626J0G","01M7AJ7JE1K98GRPH9Z57Z0R0W",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fweb-performance-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-performance-audit\ndescription: Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.\nlicense: MIT\n---\n\n# Web Performance Audit\n\nAudit web page performance using Chrome DevTools MCP tools. This skill focuses on Core Web Vitals, network optimization, and high-level accessibility gaps.\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\nAudit web page performance using Chrome DevTools MCP tools. This skill focuses on Core Web Vitals, network optimization, and high-level accessibility gaps.\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,"license":14,"description":7},"main","45d5ac830c3e238eeba6d0b4e6fd7cf6b56bf380","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn","2026-09-09 16:05:56",{"source":8,"skillName":5,"commands":29,"prompt":39,"zipAvailable":40},[30,33,36],{"tool":31,"command":32},"npx","npx skills add davidanthonyn\u002Fclaude-skills --skill web-performance-audit",{"tool":34,"command":35},"bunx","bunx skills add davidanthonyn\u002Fclaude-skills --skill web-performance-audit",{"tool":37,"command":38},"pnpm","pnpm dlx skills add davidanthonyn\u002Fclaude-skills --skill web-performance-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fweb-performance-audit\u002FSKILL.md",true,[],[43,50,58,65,72,81],{"skillNo":44,"name":45,"nameZh":6,"description":46,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":47,"categories":48,"keywords":49,"publishedAt":18},"01M7AQPHJF528A4MD52YZEZV3R","zustand-state-management","Production-tested setup for Zustand state management in React applications with TypeScript.\nThis skill provides comprehensive patterns for building scalable, type-safe global state.\n\nUse when: setting up global state in React, migrating from Redux or Context API, implementing\nstate persistence with localStorage, configuring TypeScript with Zustand, using slices pattern\nfor modular stores, adding devtools middleware for debugging, handling Next.js SSR hydration,\nor encountering hydration errors, TypeScript inference issues, or persist middleware problems.\n\nPrevents 5 documented issues: Next.js hydration mismatches, TypeScript double parentheses\nsyntax errors, persist middleware export errors, infinite render loops, and slices pattern\ntype inference failures.\n\nKeywords: zustand, state management, React state, TypeScript state, persist middleware,\ndevtools, slices pattern, global state, React hooks, create store, useBoundStore,\nStateCreator, hydration error, text content mismatch, infinite render, localStorage,\nsessionStorage, immer middleware, shallow equality, selector pattern, zustand v5","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzustand-state-management\u002FSKILL.md",[],[],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7AQP2XJRPNYEH323GJ81NN5","zetic-mlange","Help users integrate the ZETIC Melange (MLange) on-device AI SDK into Android (Kotlin\u002FJava) and iOS (Swift) mobile apps. Use this skill whenever the user mentions Zetic, MLange, Melange, ZeticMLangeModel, ZeticMLangeLLMModel, ZeticMLangeHFModel, on-device NPU inference for mobile, or deploying ML models to Android\u002FiOS with NPU acceleration. Also trigger when users ask about running LLMs on-device with GGUF quantization, mobile NPU model deployment, or converting PyTorch\u002FONNX models for mobile inference. Covers general model inference, LLM inference (streaming token generation), and HuggingFace model loading.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7AQNEJHD27NNF5PYQDSW8B9","youtube-downloader","Download videos, audio, playlists, and channels from YouTube and 1000+ websites using yt-dlp. Supports quality selection, format conversion, subtitle download, playlist filtering, metadata extraction, thumbnail download, and batch operations. Use when downloading YouTube videos in any quality (4K, 8K, HDR), extracting audio as MP3\u002FM4A\u002FFLAC, downloading entire playlists\u002Fchannels, getting subtitles in multiple languages, converting to specific formats, downloading live streams, archiving content, or batch processing multiple URLs. Optimized for reliability with automatic retries, rate limiting, and error handling.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7AQJQSD2H04EE2EPNAQ8A3M","wordpress-plugin-core","This skill provides comprehensive knowledge for WordPress plugin development, covering core patterns, security best practices, database interactions, hooks\u002Ffilters, Settings API, custom post types, REST API, and AJAX. This skill should be used when creating WordPress plugins, troubleshooting security issues, implementing custom post types\u002Ftaxonomies, building admin interfaces, or working with the WordPress database.\n\nUse when: Creating new WordPress plugins, implementing nonces\u002Fsanitization\u002Fescaping, working with $wpdb and prepared statements, building Settings API pages, registering custom post types or taxonomies, implementing REST API endpoints, handling AJAX requests, debugging plugin activation\u002Fdeactivation issues, preventing SQL injection\u002FXSS\u002FCSRF vulnerabilities.\n\nKeywords: wordpress plugin development, wordpress security, wordpress hooks, wordpress filters, wordpress database, wpdb prepare, sanitize_text_field, esc_html, wp_nonce, custom post type, register_post_type, settings api, rest api, admin-ajax, wordpress sql injection, wordpress xss, wordpress csrf, plugin header, activation hook, deactivation hook, wordpress coding standards, wordpress plugin architecture","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwordpress-plugin-core\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AQJ91T970QCFMN9R1EHZXV","webapp-testing","Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AQHTCD6M8NA95WXY3DE3W0","web-frameworks","Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined\u002Ffilled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fweb-frameworks\u002FSKILL.md",[],[]]