開発
#writing
woocommerce-backend-dev
Add or modify WooCommerce 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.**
DeepseekModel
キュレーション済みスキル
品質 優秀 · 90
v1.0.0
取得
https://deepseekmodel.com/api/download.php?id=woocommerce-woocommerce-ai-skills-woocommerce-backend-dev-skill-md&format=skill
ダウンロード .skill
標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能
.skill ファイルの system_prompt フィールドの実際の内容。
name woocommerce-backend-dev description Add or modify WooCommerce 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.** WooCommerce Backend Development This skill provides guidance for developing WooCommerce backend PHP code according to project standards and conventions. When to Use This Skill ALWAYS invoke this skill before: Writing new PHP unit tests ( *Test.php files) Creating new PHP classes Modifying existing backend PHP code Adding hooks or filters Instructions Follow WooCommerce project conventions when adding or modifying backend PHP code: Creating new code structures : See file-entities.md for conventions on creating classes and organizing files (but for new unit test files see unit-tests.md ). Naming conventions : See code-entities.md for naming methods, variables, and parameters Coding style : See coding-conventions.md for general coding standards and best practices Type annotations : See type-annotations.md for PHPStan-aware PHPDoc annotations Working with hooks : See hooks.md for hook callback conventions and documentation Dependency injection : See dependency-injection.md for DI container usage Data integrity : See data-integrity.md for ensuring data integrity when performing CRUD operations Writing tests : See unit-tests.md for unit testing conventions Key Principles Always follow WordPress Coding Standards Use class methods instead of standalone functions Place new internal classes in src/Internal/ by default Use PSR-4 autoloading with Automattic\WooCommerce namespace Write comprehensive unit tests for new functionality Run linting and tests before committing changes Version Information To determine the next WooCommerce version number for @since annotations: Read the $version property in includes/class-woocommerce.php on the trunk branch Remove the -dev suffix if present Example: If trunk shows 10.4.0-dev , use @since 10.4.0 Note: When reviewing PRs against trunk, the version in trunk is correct even if it seems "future" relative to released versions
このスキルを起動するキーワード。クリックでコピーできます。
このスキルにはトリガーワードがありません。
ダウンロードした .skill に含まれるフィールド。
| フィールド | 説明 |
|---|---|
| format | フォーマット識別子（skill/v1） |
| skill_id | スキル固有 ID |
| name | スキル名 |
| version | バージョン |
| description | 説明 |
| category | カテゴリ（配列） |
| trigger_words | トリガーワード |
| tags | タグ |
| source | ソース |
| source_url | ソース URL（本ページ） |
| exported_at | エクスポート日時（ダウンロード毎） |
| system_prompt | システムプロンプト本文 |
| model_config | モデル設定：provider / model / temperature / max_tokens / top_p |
| examples | サンプル |
| install_guide | 各プラットフォームの導入説明（Coze / Dify / Claude / カスタム） |
