playbooks

home / skills / secondsky / claude-skills / woocommerce-copy-guidelines

woocommerce-copy-guidelines skill

/plugins/woocommerce-copy-guidelines/skills/woocommerce-copy-guidelines

This skill helps you write user-facing copy for WooCommerce by enforcing sentence case, conciseness, and consistency across UI elements.

npx playbooks add skill secondsky/claude-skills --skill woocommerce-copy-guidelines

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
770 B
---
name: woocommerce-copy-guidelines
description: Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects.
---

# WooCommerce Copy Guidelines

This skill provides guidelines for writing user-facing copy in WooCommerce, including UI text, labels, buttons, messages, and documentation.

## Instructions

Follow these guidelines when writing any user-facing text:

1. **Sentence case**: See [sentence-case.md](sentence-case.md) for rules on using sentence case for all UI text

## Key Principles

- Always use sentence case for UI text, not title case
- Keep copy concise and action-oriented
- Use clear, simple language
- Be consistent with existing WooCommerce copy patterns

Overview

This skill defines clear, practical guidelines for writing user-facing copy in WooCommerce projects. It focuses on UI text, labels, buttons, messages, and documentation to ensure consistency and usability. Use these rules to make copy concise, action-oriented, and aligned with WooCommerce patterns.

How this skill works

The skill inspects and guides copy for labels, buttons, error messages, onboarding text, and documentation snippets. It enforces sentence case, promotes simple language, and checks for consistency with established WooCommerce phrasing and tone. Apply it during content authoring, UI reviews, and localization handoffs to keep all product text aligned.

When to use it

  • Writing any UI label, button text, or menu entry
  • Drafting error, success, or informational messages shown to users
  • Creating onboarding, setup, or contextual help copy
  • Preparing developer-facing or end-user documentation for WooCommerce features
  • Reviewing translations or handoffs for localization

Best practices

  • Use sentence case for all UI text (not title case) to match WooCommerce conventions
  • Keep copy concise and action-oriented — prefer short verbs and clear outcomes
  • Choose simple, familiar words over jargon; avoid technical phrasing for end users
  • Be consistent with existing WooCommerce patterns for labels, verbs, and microcopy
  • State the action or outcome first in buttons and calls to action
  • Write messages that help users recover from errors and explain next steps

Example use cases

  • Button text: use ‘Save changes’ instead of ‘Save Changes’ or ‘Save’ when context needs clarity
  • Error message: explain cause and next step, e.g., ‘Payment failed. Try another card or contact support.’
  • Onboarding tip: short, actionable guidance like ‘Connect your payment gateway to start accepting payments.’
  • Documentation heading or step label following sentence case: ‘Set up shipping zones’
  • Localization note: hand off concise strings with context and examples to translators

FAQ

Why sentence case instead of title case?

Sentence case reads more conversationally and matches WooCommerce UI patterns, improving scannability and consistency.

How long should UI copy be?

Aim for the shortest text that still communicates the action or result clearly—usually one short sentence or a brief phrase.