ecommerce-checkout

name	ecommerce-checkout
description	Ecommerce brand building and checkout experience optimisation. Use when establishing the brand foundation before site build, designing the checkout flow, or planning the post-purchase experience. Covers Verma's 7C brand framework, EVP vs UVP, checkout UX deep-dive, customer journey mapping, and DTC growth levers. Companion to the ecommerce skill.

Ecommerce Checkout

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use when

• The task matches this domain: Ecommerce brand building and checkout experience optimisation. Use when establishing the brand foundation before site build, designing the checkout flow, or planning the post-purchase experience. Covers Verma's 7C brand framework, EVP vs UVP, checkout UX deep-dive, customer journey mapping, and DTC growth levers. Companion to the ecommerce skill.
• The user needs domain-specific strategy, writing, or planning in this area.

Do not use when

• Another skill is clearly narrower and better matched to the request.
• The task is unrelated to this domain or needs direct implementation instead.

Required inputs

• Business context, target audience, and the artifact or decision being developed.
• Any existing materials, constraints, or supporting references already available.

Workflow

1. Read the current business context and the concrete task to solve.
2. Use only the relevant detailed guidance and references for the request at hand.
3. Produce the strategy, writing, or framework output this skill is responsible for.
4. Check the result for clarity, realism, and handoff readiness.

Quality standards

• Outputs must be specific, usable, and grounded in the available evidence.
• Recommendations should support follow-on execution instead of staying abstract.
• The result should remain consistent with the broader repository system.

Anti-patterns

• Do not produce generic framework dumps with no decision made.
• Do not invent facts to complete the output.
• Do not ignore the actual audience, offer, or business constraints.

Outputs

• Strategy notes, writing deliverables, framework outputs, or implementation-facing recommendations.

References

• Start with references/legacy-guidance.md when you need the preserved detailed instructions from the previous skill version.
• Use sibling reference ../ecommerce/references/premium-ecommerce-growth-system.md when checkout recommendations must connect to product-page clarity, cart trust, abandoned-cart recovery, retention, or ecommerce measurement.
• Read only the specific files under references/ that match the current task instead of loading the whole directory.
• This skill has no bundled scripts by default; keep execution focused on the documented workflow and any existing project files.

Notes

• Treat this SKILL.md as the portable execution layer for both Codex and Codex.
• Preserve existing project behavior unless the current task explicitly requires a change.