Page launch
Publish the page you actually approved
Verify the exact page version, source, theme, assets and shopping journey before releasing it to customers.
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
Publishing is intentionally separated from page creation and design approval.
This workflow does not redesign or rebuild the page. It verifies that the saved draft is the same version that passed review and then publishes that exact version.
What you need
- Page name or ID
- Exact version
- Recorded design approval
- Completed hosted QA
- Explicit authority to publish
Starting prompt
Replace the bracketed details, then give the complete prompt to your connected AI agent.
Publish Lexsis page [PAGE NAME OR ID], version [VERSION].
I explicitly approve live publication of this exact page version after you verify its design approval, persisted source, store and theme binding, responsive QA, commerce behaviour, claims, assets, integrity and publication entitlement.
Do not rebuild or silently modify the page. If the saved version differs from the approved version, stop and report the difference.How the workflow works
Follow the sequence in order. Approval and verification remain separate from page creation and live publication.
- 01
Identify the exact target
The agent resolves the requested page ID and version. A page name without a clear version is not enough to publish.
- 02
Confirm design approval
The approved design record must belong to the same page version currently saved in Lexsis.
- 03
Compare the persisted source
The agent confirms that the source, sections and compiled bundle match the reviewed version.
Any visible edit after approval returns the page to review.
- 04
Recheck quality evidence
The page must have completed review at:
- 390px
- 768px
- 1280px
Commerce, copy, claims, assets, interactions and integrity must all pass.
- 05
Confirm the store binding
The workspace, connected Shopify store and theme must still exist and match the approved page.
- 06
Confirm publication entitlement
The agent checks that the workspace can publish the page.
- 07
Publish the page
Only after the gates pass does the agent use the Lexsis live publication action.
- 08
Report the result
The final response includes:
- Published page
- Published version
- Public URL
- Publication result
- Previous version
- Rollback availability
How Lexsis MCP is used
Each operation stays tied to the selected workspace, store, page and version for this workflow.
- Read the latest edit context
- Verify source and bundle integrity
- Confirm the page version
- Confirm workspace and store access
- Check publication entitlement
- Publish through Lexsis live operations
Safety boundaries
- Draft creation is not publication approval
- Design approval is not publication approval
- A preview request is not publication approval
- The agent cannot substitute local checks for Lexsis integrity evidence
- Version drift blocks publication
- Rollback and unpublish require separate explicit requests