Spark = Riggr's word for a prompt. A project is where those Sparks live together — one API key, one Talk to your AI path, and (when you want) one local app that grows with your store.
Riggr does not host the finished app. Your AI scaffolds it on your computer; Riggr supplies live Shopify data.
Spark = Riggr's word for a prompt
Same idea you already know - Riggr just names it Spark. Check below so we know it landed.
A project is your ops workspace in Riggr — not a separate Shopify app install for every idea.
What you get when Sparks share a project
riggr-*-api-key.env / .env.local. No juggling keys per Spark.npm run dev, one sidebar, one Help Center. Returns + WISMO + reorder can live together instead of three localhost tabs.When to use separate projects instead
Most merchants start with one project and grow Sparks into that same app.
Projects organize Sparks
One key, one AI handoff, one app that grows — unless you intentionally want separate apps.
Think in three phases. You can attach Sparks early for planning; prompts and handoffs unlock in order.
Download the project API key .env if you haven’t. On the project page, the emerald Do this first card is your kickoff: Copy this prompt to kickstart your app, then paste into Claude Code, Cursor, or Codex. With one Spark, Autopilot builds that template. With two, your AI follows composePrompt + riggr-compose: one Next.js app, left sidebar, shared Help Center. Starter wins port and folder defaults.
When the app runs on localhost and looks good, your AI should call mark_project_app_ready over MCP — or click Mark starter ready to unlock Add-ons and confirm in the dialog. That unlocks Add-ons, stashes the starter Talk to your AI line, and marks Starter + Compose Active (locked to the project — hover the lock icon for the tip).
Only the next Add-on is highlighted (emerald Do this next). Copy that one-line handoff into your AI. It loads the full Spark via use_prompt_in_project + riggr-addon and merges into the existing app — same .env.local, same port. Later Add-ons show Waiting until you finish the current one. Never a second project folder.
When that feature works, your AI calls mark_addon_applied — or click Mark add-on applied and confirm. That Spark becomes Active and locked; the next Waiting Add-on opens automatically. Repeat until every Add-on is Active.
Add-ons stay gated until the starter/Compose app exists, then merge one Spark at a time so your AI never juggles multiple Add-on handoffs. Attach early if you like — build and unlock in sequence.
The default way to use a Spark is Riggr Autopilot. Your AI loads the template over the Riggr MCP bridge — you don’t download and paste the 30KB file.
Open your project → use the emerald Do this first Talk to your AI card → copy the kickoff prompt → paste into Claude Code, Cursor, or Codex. One Spark loads that template; two Sparks load Compose over MCP (you still paste only the short line).
Prompts are MCP resources (riggr://prompts/...) and use_prompt_in_project. With two Sparks, get_project returns composePrompt plus riggr-compose. Add-ons use riggr-addon after unlock.
The only file you download is the project API key. The prompt tells your AI to search (usually Downloads) for riggr-*-api-key.env and wire it into .env.local.
During the build, your AI uses MCP to explore your store and load prompts. The finished app uses the Riggr REST API key at runtime — never MCP inside the app code.
I know how Autopilot loads Sparks over MCP
Acknowledge below so we know this landed.
I know MCP is for building, API key is for the app
Acknowledge below so we know this landed.
Open a project from Projects. Main path on the left; status and reference on the right.
Header
Left column (do the work)
Right column (status + reference)
.riggr/project.json for AI auto-detectI know where Talk to AI, Sparks, API key, and build status live on a project
Acknowledge below so we know this landed.
A project can attach up to eight Sparks.
| Role | Which Sparks | What happens | | --- | --- | --- | | Starter | First attached | Name, folder, port, accent defaults | | Compose | Second | Merged with Starter into one app + sidebar | | Add-on | 3rd–8th | Merged later into that same app |
One repo, one npm run dev, one SQLite DB. Persistent left sidebar with a section per Spark. Shared Help Center. Optional: expand View Compose instructions on the project if you want to read the merge brief yourself — your AI still loads it over MCP.
Add-on handoffs unlock only when get_project.addonsUnlocked is true (after mark_project_app_ready / Mark starter ready with confirm). Until then, Talk to your AI only covers Starter/Compose. Starter + Compose become Active.
Riggr highlights only the next Add-on (Do this next). Copy that handoff → AI merges with riggr-addon → confirm Mark add-on applied (dialog) / mark_addon_applied. That Spark becomes Active; the next Waiting Add-on opens. Same project key throughout.
You never paste the 30KB Spark body for Add-ons. Attach on the project, copy the highlighted one-liner, and your AI pulls the template over MCP — same as Autopilot.
Compose and Add-ons share one port (Starter wins). You only juggle ports if you intentionally run separate projects as separate apps.
Compose + Add-ons
Two Sparks to kickstart. More Sparks merge one at a time into the same app.
Every Riggr Spark combines four things:
What the app does, who it's for, and what problem it solves.
Which Shopify data the prompt uses (orders, fulfillments, inventory, etc.) and how it should be shaped.
Component structure, layout, styling, and interaction patterns — real specs, not vague guidance.
Next.js patterns, TypeScript conventions, Riggr REST at runtime, and error handling.
Small prompts produce vague outputs. Large, detailed prompts produce specific, robust apps. Every Riggr prompt has been iterated with real merchant flows — the length is intentional.
Pick Sparks that match jobs you struggle with today. Attach several on one project if those jobs belong in the same daily tool.
Best for: Merchants who want a project-management style home base for Shopify day-to-day - not another analytics dashboard.
Spark: Today checklist with live counts, an attention Inbox, and a Log of what you finished. Edit Routines so mornings match how you actually work.
Data used: Orders, fulfillment orders, products, locations, returns. Read-only.
Local port: localhost:3005 (Starter default when this Spark is first)
I picked a Spark that fits my store
Acknowledge below so we know this landed.
Once v1 is running:
Get the default version working before you customize.
Example: "Add a filter for orders from last 30 days only."
One change at a time is easier to review than giant refactors.
Prefer attaching another Spark on the same project over starting a second app for a related desk.
Your AI can help set up git so you can roll back.
Riggr Sparks are starting ideas, not finished products we host. Once the codebase runs, it is a normal Next.js app on your machine — reshape it, or attach the next Spark and merge.
After scaffold, ask your AI for a short CLAUDE.md or .cursorrules (keep it under 300 lines) covering customizations and how you work.
MCP is read-only. Writes to Shopify need Admin or your own Admin API integration — not Riggr.
If Morning checklist, exceptions, and reorder all belong in the same daily tool, keep them on one project and use Compose + Add-ons. Split projects when you truly want split apps.
Sparks on /sparks can show different access badges:
If a Spark is locked, the detail page shows why (MCP, one-time unlock, or connect Shopify first for billing). MCP subscription and one-time Spark purchases both bill through Shopify.
Missing a job in the catalog? On /sparks (signed in), use Suggest a Spark. You’ll share a working title, the merchant pain, the daily job, optional “what it is not,” which Shopify data you’d need, and how often you’d use it.
We review every idea carefully. Submitting is not a promise to publish — we may decline, reshape, combine, or postpone ideas, and there is no delivery timeline.
On the project: ⋯ → Settings (or /project/.../settings).
Billing Danger zone (cancel MCP) is different — that lives under Settings → Billing.
Need account + API key steps? Setup guide. Terminal / Node / npm run dev? Your computer setup. Public HTTPS for your team? Going live. Merchant-specific picks? Use cases. Stuck? Troubleshooting.