GenesisAI commerce studio
Genesis SkillGuided foundation
Prepare an existing Selldone shop's domain, email, public copy, settings, policies, categories, and products—without committing the full catalog before the sample is right.
The Skill starts with a read-only audit, gathers missing facts, presents proposed changes, and asks before every write. Existing configuration is preserved unless the user approves a specific replacement.
The AI should never turn a broad “set up my shop” request into silent production changes.
Confirm the connected MCP identity, intended shop, scopes, and current state.
Resolve business identity, domain, provider, content, policies, category, and product data without guessing.
Show exact proposed settings, dependencies, approvals, validations, and unresolved decisions.
Provide exact DNS records, wait for the user's DNS change, then verify DNS and SSL before claiming success.
Use the supported provider flow, keep credentials out of chat, and report the test without exposing secrets.
Merge current settings, preserve untouched values, upload approved brand assets, and verify the saved result.
Use only supplied facts, label Privacy and Terms as drafts, and save only the exact user-approved version.
Resolve duplicates, approve the hierarchy, create parents before children, and verify the resulting tree.
Add two or three representative products individually as unlisted, re-read every field, and show the result.
Wait for explicit post-creation approval before any remaining product is added or any product is published.
The sample set should cover the important catalog patterns—different categories, variants, product types, prices, inventory behavior, media, SEO, and delivery fields—so errors appear while they are still cheap to correct.
The AI must show the requesting user the created product IDs and fields, ask them to inspect the records in Selldone, and stop. Silence, partial feedback, earlier plan approval, or another person's approval cannot unlock the remainder. If anything is wrong, the AI fixes only the samples and repeats this gate.
Continuing creation and publishing require separate, explicit approval.
Unlisted during review by defaultPrivacy Policy and Terms of Use are drafts based on facts the user supplies. The user remains responsible for legal review. Email credentials belong only in secure Selldone or MCP inputs and must never appear in chat, code, screenshots, or the final report.
Provide accurate business facts and a structured catalog source where possible. The Skill makes the AI surface missing information and approval points instead of guessing.
Use the Selldone Genesis Essential Setup skill for my connected shop. Begin with a read-only audit. Prepare the domain, email, shop copy and settings, policy drafts, category plan, and two or three representative unlisted products. Show every proposed change and stop after the sample products. Do not add or publish the remaining catalog until I explicitly confirm the created samples are correct.
Connect MCP, attach the Essential Setup Skill, and let a verified sample prove the catalog pattern before you scale it.