菜单
Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | poocommerce-copy-guidelines |
| description | Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages. |
This skill provides guidelines for writing user-facing copy in PooCommerce, including UI text, labels, buttons, messages, and documentation.
Follow these guidelines when writing any user-facing text:
Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
Run tests, linting, and quality checks for PooCommerce development. Use when running tests, fixing code style, or following the development workflow.
Setup and develop the PooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.
Commit uncommitted changes with well-crafted messages following PooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".
Create a high-quality draft PR for the current branch. Use when the user says "create a PR", "draft PR", "open a PR", "make a PR", "push and create PR", or "submit PR".
