所有 Skills
找到 8442 个 Skills
Skills 列表
wp-plugin-directory-guidelines
Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware 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.
wordpress
steve-jobs-design-review
Review designs, products, and features with Steve Jobs'' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste", "saying no", or "is this good enough to ship". Also trigger when critiquing a UI, feature, or roadmap for focus and simplicity, cutting scope to the essential, or pressure-testing the whole experience from first run to daily use. Covers the simplicity audit, the no list, design-is-how-it-works, end-to-end ownership, demo culture, and a Jobs-style review protocol with binary verdicts. For visual design fundamentals, see refactoring-ui. For usability audits, see ux-heuristics. For detail polish, see microinteractions.
wondelaiworking-with-legacy-code
Safely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
wondelaiblueprint
当交付物为 WordPress Playground Blueprint JSON 或 Blueprint bundle（蓝图资源包）时使用，涵盖 Blueprint 文件的创建、编辑、评审、Schema 字段校验、步骤/资源选择以及调试等场景。如果仅需运行或分享 Playground 环境，请使用 wp-playground。
wordpresswp-interactivity-api
在构建或调试 WordPress Interactivity API 功能（包括 data-wp-* 指令、@wordpress/interactivity store/state/actions、区块 viewScriptModule 集成以及 wp_interactivity_*() 函数）时使用，涵盖性能优化、水合 (hydration) 和指令行为调试。
wordpresswpds
在利用WordPress设计系统（WPDS）及其组件、令牌、模式等构建UI时使用。
wordpresswp-phpstan
在WordPress项目（插件/主题/站点）中配置、运行或修复PHPStan静态分析时使用：phpstan.neon设置、基线、WordPress特定类型以及处理第三方插件类。
wordpresswp-abilities-api
适用于开发或使用 WordPress Abilities API（包含 `wp_register_ability`、`wp_register_ability_category`、`/wp-json/wp-abilities/v1/*`、`@wordpress/abilities`）的场景，涵盖 Abilities（能力）及分类定义、Meta 配置、REST 接口暴露以及客户端权限校验等操作。
wordpresswp-playground
用作 WordPress Playground 路由包装器，处理模糊的 Playground 工作、使用 @wp-playground/cli 的本地 CLI 运行、playground.wordpress.net 分享链接、浏览器预览、快照、挂载、版本切换和 Xdebug。对于 Blueprint JSON 编写或审查，请直接使用 blueprint 技能。
wordpress
chatgpt-app-builder
指导开发者创建和更新ChatGPT应用。 涵盖完整生命周期：根据UX指南构思创意、引导项目启动、实现工具/视图、调试、运行开发服务器、部署以及将应用连接到ChatGPT。 当用户想要创建或更新ChatGPT应用/MCP服务器，或使用Skybridge框架时使用。
alpic-ai
figma-use-figjam
This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
figma
workers-best-practices
审查并编写符合生产最佳实践的 Cloudflare Workers 代码。在编写新的 Worker、审查 Worker 代码、配置 wrangler.jsonc 或检查常见的 Worker 反模式（流处理、未处理的 Promise、全局状态、密钥、绑定、可观测性）时加载。倾向于从 Cloudflare 文档检索，而非依赖预训练知识。
cloudflarewp-wpcli-and-ops
当需要通过 WP-CLI (wp) 执行 WordPress 运维操作时使用：安全的 search-replace、数据库导出/导入、插件/主题/用户/内容管理、cron、缓存刷新、多站点以及使用 wp-cli.yml 进行脚本编写和自动化。
wordpresswp-project-triage
当你需要对WordPress仓库（插件/主题/区块主题/WP核心/Gutenberg/完整站点）进行确定性检查，包括工具链/测试/版本提示，并生成结构化JSON报告以指导工作流程和防护措施时使用。
wordpresswordpress-router
当用户询问关于 WordPress 代码库（插件、主题、块主题、Gutenberg 块、WP 核心检出）且你需要快速分类仓库并路由到正确的工作流/技能（块、theme.json、REST API、WP-CLI、性能、安全、测试、发布打包）时使用。
wordpress
linting-neostandard-eslint9
Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.
mcollina
asd-ste100
Use when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy.
danyuchninit
Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase. Use when setting up agent instructions or Claude configuration for a new repository, when an existing AGENTS.md is too long, generic, or stale, when agents repeatedly make avoidable mistakes, or when repository workflows have changed and the agent configuration needs pruning. Applies a discoverability filter—omitting anything Claude can learn from README, code, config, or directory structure—and a quality gate to verify each line remains accurate and operationally significant.
mcollinaoctocat
Use this skill whenever the prompt contains any `github.com` URL, even if the user only pastes a link and gives no GitHub-specific keywords. Handles git and GitHub operations using the gh CLI. Triggers include any GitHub link to an issue, pull request, commit, compare page, Actions run, release, discussion, or repository. Covers creating and reviewing PRs, watching CI checks, interactive rebasing, branch cleanup, submodule management, and repository archaeology with git log/blame/bisect.
mcollinawp-block-themes
用于开发WordPress区块主题：theme.json（全局设置/样式）、模板和模板部件、模式、样式变体以及站点编辑器故障排除（样式层级、覆盖、缓存）。
wordpresswp-performance
用于调查或改进WordPress性能（仅后端代理）：性能分析和测量（WP-CLI profile/doctor、Server-Timing、通过REST头部的Query Monitor）、数据库/查询优化、自动加载选项、对象缓存、cron、HTTP API调用以及安全验证。
wordpresswp-block-development
开发 WordPress (Gutenberg) 区块（Block）时使用：涵盖 block.json 元数据、register_block_type(_from_metadata)、属性与序列化（attributes/serialization）、supports 配置、动态渲染（render.php/render_callback）、版本废弃与迁移（deprecations/migrations）、viewScript 与 viewScriptModule 的对比，以及基于 @wordpress/scripts 和 @wordpress/create-block 的构建与测试工作流。
wordpresswp-rest-api
适用于构建、扩展或调试 WordPress REST API 端点/路由场景：包含 register_rest_route 的注册与使用、WP_REST_Controller 控制器类继承、Schema 及请求参数校验、permission_callback 与权限认证、响应数据格式化（response shaping）、register_rest_field/register_meta 扩展自定义字段，以及通过 show_in_rest 暴露自定义文章类型（CPT）或分类法（Taxonomy）。
wordpressoauth
Implements OAuth 2.0/2.1 authorization flows in Fastify applications — configures authorization code with PKCE, client credentials, device flow, refresh token rotation, JWT validation, and token introspection/revocation endpoints. Use when setting up authentication, authorization, login flows, access tokens, API security, or securing Fastify routes with OAuth; also applies when troubleshooting token validation errors, mismatched redirect URIs, CSRF issues, scope problems, or RFC 6749/6750/7636/8252/8628 compliance questions.
mcollina