site commerce conversion architecture
Workflow
- Confirm the business outcome, owner, source data, constraints, and success metric.
- Inspect the project and available account or analytics evidence before proposing changes.
- Use official documentation for current platform behavior and retain source provenance.
- Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
- Run only read-only diagnostics by default; gate external, paid, production, or publishing actions behind explicit approval.
Domain Focus
design ecommerce discovery, product, cart, checkout, trust, tracking, and recovery flows.
Official Sources
https://web.dev/learn/ | https://www.w3.org/WAI/standards-guidelines/wcag/
Guardrails
- Preserve existing design and content conventions unless the task calls for a redesign.
- Review external code, assets, and components for provenance, license, accessibility, performance, and dependency cost.
- Require explicit approval for production deployment, DNS, publishing, or irreversible migrations.
1---2name: site-commerce-conversion-architecture3description: Use for Site Building work when Codex should design ecommerce discovery, product, cart, checkout, trust, tracking, and recovery flows.4---5
6# site commerce conversion architecture
7
8## Workflow
9
101. Confirm the business outcome, owner, source data, constraints, and success metric.
112. Inspect the project and available account or analytics evidence before proposing changes.
123. Use official documentation for current platform behavior and retain source provenance.
134. Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
145. Run only read-only diagnostics by default; gate external, paid, production, or publishing actions behind explicit approval.
15
16## Domain Focus
17
18design ecommerce discovery, product, cart, checkout, trust, tracking, and recovery flows.
19
20## Official Sources
21
22https://web.dev/learn/ | https://www.w3.org/WAI/standards-guidelines/wcag/
23
24## Guardrails
25
26- Preserve existing design and content conventions unless the task calls for a redesign.
27- Review external code, assets, and components for provenance, license, accessibility, performance, and dependency cost.
28- Require explicit approval for production deployment, DNS, publishing, or irreversible migrations.
srednoff888-art