[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RACN5F4BJYC0QX4MBFV0P":3,"skill-same:01M79RACN5F4BJYC0QX4MBFV0P":94},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79RACN5F4BJYC0QX4MBFV0P","wp-performance",null,"Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile\u002Fdoctor, Server-Timing, Query Monitor via REST headers), database\u002Fquery optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.","gambitph\u002FAhentic","gambitph","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3227089?v=4","01M6C1ZD8129MTRC23K53VJ45E","Gambit Technologies","01M79R7A85NS2N9JAK7AC0NE1X",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wp-performance\ndescription: \"Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile\u002Fdoctor, Server-Timing, Query Monitor via REST headers), database\u002Fquery optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.\"\ncompatibility: \"Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor\u002Fprofile) when available.\"\n---\n\n# WP Performance (backend-only)\n\n## When to use\n\nUse this skill when:\n\n- a WordPress site\u002Fpage\u002Fendpoint is slow (frontend TTFB, admin, REST, WP-Cron)\n- you need a profiling plan and tooling recommendations (WP-CLI profile\u002Fdoctor, Query Monitor, Xdebug\u002FXHProf, APMs)\n- you’re optimizing DB queries, autoloaded options, object caching, cron tasks, or remote HTTP calls\n\nThis skill assumes the agent cannot use a browser UI. Prefer WP-CLI, logs, and HTTP requests.\n\n## Inputs required\n\n- Environment and safety: dev\u002Fstaging\u002Fprod, any restrictions (no writes, no plugin installs).\n- How to target the install:\n  - WP root `--path=\u003Cpath>`\n  - (multisite\u002Fsite targeting) `--url=\u003Curl>`\n- The performance symptom and scope:\n  - which URL\u002FREST route\u002Fadmin screen\n  - when it happens (always vs sporadic; logged-in vs logged-out)\n\n## Procedure\n\n### 0) Guardrails: measure first, avoid risky ops\n\n1. Confirm whether you may run write operations (plugin installs, config changes, cache flush).\n2. Pick a reproducible target (URL or REST route) and capture a baseline:\n   - TTFB\u002Ftime with `curl` if possible\n   - WP-CLI profiling if available\n\nRead:\n- `references\u002Fmeasurement.md`\n\n### 1) Generate a backend-only performance report (deterministic)\n\nRun:\n\n- `node skills\u002Fwp-performance\u002Fscripts\u002Fperf_inspect.mjs --path=\u003Cpath> [--url=\u003Curl>]`\n\nThis detects:\n\n- WP-CLI availability and core version\n- whether `wp doctor` \u002F `wp profile` are available\n- autoloaded options size (if possible)\n- object-cache drop-in presence\n\n### 2) Fast wins: run diagnostics before deep profiling\n\nIf you have WP-CLI access, prefer:\n\n- `wp doctor check`\n\nIt catches common production foot-guns (autoload bloat, SAVEQUERIES\u002FWP_DEBUG, plugin counts, updates).\n\nRead:\n- `references\u002Fwp-cli-doctor.md`\n\n### 3) Deep profiling (no browser required)\n\nPreferred order:\n\n1. `wp profile stage` to see where time goes (bootstrap\u002Fmain_query\u002Ftemplate).\n2. `wp profile hook` (optionally with `--url=`) to find slow hooks\u002Fcallbacks.\n3. `wp profile eval` for targeted code paths.\n\nRead:\n- `references\u002Fwp-cli-profile.md`\n\n### 4) Query Monitor (backend-only usage)\n\nQuery Monitor is normally UI-driven, but it can be used headlessly via REST API response headers and `_envelope` responses:\n\n- Authenticate (nonce or Application Password).\n- Request REST responses and inspect headers (`x-qm-*`) and\u002For the `qm` property when using `?_envelope`.\n\nRead:\n- `references\u002Fquery-monitor-headless.md`\n\n### 5) Fix by category (choose the dominant bottleneck)\n\nUse the profile output to pick *one* primary bottleneck category:\n\n- **DB queries** → reduce query count, fix N+1 patterns, improve indexes, avoid expensive meta queries.\n  - `references\u002Fdatabase.md`\n- **Autoloaded options** → identify the biggest autoloaded options and stop autoloading large blobs.\n  - `references\u002Fautoload-options.md`\n- **Object cache misses** → introduce caching or fix cache key\u002Fgroup usage; add persistent object cache where appropriate.\n  - `references\u002Fobject-cache.md`\n- **Remote HTTP calls** → add timeouts, caching, batching; avoid calling remote APIs on every request.\n  - `references\u002Fhttp-api.md`\n- **Cron** → reduce due-now spikes, de-duplicate events, move heavy tasks out of request paths.\n  - `references\u002Fcron.md`\n\n### 6) Verify (repeat the same measurement)\n\n- Re-run the same `wp profile` \u002F `wp doctor` \u002F REST request.\n- Confirm the performance delta and that behavior is unchanged.\n- If the fix is risky, ship behind a feature flag or staged rollout when possible.\n\n## WordPress 6.9 performance improvements\n\nBe aware of these 6.9 changes when profiling:\n\n**On-demand CSS for classic themes:**\n- Classic themes now get on-demand CSS loading (previously only block themes had this).\n- Reduces CSS payload by 30-65% by only loading styles for blocks actually used on the page.\n- If you're profiling a classic theme, this should already be helping.\n\n**Block themes with no render-blocking resources:**\n- Block themes that don't define custom stylesheets (like Twenty Twenty-Three\u002FFour) can now load with zero render-blocking CSS.\n- Styles come from global styles (theme.json) and separate block styles, all inlined.\n- This significantly improves LCP (Largest Contentful Paint).\n\n**Inline CSS limit increased:**\n- The threshold for inlining small stylesheets has been raised, reducing render-blocking resources.\n\nReference: https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2025\u002F11\u002F18\u002Fwordpress-6-9-frontend-performance-field-guide\u002F\n\n## Verification\n\n- Baseline vs after numbers are captured (same environment, same URL\u002Froute).\n- `wp doctor check` is clean (or improved) when applicable.\n- No new PHP errors or warnings in logs.\n- No cache flush is required for correctness (cache flush should be last resort).\n\n## Failure modes \u002F debugging\n\n- “No change” after code changes:\n  - you measured a different URL\u002Fsite (`--url` mismatch), caches masked results, or opcode cache is stale\n- Profiling data is noisy:\n  - eliminate background tasks, test with warmed caches, run multiple samples\n- `SAVEQUERIES`\u002FQuery Monitor causes overhead:\n  - don’t run in production unless explicitly approved\n\n## Escalation\n\n- If this is production and you don’t have explicit approval, do not:\n  - install plugins, enable `SAVEQUERIES`, run load tests, or flush caches during traffic\n- If you need system-level profiling (APM, PHP profiler extensions), coordinate with ops\u002Fhosting.\n","# WP Performance (backend-only)\n\n## When to use\n\nUse this skill when:\n\n- a WordPress site\u002Fpage\u002Fendpoint is slow (frontend TTFB, admin, REST, WP-Cron)\n- you need a profiling plan and tooling recommendations (WP-CLI profile\u002Fdoctor, Query Monitor, Xdebug\u002FXHProf, APMs)\n- you’re optimizing DB queries, autoloaded options, object caching, cron tasks, or remote HTTP calls\n\nThis skill assumes the agent cannot use a browser UI. Prefer WP-CLI, logs, and HTTP requests.\n\n## Inputs required\n\n- Environment and safety: dev\u002Fstaging\u002Fprod, any restrictions (no writes, no plugin installs).\n- How to target the install:\n  - WP root `--path=\u003Cpath>`\n  - (multisite\u002Fsite targeting) `--url=\u003Curl>`\n- The performance symptom and scope:\n  - which URL\u002FREST route\u002Fadmin screen\n  - when it happens (always vs sporadic; logged-in vs logged-out)\n\n## Procedure\n\n### 0) Guardrails: measure first, avoid risky ops\n\n1. Confirm whether you may run write operations (plugin installs, config changes, cache flush).\n2. Pick a reproducible target (URL or REST route) and capture a baseline:\n   - TTFB\u002Ftime with `curl` if possible\n   - WP-CLI profiling if available\n\nRead:\n- `references\u002Fmeasurement.md`\n\n### 1) Generate a backend-only performance report (deterministic)\n\nRun:\n\n- `node skills\u002Fwp-performance\u002Fscripts\u002Fperf_inspect.mjs --path=\u003Cpath> [--url=\u003Curl>]`\n\nThis detects:\n\n- WP-CLI availability and core version\n- whether `wp doctor` \u002F `wp profile` are available\n- autoloaded options size (if possible)\n- object-cache drop-in presence\n\n### 2) Fast wins: run diagnostics before deep profiling\n\nIf you have WP-CLI access, prefer:\n\n- `wp doctor check`\n\nIt catches common production foot-guns (autoload bloat, SAVEQUERIES\u002FWP_DEBUG, plugin counts, updates).\n\nRead:\n- `references\u002Fwp-cli-doctor.md`\n\n### 3) Deep profiling (no browser required)\n\nPreferred order:\n\n1. `wp profile stage` to see where time goes (bootstrap\u002Fmain_query\u002Ftemplate).\n2. `wp profile hook` (optionally with `--url=`) to find slow hooks\u002Fcallbacks.\n3. `wp profile eval` for targeted code paths.\n\nRead:\n- `references\u002Fwp-cli-profile.md`\n\n### 4) Query Monitor (backend-only usage)\n\nQuery Monitor is normally UI-driven, but it can be used headlessly via REST API response headers and `_envelope` responses:\n\n- Authenticate (nonce or Application Password).\n- Request REST responses and inspect headers (`x-qm-*`) and\u002For the `qm` property when using `?_envelope`.\n\nRead:\n- `references\u002Fquery-monitor-headless.md`\n\n### 5) Fix by category (choose the dominant bottleneck)\n\nUse the profile output to pick *one* primary bottleneck category:\n\n- **DB queries** → reduce query count, fix N+1 patterns, improve indexes, avoid expensive meta queries.\n  - `references\u002Fdatabase.md`\n- **Autoloaded options** → identify the biggest autoloaded options and stop autoloading large blobs.\n  - `references\u002Fautoload-options.md`\n- **Object cache misses** → introduce caching or fix cache key\u002Fgroup usage; add persistent object cache where appropriate.\n  - `references\u002Fobject-cache.md`\n- **Remote HTTP calls** → add timeouts, caching, batching; avoid calling remote APIs on every request.\n  - `references\u002Fhttp-api.md`\n- **Cron** → reduce due-now spikes, de-duplicate events, move heavy tasks out of request paths.\n  - `references\u002Fcron.md`\n\n### 6) Verify (repeat the same measurement)\n\n- Re-run the same `wp profile` \u002F `wp doctor` \u002F REST request.\n- Confirm the performance delta and that behavior is unchanged.\n- If the fix is risky, ship behind a feature flag or staged rollout when possible.\n\n## WordPress 6.9 performance improvements\n\nBe aware of these 6.9 changes when profiling:\n\n**On-demand CSS for classic themes:**\n- Classic themes now get on-demand CSS loading (previously only block themes had this).\n- Reduces CSS payload by 30-65% by only loading styles for blocks actually used on the page.\n- If you're profiling a classic theme, this should already be helping.\n\n**Block themes with no render-blocking resources:**\n- Block themes that don't define custom stylesheets (like Twenty Twenty-Three\u002FFour) can now load with zero render-blocking CSS.\n- Styles come from global styles (theme.json) and separate block styles, all inlined.\n- This significantly improves LCP (Largest Contentful Paint).\n\n**Inline CSS limit increased:**\n- The threshold for inlining small stylesheets has been raised, reducing render-blocking resources.\n\nReference: https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2025\u002F11\u002F18\u002Fwordpress-6-9-frontend-performance-field-guide\u002F\n\n## Verification\n\n- Baseline vs after numbers are captured (same environment, same URL\u002Froute).\n- `wp doctor check` is clean (or improved) when applicable.\n- No new PHP errors or warnings in logs.\n- No cache flush is required for correctness (cache flush should be last resort).\n\n## Failure modes \u002F debugging\n\n- “No change” after code changes:\n  - you measured a different URL\u002Fsite (`--url` mismatch), caches masked results, or opcode cache is stale\n- Profiling data is noisy:\n  - eliminate background tasks, test with warmed caches, run multiple samples\n- `SAVEQUERIES`\u002FQuery Monitor causes overhead:\n  - don’t run in production unless explicitly approved\n\n## Escalation\n\n- If this is production and you don’t have explicit approval, do not:\n  - install plugins, enable `SAVEQUERIES`, run load tests, or flush caches during traffic\n- If you need system-level profiling (APM, PHP profiler extensions), coordinate with ops\u002Fhosting.\n",{"name":5,"description":7,"compatibility":24},"Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor\u002Fprofile) when available.","main","c4de8c3c2dcdca2892337cdc47c05dcb1cea8562",".cursor\u002Fskills\u002Fwp-performance","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic","https:\u002F\u002Fgithub.com\u002Fgambitph","https:\u002F\u002Fwpstackable.com","2026-08-15 14:40:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add gambitph\u002FAhentic --skill wp-performance",{"tool":38,"command":39},"bunx","bunx skills add gambitph\u002FAhentic --skill wp-performance",{"tool":41,"command":42},"pnpm","pnpm dlx skills add gambitph\u002FAhentic --skill wp-performance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fautoload-options.md","REFERENCE","参考文档",810,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fautoload-options.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcron.md",483,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fcron.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdatabase.md",619,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fdatabase.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fhttp-api.md",458,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fhttp-api.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fmeasurement.md",1037,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fmeasurement.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fobject-cache.md",756,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fobject-cache.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fquery-monitor-headless.md",1108,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fquery-monitor-headless.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fserver-timing.md",639,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fserver-timing.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fwp-cli-doctor.md",660,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fwp-cli-doctor.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fwp-cli-profile.md",858,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Freferences\u002Fwp-cli-profile.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fperf_inspect.mjs","SCRIPT","脚本",4630,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-performance\u002Fscripts\u002Fperf_inspect.mjs",[95,102,109,116,123,130],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79RB5GMQX62XBSR4XMJ3758","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"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":19},"01M79RB0ET331AVRW6W4JAW30C","wp-rest-api","Use when building, extending, or debugging WordPress REST API endpoints\u002Froutes: register_rest_route, WP_REST_Controller\u002Fcontroller classes, schema\u002Fargument validation, permission_callback\u002Fauthentication, response shaping, register_rest_field\u002Fregister_meta, or exposing CPTs\u002Ftaxonomies via show_in_rest.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-rest-api\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M79RAX0CGSMDWJ7F5DATG4WF","wp-project-triage","Use when you need a deterministic inspection of a WordPress repository (plugin\u002Ftheme\u002Fblock theme\u002FWP core\u002FGutenberg\u002Ffull site) including tooling\u002Ftests\u002Fversion hints, and a structured JSON report to guide workflows and guardrails.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-project-triage\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M79RAQ5Q24QC2W4M3XDM2195","wp-plugin-directory-guidelines","Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell\u002Ffreemium\u002Ftrialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M79RAJ56J66CKG54B0SBK8PX","wp-plugin-development","Use when developing WordPress plugins: architecture and hooks, activation\u002Fdeactivation\u002Funinstall, admin UI and Settings API, data storage, cron\u002Ftasks, security (nonces\u002Fcapabilities\u002Fsanitization\u002Fescaping), and release packaging.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-plugin-development\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M79RA667YDQ2NQWCYBVKTTKS","wp-patterns","Generate technically correct, design-distinctive WordPress block patterns. Use when creating block patterns, starter page patterns, template patterns, template part patterns, or improving pattern design quality. Covers pattern registration (PHP headers, auto\u002Fmanual), block markup syntax, theme.json design tokens, categories, template types, accessibility, and i18n\u002Fescaping.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FAhentic\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fwp-patterns\u002FSKILL.md",[],[]]