Store setup
Give your AI agent the context behind your store
Connect your Shopify store through Lexsis and create a reusable source of truth for your brand, theme, catalog, customer personas, policies, offers, and available reviews.
Install Lexsis MCP and skills in your AI client
Run the installer, then follow the authentication prompts to connect Lexsis MCP and add the workflow skills to your supported AI client.
curl -fsSL https://mcp.trylexsis.com/install.sh -o /tmp/lexsis-install.sh && sh /tmp/lexsis-install.shWhat this workflow does
Most AI agents begin with very little understanding of your store. They may know the product you mention, but not your complete catalog, visual system, claims, policies, customer concerns, or active Shopify theme.
This workflow creates reusable store context that later workflows can reference when planning, designing, or improving storefront pages.
It does not create, edit, or publish a page.
What you need
- A Shopify store connected to Lexsis
- Lexsis MCP connected to your AI agent
- The store and theme you want the agent to use
- Optional merchant notes about positioning or customers
Starting prompt
Replace the bracketed details, then give the complete prompt to your connected AI agent.
Use the Lexsis `setup` skill for my Shopify store.
Store or domain: [STORE]
Preferred theme: [THEME OR “USE THE DEFAULT”]
Build reusable storefront context covering the brand, design guide, navigation, product catalog, customer personas, store rules, offers, claims, review availability, and theme CSS.
If multiple workspaces, stores, or themes match, ask me to choose. Clearly label confirmed facts, evidence-supported inferences, and open questions.
Do not create, edit, or publish a page.How the workflow works
Follow the sequence in order. Approval and verification remain separate from page creation and live publication.
- 01
Find the connected store
The agent asks Lexsis for available workspaces and connected Shopify stores. It resolves the exact workspace and store instead of assuming from the domain name.
- 02
Select the working theme
Lexsis returns the available themes and their identifiers. The agent uses your selected theme or the default theme when only one clear option exists.
Separate themes remain separate. Their styles are not merged into one generic design system.
- 03
Read the brand and design context
The agent reads:
- Brand identity and positioning
- Colors, fonts and logos
- Theme configuration
- Navigation
- Lexsis design guidance
- Existing brand-owned visual references
- 04
Map the Shopify catalog
The agent reads the complete connected catalog, including all available pages of products.
It builds a compact map of products, variants, options, media, product types, tags, selling plans and availability gaps.
Prices and availability are treated as dated snapshots. Later workflows refresh selected products before using them.
- 05
Map proof and store rules
The agent checks:
- Review connection status
- Available review collections
- Shipping and returns
- Guarantees
- Offer restrictions
- Approved claims
- Certifications
- Required and prohibited language
Unsupported claims are saved as open questions rather than presented as facts.
- 06
Create the persona map
Personas are built from verified store information, product patterns, merchant notes and information you confirm.
The agent must not invent demographics, customer quotations or buying behaviour.
- 07
Save reusable context
The final setup becomes the store map that later Lexsis workflows read before making page decisions.
How Lexsis MCP is used
Each operation stays tied to the selected workspace, store, page and version for this workflow.
Workspace
- List available workspaces
- Read workspace details
- Find connected stores
Brand and theme
- Read brand context
- Read the brand kit
- List and inspect themes
- Read navigation
- Load the exact design guide
Catalog and proof
- Read the complete product catalog
- Refresh missing product information
- Check review availability
- Read active review collections
Safety boundaries
- No pages are created
- No products are changed
- No assets are generated
- No customer records or complete review text are stored
- No theme is published or modified
- No unsupported claims are invented
What you receive
The result includes the working artifacts and verification evidence needed for the next decision.
- Selected workspace, store and theme
- Brand context
- Exact design guidance
- Product catalog map
- Persona map
- Store rules and claim controls
- Review availability
- Separate theme CSS files
- Open questions requiring merchant confirmation