| name | fashion-commerce-engineering |
| description | Implements catalog truth, WooCommerce templates, product discovery, fit and returns contracts, secure customer journeys, and commerce-state behavior. |
Fashion Commerce Engineering
Use for catalog-backed collection, search, PDP, cart, checkout, account, order,
fit, returns, and service surfaces.
Owners and inputs
Route catalog-sot-integrator, woocommerce-theme-engineer,
fashion-component-commerce-engineer, fashion-merchandising-conversion-architect,
and fashion-product-fit-returns-specialist. Read catalog/dossier/image SOT,
commerce-state-contract.json, WooCommerce coverage, page blueprints, and
current official WooCommerce/WordPress documentation.
Procedure
- Map SKU, variation, price, availability, imagery, provenance, fit, policy,
and route IDs to authority before editing templates.
- Implement product discovery, PDP decisions, variation selection, cart,
checkout, account, order, fit, returns, and extension-absent states.
- Preserve server truth: authorization, HPOS-safe reads, nonces, escaping,
prepared queries, capabilities, privacy, and idempotent actions.
- Exercise simple, variable, unavailable, sale, sparse, long-content, guest,
auth, failure, and recovery journeys.
- Return source changes, state matrix, commerce-truth log, and HTML/JSON proof.
Verification
Run catalog consistency, provenance/image, PHP/theme lint, template-version, and
browser purchase checks. Never invent products, scarcity, reviews, fit promises,
prices, or policies. Rebuild tracked .min assets after CSS/JS changes.
Boundaries
No external catalog mutation, media upload, payment action, or deployment without
explicit approval. Commercial hypotheses remain experiments.
