[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C225595ZG6MPCRGKA7FSNZ":3,"skill-same:01M6C225595ZG6MPCRGKA7FSNZ":80},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6C225595ZG6MPCRGKA7FSNZ","wp-plugin-directory-guidelines",null,"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.","gambitph\u002FCimo","gambitph","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3227089?v=4","01M6C1ZD8129MTRC23K53VJ45E","Gambit Technologies","01M6C1ZDCJPEHP3CKCWNG7HDVV",2,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"directory","plugin","guidelines","wp plugin directory guidelines","wordpress","license","plugins","compliance","why","php","Rules","question","user","use","2026-11-10 10:12:30",false,"---\nname: wp-plugin-directory-guidelines\ndescription: \"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.\"\ncompatibility: \"Targets WordPress 7.0+ (PHP 7.4.0+).\"\n---\n\n## Overview\n\nAuthoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming\u002Ftrademark rules, trialware restrictions, and all other submission requirements.\n\n## When to use\n\nUse this skill when you need to:\n- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines\n- Check GPL license compatibility for a plugin or its bundled libraries\n- Verify license headers in plugin files\n- Identify common guideline violations before submission\n- Answer questions about what is or is not allowed on WordPress.org\n- Evaluate premium\u002Fupsell flows, license checks, or freemium positioning\n- Review \"teaser\" or \"preview\" UI for trialware violations\n\n## Inputs required\n\n- Plugin source code (or specific files to review)\n- Optional: plugin readme and plugin header metadata for naming and license checks\n\n## Procedure\n\n1. Check the plugin's license header against the **Valid License Headers** section below.\n2. Walk through the **18 Guidelines** checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.\n3. Confirm trialware\u002Ffreemium compliance using the checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md) (Guideline 5 section).\n4. For bundled third-party code, verify license compatibility against **GPL-Compatible Licenses (Quick)** below.\n5. Flag matches from **Common GPL Violations (Quick)** below.\n6. For edge cases, consult the detailed references and the [GNU GPL FAQ](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-faq.html).\n\n## 18-Guideline Review Checklist\n\nUse the detailed, per-guideline checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md). Load this reference file only when a full guideline audit is requested.\n\n## GPL Compliance (Guideline 1 in Detail)\n\nUse [gpl-compliance.md](references\u002Fgpl-compliance.md) for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.\n\n### Verification (Licensing)\n\n- Every licensing-related issue must cite **Guideline 1** and include the file path and exact license string.\n- Confirm compatibility claims against **GPL-Compatible Licenses (Quick)** and escalate ambiguous licenses.\n\n### Failure modes (Licensing)\n\n- If a license is not clearly GPL-compatible, do not guess. Check the [GNU license list](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Flicense-list.html).\n- For dual-license packages, verify both licenses and redistribution terms.\n\n### Quick Reference: WordPress GPL Requirements\n\n- WordPress is **GPLv2 or later**.\n- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).\n- Include a valid `License:` header and `License URI:` in the main plugin file.\n- Do not add restrictions that conflict with GPL freedoms.\n\n### Valid License Headers\n\n## GPL Versions Summary\n\n| Version | Year | Key Addition |\n|---------|------|--------------|\n| GPLv1 | 1989 | Base copyleft: share-alike for modifications |\n| GPLv2 | 1991 | \"Liberty or death\" clause (Section 7), clearer distribution terms |\n| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |\n\nWordPress uses **GPLv2 or later**, meaning plugins can use GPLv2, GPLv3, or \"GPLv2 or later\".\n\nFor full license texts, see:\n- [GNU General Public License v1](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-1.0.html)\n- [GNU General Public License v2](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html)\n- [GNU General Public License v3](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html)\n\n## License Compliance Checklist\n\nWhen reviewing a plugin, verify:\n\n- [ ] Main plugin file has a valid `License:` header (e.g., `GPL-2.0-or-later`, `GPL-2.0+`, `GPLv2 or later`)\n- [ ] Main plugin file has a `License URI:` header pointing to the GPL text\n- [ ] If bundled libraries exist, each has a GPL-compatible license\n- [ ] No \"split licensing\" (e.g., code GPL but premium features proprietary)\n- [ ] No additional restrictions beyond what GPL allows\n- [ ] No clauses restricting commercial use, modification, or redistribution\n- [ ] No obfuscated code (violates the spirit of source code availability)\n\n## Valid License Headers for WordPress Plugins\n\n```\nLicense: GPL-2.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n```text\nLicense: GPL-3.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html\n```\n\n```text\nLicense: GPLv2 or later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n### GPL-Compatible Licenses (Quick)\n\n- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.\n- Commonly accepted permissive families: MIT\u002FExpat, BSD, ISC, zlib, Boost.\n- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).\n- For full accepted and rejected identifiers, use [gpl-compliance.md](references\u002Fgpl-compliance.md).\n\n### Common GPL Violations (Quick)\n\n- Split licensing that restricts distributed code.\n- Obfuscated or non-corresponding source distribution.\n- Restrictive clauses (non-commercial, no-resale, forced backlink).\n- Bundling GPL-incompatible libraries or assets.\n\n## Plugin Naming Rules (Guideline 17)\n\nUse [naming-rules.md](references\u002Fnaming-rules.md) for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.\n\n### Naming Checklist (Quick)\n\n- Name is not a placeholder and has at least 5 alphanumeric characters.\n- Header name and readme name match.\n- Name is specific and function-related; avoid keyword stuffing.\n- Trademark\u002Fproject names appear only after connectors like `for`, `with`, `using`, `and`.\n- No banned\u002Fdiscouraged terms or trademark portmanteaus.\n- Slug is lowercase, hyphenated, \u003C= 50 chars, and avoids blocked terms.\n","## Overview\n\nAuthoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming\u002Ftrademark rules, trialware restrictions, and all other submission requirements.\n\n## When to use\n\nUse this skill when you need to:\n- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines\n- Check GPL license compatibility for a plugin or its bundled libraries\n- Verify license headers in plugin files\n- Identify common guideline violations before submission\n- Answer questions about what is or is not allowed on WordPress.org\n- Evaluate premium\u002Fupsell flows, license checks, or freemium positioning\n- Review \"teaser\" or \"preview\" UI for trialware violations\n\n## Inputs required\n\n- Plugin source code (or specific files to review)\n- Optional: plugin readme and plugin header metadata for naming and license checks\n\n## Procedure\n\n1. Check the plugin's license header against the **Valid License Headers** section below.\n2. Walk through the **18 Guidelines** checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.\n3. Confirm trialware\u002Ffreemium compliance using the checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md) (Guideline 5 section).\n4. For bundled third-party code, verify license compatibility against **GPL-Compatible Licenses (Quick)** below.\n5. Flag matches from **Common GPL Violations (Quick)** below.\n6. For edge cases, consult the detailed references and the [GNU GPL FAQ](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-faq.html).\n\n## 18-Guideline Review Checklist\n\nUse the detailed, per-guideline checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md). Load this reference file only when a full guideline audit is requested.\n\n## GPL Compliance (Guideline 1 in Detail)\n\nUse [gpl-compliance.md](references\u002Fgpl-compliance.md) for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.\n\n### Verification (Licensing)\n\n- Every licensing-related issue must cite **Guideline 1** and include the file path and exact license string.\n- Confirm compatibility claims against **GPL-Compatible Licenses (Quick)** and escalate ambiguous licenses.\n\n### Failure modes (Licensing)\n\n- If a license is not clearly GPL-compatible, do not guess. Check the [GNU license list](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Flicense-list.html).\n- For dual-license packages, verify both licenses and redistribution terms.\n\n### Quick Reference: WordPress GPL Requirements\n\n- WordPress is **GPLv2 or later**.\n- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).\n- Include a valid `License:` header and `License URI:` in the main plugin file.\n- Do not add restrictions that conflict with GPL freedoms.\n\n### Valid License Headers\n\n## GPL Versions Summary\n\n| Version | Year | Key Addition |\n|---------|------|--------------|\n| GPLv1 | 1989 | Base copyleft: share-alike for modifications |\n| GPLv2 | 1991 | \"Liberty or death\" clause (Section 7), clearer distribution terms |\n| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |\n\nWordPress uses **GPLv2 or later**, meaning plugins can use GPLv2, GPLv3, or \"GPLv2 or later\".\n\nFor full license texts, see:\n- [GNU General Public License v1](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-1.0.html)\n- [GNU General Public License v2](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html)\n- [GNU General Public License v3](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html)\n\n## License Compliance Checklist\n\nWhen reviewing a plugin, verify:\n\n- [ ] Main plugin file has a valid `License:` header (e.g., `GPL-2.0-or-later`, `GPL-2.0+`, `GPLv2 or later`)\n- [ ] Main plugin file has a `License URI:` header pointing to the GPL text\n- [ ] If bundled libraries exist, each has a GPL-compatible license\n- [ ] No \"split licensing\" (e.g., code GPL but premium features proprietary)\n- [ ] No additional restrictions beyond what GPL allows\n- [ ] No clauses restricting commercial use, modification, or redistribution\n- [ ] No obfuscated code (violates the spirit of source code availability)\n\n## Valid License Headers for WordPress Plugins\n\n```\nLicense: GPL-2.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n```text\nLicense: GPL-3.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html\n```\n\n```text\nLicense: GPLv2 or later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n### GPL-Compatible Licenses (Quick)\n\n- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.\n- Commonly accepted permissive families: MIT\u002FExpat, BSD, ISC, zlib, Boost.\n- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).\n- For full accepted and rejected identifiers, use [gpl-compliance.md](references\u002Fgpl-compliance.md).\n\n### Common GPL Violations (Quick)\n\n- Split licensing that restricts distributed code.\n- Obfuscated or non-corresponding source distribution.\n- Restrictive clauses (non-commercial, no-resale, forced backlink).\n- Bundling GPL-incompatible libraries or assets.\n\n## Plugin Naming Rules (Guideline 17)\n\nUse [naming-rules.md](references\u002Fnaming-rules.md) for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.\n\n### Naming Checklist (Quick)\n\n- Name is not a placeholder and has at least 5 alphanumeric characters.\n- Header name and readme name match.\n- Name is specific and function-related; avoid keyword stuffing.\n- Trademark\u002Fproject names appear only after connectors like `for`, `with`, `using`, `and`.\n- No banned\u002Fdiscouraged terms or trademark portmanteaus.\n- Slug is lowercase, hyphenated, \u003C= 50 chars, and avoids blocked terms.\n",{"name":5,"description":7,"compatibility":43},"Targets WordPress 7.0+ (PHP 7.4.0+).","develop","647b3a86ad96843d26f677d200372b67b7336254",".cursor\u002Fskills\u002Fwp-plugin-directory-guidelines",0,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo","https:\u002F\u002Fgithub.com\u002Fgambitph","https:\u002F\u002Fwpstackable.com","2026-10-15 14:34:26",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add gambitph\u002FCimo --skill wp-plugin-directory-guidelines",{"tool":58,"command":59},"bunx","bunx skills add gambitph\u002FCimo --skill wp-plugin-directory-guidelines",{"tool":61,"command":62},"pnpm","pnpm dlx skills add gambitph\u002FCimo --skill wp-plugin-directory-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002FSKILL.md",true,[66,72,76],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgpl-compliance.md","REFERENCE","参考文档",10342,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fgpl-compliance.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fguideline-review-checklist.md",25561,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fguideline-review-checklist.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fnaming-rules.md",7003,"https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fnaming-rules.md",[81,100,128,145,164,189],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":38},"01M6C22DH5PD92NQAX0Y2X0YA6","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\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[96,97,37,98,99],"writing for agents","writing","editing","documents",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":112,"publishedAt":38},"01M6C22APBD07T1MBH301FJKA6","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\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-rest-api\u002FSKILL.md",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[113,114,115,116,117,37,118,119,120,33,121,122,123,124,125,126,28,127],"wp rest api","REST","api","controller","schema","node","filesystem","shaping","Bash","Meta","validation","authentication","debugging","workflows","cli",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":38},"01M6C228355FYPDSH157J7962Z","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\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-project-triage\u002FSKILL.md",[],[135,136,137,119,138,121,33,139,140,141,142,143,25,126,28,127,118,37,144],"wp project triage","triage","repository","Guardrails","json","site","version","report","core","guide",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":38},"01M6C221V1PYQWWN2CVKSDDHC9","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\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-plugin-development\u002FSKILL.md",[151],{"categoryNo":107,"categoryName":108,"taxonomyType":90,"taxonomyTypeDesc":91},[153,154,25,37,155,156,121,127,119,115,157,158,159,160,161,126,162,28,118,163],"wp plugin development","development","packaging","settings","admin","capabilities","release","tasks","architecture","storage","uninstall",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":174,"publishedAt":38},"01M6C21YFXNYHM5B9ZN6JGCAJW","wp-performance","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.","https:\u002F\u002Fgithub.com\u002Fgambitph\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-performance\u002FSKILL.md",[170,171],{"categoryNo":107,"categoryName":108,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":172,"categoryName":173,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[175,176,177,178,179,180,181,28,182,127,183,184,37,185,186,33,187,115,114,188],"wp performance","performance","database","verification","doctor","monitor","http","safe","server","backend","profile","profiling","cron","Optimization",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":201,"publishedAt":38},"01M6C21VGHXMBDNDRZJGDW63CE","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\u002FCimo\u002Fblob\u002Fdevelop\u002F.cursor\u002Fskills\u002Fwp-patterns\u002FSKILL.md",[195,198],{"categoryNo":196,"categoryName":197,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[202,203,204,205,37,206,207,208,139,209,33,210,211,212,28,213],"wp patterns","syntax","auto","html","quality","page","template","correct","file","generate","accessibility","design"]