Skip to content

Rules

Each file in rules/ is a short list of constraints for one skill. The file name matches the skill directory. The file is plain Markdown: a heading and the rules. It has no YAML frontmatter.

Use a rule as always-on guidance. Use the matching skill when the agent is doing that task and needs the procedure, examples, and references.

The validator checks that:

  • Every skill has a rule, and every rule names a skill.
  • A rule starts with a level-1 heading.
  • A rule is between 8 and 80 lines.

Keep a rule specific enough that an agent can apply it without opening the skill. If a rule needs a worked example, that example belongs in the skill instead.

Rule Category
woocommerce-plugin-development Platforms and storefronts
woocommerce-rest-api Platforms and storefronts
wordpress-plugin-security Platforms and storefronts
shopify-app-development Platforms and storefronts
headless-nextjs-storefront Platforms and storefronts
payment-gateway-integration Payments and orders
order-and-webhook-reliability Payments and orders
subscription-billing Payments and orders
fraud-and-risk-basics Payments and orders
tax-and-shipping Payments and orders
multi-vendor-payouts Payments and orders
stripe-payments Payments and orders
iranian-payment-gateways Payments and orders
product-catalog-modeling Catalog and search
marketplace-search-and-ranking Catalog and search
vector-product-search Catalog and search
google-merchant-product-feeds Catalog and search
product-description-guardrails Catalog and search
checkout-ux-and-conversion Conversion and growth
ecommerce-seo-structured-data Conversion and growth
conversion-event-tracking Conversion and growth
rtl-and-persian-localization Conversion and growth
storefront-accessibility Conversion and growth
storefront-performance Conversion and growth
inventory-and-multi-warehouse Store operations
returns-and-refunds Store operations
b2b-pricing Store operations
catalog-import-and-migration Store operations
mcp-store-tooling Store operations