launchmystorelisted

Build, run, and customize a LaunchMyStore e-commerce store from natural language. Use when the user wants to scaffold an app, ship a storefront / checkout / admin extension, build and deploy a WASM Function, configure App Bridge actions (Toast, Modal, ResourcePicker, SessionToken, TitleBar...), manage products / orders / customers / themes via the LaunchMyStore MCP server, or write Aqua (Liquid-dialect) theme code. Triggers include: "build a LaunchMyStore app", "lms cli", "add a discount function", "set up app bridge", "manage my store with AI", "write a theme block", "install an extension", "deploy a function", "use launchmystore", "lms", or any mention of LaunchMyStore / launchmystore.io.
LaunchMyStore/skill · ★ 0 · AI & Automation · score 73

Install: claude install-skill LaunchMyStore/skill

# LaunchMyStore You're an AI assistant helping the user work with **LaunchMyStore** — an e-commerce platform with apps, extensions, WASM Functions, Liquid-based Aqua themes, and an MCP server that lets an LLM run a real merchant store end-to-end. This skill follows the open `SKILL.md` standard and works identically across Claude Code / Claude.ai / the Claude API / OpenAI Codex / Cursor / Gemini CLI / Windsurf / Antigravity / Aider / OpenCode / Kilo Code / Augment / Hermes / Mistral Vibe — anywhere SKILL.md is supported. Four developer-facing surfaces ship today: 1. **`@launchmystore/cli`** — local Javy compile, app scaffolding, extension push, function build/test/deploy, webhook tail. 2. **`@launchmystore/app-bridge`** + **`@launchmystore/app-bridge-react`** — iframe ↔ host SDK for admin / checkout / post-purchase extensions. 3. **LaunchMyStore MCP server** — 130+ tools for products, orders, customers, themes, billing, plus AI helpers like `chat_with_data`. 4. **Aqua theme system** — `.aqua` files using the Liquid templating language with sections, blocks, snippets, settings schema, and the `{owner}.metafields.{namespace}.{key}` access pattern. Canonical docs live at <https://docs.launchmystore.io>. ## Step 1 — Identify the intent Match the user's request to one of these tracks and load the matching reference. **If the user is new or hasn't specified, always check `references/01-quickstart.md` first.** | User says | Track | Reference | |---|---|---| | "I