architecture-well-architected-commerce

Define and review VTEX commerce architecture decisions with pillar-based alignment.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/exilonX/ap2 --skill architecture-well-architected-commerce-exilonx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-well-architected-commerce
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/architecture-well-architected-commerce
Command: npx skills add https://github.com/exilonX/ap2 --skill architecture-well-architected-commerce-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams prevent fragile, insecure VTEX commerce architectures by grounding cross-cutting design decisions in a consistent Well-Architected Commerce framework so reliability, future-proofing, and operational excellence aren’t left to chance.

Core Features & Use Cases

  • Cross-cutting architecture guidance for VTEX: Aligns solution architecture choices across storefront, VTEX IO, headless/marketplace, and payments using Technical Foundation, Future-proof, and Operational Excellence.
  • Decision routing to product tracks: Routes implementation details to the right specialized skills (e.g., VTEX IO service paths/performance, Master Data suitability, marketplace fulfillment patterns) instead of overloading a single plan.
  • Guardrails and constraints for safer delivery: Enforces hard constraints around Technical Foundation (secrets/PCI/private APIs), Future-proof complexity justification, native-before-IO discipline, and Master Data placement to avoid reliability and compliance pitfalls.
  • Review and readiness structure: Supports architecture reviews and RFP-level scoping with an explicit decision log approach and a checklist for metrics, ownership, and failure modes.

Quick Start

Use the architecture-well-architected-commerce skill to review a proposed VTEX storefront + VTEX IO + payments architecture and produce a pillar-mapped decision log with routed next steps for the relevant product-track skills.

Frequently Asked Questions about architecture-well-architected-commerce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a VTEX commerce architecture for operational excellence and security?

Review VTEX commerce architecture by mapping decisions against a Well-Architected framework covering technical foundation, operational excellence, and security. This framework validates storefront models, VTEX IO extensions, and payments constraints to prevent fragile designs.

What is the best way to scope VTEX IO extensions and storefront model choices?

Scoping VTEX IO extensions and storefront models requires a cross-cutting readiness review that justifies complexity and enforces native-before-custom routing. This approach aligns choices with future-proof architecture constraints and specialized product tracks.

How does well-architected design routing work for marketplace integration and payments constraints?

Well-architected design routing directs marketplace integration and payments constraints to specialized product-track skills instead of overloading a single plan. This maintains Master Data placement rules and ensures PCI scope guardrails are satisfied.

Can I use this framework for RFP-level architecture scoping and decision logging?

Yes, you can use this framework for RFP-level architecture scoping and decision logging. It provides an explicit decision log approach alongside a checklist for metrics, ownership, and failure modes to structure readiness reviews.

When should I not use custom VTEX IO extensions over native commerce features?

You should not use custom VTEX IO extensions when native commerce features satisfy the requirement. The framework enforces native-before-IO discipline and requires justifying custom complexity to avoid reliability pitfalls and maintain operational excellence.