ecommerce

name

ecommerce

description

E-commerce website design, business model selection, and conversion strategy. Use when building online shops, product catalogues, checkout flows, or acquisition paths for any site where visitors buy products or services online. Covers the CLICK system (Convenient, Likeable, Informative, Customized, Knowledgeable), trust signals, product-page design, checkout risk reduction, pricing psychology, and traffic-to-retargeting mechanics.

Ecommerce

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

Use when

• The task matches this domain: E-commerce website design, business model selection, and conversion strategy. Use when building online shops, product catalogues, checkout flows, or acquisition paths for any site where visitors buy products or services online. Covers the CLICK system (Convenient, Likeable, Informative, Customized, Knowledgeable), trust signals, product-page design, checkout risk reduction, pricing psychology, and traffic-to-retargeting mechanics.
• 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. Identify the business model and channel reality before recommending page or funnel patterns.
3. Treat the store as a traffic, product-decision, checkout, retention, and measurement system before recommending isolated page changes.
4. Use only the relevant detailed guidance and references for the request at hand.
5. Produce the strategy, writing, or framework output this skill is responsible for.
6. Check the result for clarity, realism, and handoff readiness.

Quality standards

• Outputs must be specific, usable, and grounded in the available evidence.
• Recommendations must match the business model, traffic source, and fulfilment reality.
• 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 import Amazon-specific tactics into a standalone ecommerce site without checking fit.
• 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 references/business-model-selection.md when the task depends on marketplace vs owned-store tradeoffs, fulfilment posture, or retention model.
• Use references/acquisition-and-retargeting.md when traffic, retargeting, or remarketing paths materially affect the recommendation.
• Use references/premium-ecommerce-growth-system.md when designing, auditing, or improving ecommerce product pages, category pages, cart, checkout, retention, or revenue measurement for a premium client.
• 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.