consumer-protection-readiness

People feel cheated by inconsistency and surprise: a price that changes at checkout, a trial that quietly bills, a cancel button that does not exist. This skill checks that what the product shows, charges, and promises agree. Legal specifics are the owner's and counsel's.

Activate when

• Prices, plans, checkout, invoices, trials, subscriptions, auto-renewal, discounts, refunds, returns, shipping, or digital delivery exist.
• Not for a free product with no offers (record "not applicable"). Integration security of the payment provider is payments-readiness. Recurring mechanics in depth are subscription-readiness.

Working alone

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: design-system-reconnaissance, subscription-readiness, payments-readiness.

Inspect