Claude Skills by vtex

github.com/vtex

10 skillsA× 100 installs8 views

Vtex Architect ScribeAAuthors VTEX technical documentation (integration specs, functional docs, design docs) and then verifies it against ground truth with an independent adversarial fact-check before it ships. Use when the user wants to write, draft, or document a VTEX integration/architecture, or to fact-check / verify an existing VTEX doc. The architect decides; the scribe writes it down and proves it correct. Do NOT use for architecture decisions themselves (use vtex-architect) or for live account state readou...documentationrustgoVotes: 0GitHub stars: 2
Vtex ArchitectAActivate for solution architecture questions or matters — including any question about VTEX architecture, platform decisions, storefront design, backend integrations, checkout, OMS, Intelligent Search, data architecture, personalization, analytics, or migration planning. Load when the user asks about VTEX IO, FastStore, VTEX APIs, catalog design, fulfillment, payments, multi-tenancy, franchise accounts, or any e-commerce infrastructure topic related to VTEX.businessgoreactVotes: 0GitHub stars: 2
Vtex ExpertAActivate for technical questions about how the VTEX platform works — including platform mechanics, feature behavior, logistics and shipping strategies, OMS order lifecycle, catalog structure, promotions and pricing configuration, checkout behavior, and admin platform configuration. Use when the question is "how does X work" or "how do I configure X" on the VTEX platform. Do NOT activate for solution architecture decisions or system design trade-offs — use vtex-architect for those.documentationgorailsVotes: 0GitHub stars: 2
Vtex InspectorAActivate when the user asks about the current state of a specific VTEX account — what is configured, what is active, what has been implemented. Use for questions like "what carriers do we have configured?", "what promotions are currently active?", "what apps are installed?", "how is our shipping set up?", "what does our account architecture look like?", or "what trade policies exist?". Do NOT activate for questions about how the platform works in general (use vtex-expert for that) or for arch...developmentgorailsVotes: 0GitHub stars: 2
Vtex Architect ScribeAAuthors VTEX technical documentation (integration specs, functional docs, design docs) and then verifies it against ground truth with an independent adversarial fact-check before it ships. Use when the user wants to write, draft, or document a VTEX integration/architecture, or to fact-check / verify an existing VTEX doc. The architect decides; the scribe writes it down and proves it correct. Do NOT use for architecture decisions themselves (use vtex-architect) or for live account state readou...documentationrustgoVotes: 0GitHub stars: 2
Vtex ArchitectAActivate for solution architecture questions or matters — including any question about VTEX architecture, platform decisions, storefront design, backend integrations, checkout, OMS, Intelligent Search, data architecture, personalization, analytics, or migration planning. Load when the user asks about VTEX IO, FastStore, VTEX APIs, catalog design, fulfillment, payments, multi-tenancy, franchise accounts, or any e-commerce infrastructure topic related to VTEX.businessgoreactVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Vtex ExpertAActivate for technical questions about how the VTEX platform works — including platform mechanics, feature behavior, logistics and shipping strategies, OMS order lifecycle, catalog structure, promotions and pricing configuration, checkout behavior, and admin platform configuration. Use when the question is "how does X work" or "how do I configure X" on the VTEX platform. Do NOT activate for solution architecture decisions or system design trade-offs — use vtex-architect for those.documentationgorailsVotes: 0GitHub stars: 2
Vtex InspectorAActivate when the user asks about the current state of a specific VTEX account — what is configured, what is active, what has been implemented — or wants to debug, validate, or diagnose a VTEX implementation. Use for questions like "what carriers do we have configured?", "what promotions are currently active?", "how is our shipping set up?", "what does our account architecture look like?", "what trade policies exist?", "why is this SKU not showing at checkout?", or "why did this promotion not...developmentgorailsVotes: 0GitHub stars: 2
Vtex Architect ScribeAAuthors VTEX technical documentation (integration specs, functional docs, design docs) and then verifies it against ground truth with an independent adversarial fact-check before it ships. Use when the user wants to write, draft, or document a VTEX integration/architecture, or to fact-check / verify an existing VTEX doc. The architect decides; the scribe writes it down and proves it correct. Do NOT use for architecture decisions themselves (use vtex-architect) or for live account state readou...documentationrustgoVotes: 0GitHub stars: 2
Vtex ArchitectAActivate for solution architecture questions or matters — including any question about VTEX architecture, platform decisions, storefront design, backend integrations, checkout, OMS, Intelligent Search, data architecture, personalization, analytics, or migration planning. Load when the user asks about VTEX IO, FastStore, VTEX APIs, catalog design, fulfillment, payments, multi-tenancy, franchise accounts, or any e-commerce infrastructure topic related to VTEX.businessgoreactVotes: 0GitHub stars: 2