Selldone GenesisAI commerce studio

Genesis SkillDeep build

Build a complete custom storefront.

Use this skill when you want a fully planned, brand-specific customer experience—not a quick setup task or a few visual changes.

Complete storefront Multiple review cycles Real commerce flows Cloudflare Workers

The right Skill for a deep build.

The Skill grounds your AI in the current Selldone storefront guideline, shop context, starter architecture, API contracts, security boundaries, and a plan-first delivery process.

Use it for

  • A complete replacement or major customer-facing redesign
  • Brand-specific navigation, content, and shopping journeys
  • Real catalog, authentication, basket, checkout, and account flows
  • Iterative browser testing and production launch preparation
  • Cloudflare Workers Static Assets deployment

Do not use it for

  • A quick domain or email configuration
  • Basic shop settings and public copy only
  • Privacy, Terms, categories, or initial product entry alone
  • A one-prompt promise with no review or browser validation
Choose Essential Setup instead Smaller scope →

Plan, prove, build, and verify.

The workflow protects working commerce behavior while letting the experience become specific to the business.

  1. 01Connect the intended shop

    Use Selldone MCP's guided authorization and approve only the scopes the project needs.

  2. 02Attach the Skill

    Give the AI the downloadable SKILL.md so it knows the required contracts, approvals, and validation.

  3. 03Clone the official starter

    Start from the verified static storefront and preserve its storefront, dashboard, callback, and shared modules.

  4. 04Plan before editing

    Produce routes, data contracts, feature registry, visual direction, milestones, risks, and acceptance checks.

  5. 05Approve the plan

    Resolve scope and business decisions before committing to substantial implementation work.

  6. 06Build in stages

    Implement and test real catalog, auth, basket, checkout, orders, content, and responsive behavior in reviewable slices.

  7. 07Approve production separately

    Build and preview first; only then configure the final domain, OAuth callback, and Cloudflare deployment.

Experience freedom. Contract discipline.

The Skill tells the AI to use documented Selldone endpoints, keep MCP out of runtime code, preserve public OAuth PKCE, respect guest identity and basket billing, and test the exact production output.

genesis / implementation-plan Preview only
✓ Shop audit ✓ Starter inspected 03 Routes & data 04 Build slices 05 Production review
Current artifactRuntime contract map
Owner review
Build laneAI→MCP→Selldone
Shopper laneBrowser→XAPI→Commerce
✓ Public OAuth PKCE ✓ Guest basket identity ✓ Checkout & payment ✓ Order history
$ npm run build:static $ npm run preview:static ✓ static assets, callback route, and production output verified

Experience lane

  • Brand system and responsive shell
  • Routes, content, search, and discovery
  • Loading, empty, error, restricted, and offline states
  • Accessibility and browser validation

Commerce lane

  • XAPI for customer-facing runtime
  • Public OAuth Authorization Code + PKCE
  • Guest basket, checkout, payment, and order types
  • No secrets, guessed endpoints, or placeholder contracts

Start with clarity.

Share the business goals, audience, content, visual references, required flows, locales, currencies, and launch constraints. Let the AI inspect what it can instead of guessing.

Copy into your AI workspace

Use the Selldone Genesis Custom Storefront skill to plan a complete storefront for my connected shop. Inspect the business and starter repository first. Present the proposed routes, features, data contracts, visual direction, risks, stages, and acceptance checklist before editing files.

Ready for the full build?

Connect MCP, download the Skill, clone the starter, and give the planning stage the attention a production storefront deserves.

Copied to clipboard