ChiefOSby ConversintStart free
Menu
← Back to the library
Marketing and creative direction

GenStore storefront workflow

Plan and operate a GenStore storefront using a supplied brand brief, product facts, catalog, and authorized account. Covers store design, listings, channel readiness, and launch verification; returns a proposal when no working GenStore connection is available.

Works with the context you provideVersion 1.0.0

GenStore storefront workflow

Use this skill for the outcome in its description. Start with the supplied request and evidence, identify the specific task, and distinguish planning from execution. Do not trigger solely because the subject happens to be fashion, retail, or a technology named in an example. Read `references/execution-contract.md` before applying a retained source method.

Select the narrowest matching method below, then read its full entrypoint and the resources it requires. If multiple methods cover the same outcome, choose the one matching the user's environment and inputs; do not run them all. Retain each method's input requirements, decision steps, validation, output structure, and failure handling. If prerequisites are absent, use its honest proposal-only fallback or state that its documented path is blocked.

Store workflow

  1. Extract the brand, audience, locale, currency, product/variant facts, pricing and margins, fulfillment constraints, and requested channels from supplied material. Mark missing facts; do not turn a product photo into invented specifications.
  2. Draft a store map with home, collection, product, cart, and policy pages. Propose accessible type/color choices and explain how the design supports the audience.
  3. Build catalog drafts with titles, factual descriptions, image alt text, variants, inventory source, shipping/returns, and evidence for every claim. Treat dropshipping and print-on-demand availability as unverified until the connected account confirms a supplier, region, cost, and fulfillment path.
  4. If account tools are available, inspect their real supported operations and current store state. Apply only requested edits, then read back the resulting records. This repository documents conversational capabilities, not a reusable API client; do not invent endpoints or say an integration is installed.
  5. Review checkout/payment readiness, tax/shipping configuration, policies, domain, analytics, and channel mappings. Prepare a launch preview. Publishing the store, purchasing services, sending campaigns, and enabling social channel sync require scope from the user.
  6. Return page/catalog drafts or confirmed changes, unresolved readiness issues, costs/dependencies, and the next concrete action. Call a store live only after the public URL and checkout behavior have been verified.

Return the requested deliverable with evidence, assumptions, validation performed, unresolved dependencies, and actual execution status. Source-specific results must be verified independently; importing these methods does not establish a working service connection.