# AI Coding

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/ai-coding (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/ai-coding

## Vibe code all day. Checkout, payments, attribution secure.

Bring Claude Code, Codex, or any coding agent, or use Mist. Fluid runs the hosting, security, and scale, so anyone on your team can build without calling IT.

The five places you can build: Website (your storefront theme, what shoppers see on a computer or a phone), Sites, the Mobile app, Checkout, and Admin.

## How it fits together: we run the core. You build the rest.

Checkout, payments, attribution, and orders stay with Fluid. Your team builds the places people see, and Fluid handles the hosting, Git, databases, and sign-in underneath.

| Layer | What’s in it |
| --- | --- |
| Built by your team | Website (your storefront theme), Portal and Sites (sites for reps and customers), Mobile app (the rep app, in your brand), Checkout (drop zones inside checkout), Admin (Droplets inside the admin) |
| Run by Fluid | Checkout (one page from cart to paid), Payments (get paid the way your customers pay), Attribution (every order knows who sold it), Orders (every order, in one record), Autoship (renewals that charge once, on time). Your builds read from these and can’t change how they work. |
| Handled by Fluid | Git, APIs, databases, hosting, and sign-in, under every build |

## Website: Marketing prompts. The new homepage is live by the launch.

Describe the page, and Mist builds it in your storefront theme. Nobody has to know Liquid, and nothing reaches shoppers until you publish.

1. **Marketing prompts:** Maya Chen, Marketing Director: “Rebuild our homepage for the spring launch around this creator video. Keep the best sellers underneath.”
2. **Mist builds a preview:** a full-width video hero, four best sellers with live prices, and reviews from your top-rated products, ready to publish or change.
3. **Live on your website:** “The spring launch. Mornings, sorted.” with best sellers underneath.

Also asked for this week: “Clone our old site into the new theme,” “Make a landing page for the afternoon-crash angle,” and “Add reviews under every product photo.” [How Fluid themes work](https://docs.fluid.app/themes/developer-guide).

## Sites: a Site for every audience. Built in one conversation.

Build as many Sites as your field needs. Make one public or keep it behind sign-in, share it by member type and country, and pick the Site every member sees by default.

1. **A field leader prompts:** Marco Weber, Field Director, Germany: “Build a Site for our leaders in Germany with this quarter’s training and bonus rules. Only they should see it.”
2. **Mist builds a preview:** “Q1 leadership. Lead the launch.” shared with reps in Germany, with training videos (Week 1: Your first 10, 12 min; Week 2: Coaching calls, 9 min) and bonus rules (Fast start: 3 new customers in 30 days; Team bonus: 5 active reps by Mar 31).
3. **Leaders sign in:** Jonas Becker, a rep in Germany, sees 3 Sites: Launch hub (public), Rep home (the default for every member), and the new Q1 leadership Site.

Also asked for this week: “Build a public Site for our charity walk,” “Make a welcome Site for new customers,” and “Give Mexico its own training library.”

## Mobile app: Sales prompts. Reps have it by the end of the webinar.

Your sales and marketing teams describe the tool they need, Mist builds it, and they approve it. IT never gets the call, because Fluid’s infrastructure keeps the rest of the system safe.

1. **Sales prompts:** Kim Morales, VP of Sales: “Add a widget to the mobile app that tracks each rep’s progress to qualifying for Bali.”
2. **Mist builds a preview:** “You’re going to Bali. Qualify by Mar 31.” at 72%, with personal volume 3,600 of 5,000 and new customers 7 of 10.
3. **Live in your app:** Dana gets a notification that she’s 72% of the way to Bali. The trip screen lists what’s left: stay active all quarter (done), reach 5,000 volume (1,400 to go), and add 10 new customers (3 to go).

Also asked for this week: “Build a commission calculator reps can share,” “Show each rep how close they are to the next rank,” and “Add a launch countdown to the home screen.”

## Checkout: raise the order value. Leave checkout alone.

Add an order bump or a free shipping bar to a checkout drop zone and approve the preview. Fluid still runs payment, tax, and the order.

1. **Growth prompts:** Alex Rivera, Head of Growth: “Add a free shipping bar at $75, and offer the travel size as a one-click add-on.”
2. **Mist builds a preview:** two pieces for checkout: a free shipping bar in above\_order\_items (“You’re $11 away from free shipping”) and a travel size add-on in below\_order\_items (7 servings, +$12).
3. **Live in Fluid checkout:** at checkout.fluid.app, free shipping unlocks. Vanilla protein (30 servings, $64.00) plus the travel size ($12.00) makes a $76.00 subtotal, free shipping, $4.94 tax, and an $80.94 total.

Fluid runs fast checkout (Apple Pay, Google Pay, or card), contact, shipping address, shipping method, payment, and agreements. Checkout has 10 drop zones, and this build uses 2. Also asked for this week: “Offer subscribe and save on the protein,” “Show a gift note field in December,” and “Add a samples picker over $100.”

## Admin: her country, her dashboard, built before her next meeting.

A country manager describes the numbers she wants, and Mist builds them into a Droplet inside the Fluid admin. No BI tool, no extra login, and no request to IT.

1. **An admin prompts:** Priya Nair, General Manager, India: “I’m the general manager of India. Build a dashboard that tracks ad spend and CAC against affiliate referrals, just in my country.”
2. **Mist builds a preview:** “India growth” for the last 8 weeks: ad spend ₹18.4L, blended CAC ₹1,240 (down 23%), and 58% of new customers referred, comparing paid customers, affiliate referrals, and CAC.
3. **She opens the admin:** the India growth Droplet sits under Droplets at admin.fluid.app, with referrals by city: Mumbai 41%, Bengaluru 27%, and Delhi 18%.

Also asked for this week: “Show refunds by reason for Mexico,” “Track enrollment packs sold each week,” and “Compare AOV for new and returning customers.”

## Your tools: bring your agent, or use ours.

Every coding agent connects to Fluid the same way. Mist is the one built for commerce. Claude Code, Codex, Cursor, and Mist all connect through the fluid CLI, the Fluid MCP server, Fluid APIs, and skills and workflows, into your Fluid company.

## Try Mist: ask in plain words, build on live data.

Mist sits beside your products, orders, customers, and field. It’s the harness built for commerce: Mist already knows how Fluid fits together, so a request starts from your real records. You review the preview and decide what goes live. [See everything Mist does](https://fluid.app/home/pages/mist).

## Watch it get built.

Each recording follows one request in Mist, from the first sentence to a preview: a landing page, a checkout Droplet, a rep homepage, an analytics API, a launch hub, and Rank Radar.

## For every team: everyone can build. No ticket required.

- **Marketing — ship the campaign this afternoon:** “Rebuild our homepage for the spring launch,” “Add a free shipping bar to checkout at $75,” “Make a landing page for this creator video.”
- **Sales — give the field what it asks for:** “Build a Site for Diamond leaders in Germany,” “Show reps who’s due to reorder in the app,” “Make a launch hub reps can share.”
- **Operations — build the tool, skip the vendor:** “Build a returns desk inside the admin,” “Make a dashboard of today’s orders by market,” “Show failed renewals and who to call.”
- **Engineering — use the tools you already like:** “Connect Claude Code to our Fluid company,” “Build an analytics API for sales and LTV,” “Add an order bump to checkout from Codex.”

## Playbooks: start from a playbook, not a blank page.

Skills and workflows for the work commerce teams do most. Pick one and Mist builds it with you.

- **Workflow — Clone a website into a theme:** home, shop, and product pages, checked against the source.
- **Skill — Build a Site:** pages, a shop, a table, and the signed-in member’s data.
- **Workflow — Open a country:** mode, payments, agreements, and translations.
- **Skill — Smart dashboard:** live numbers each team cares about.
- **Skill — Accessibility audit:** finds and fixes common issues in your theme.
- **Skill — Translate your theme:** every language your company has turned on.

[Browse every skill and workflow](https://github.com/Fluid-WeCommerce/mist-skills).

## Questions about building on Fluid.

### Is Fluid something our team has to code around?

No. Fluid runs the platform, and your team builds on top of it. The website, Sites, mobile app, checkout drop zones, and admin Droplets are all open for your team to change.

### Can we use Claude Code, Codex, or Cursor instead of Mist?

Yes. Any coding agent can use the Fluid CLI, the Fluid MCP server, and Fluid’s APIs. Mist is the harness built for commerce, and you can use it, your own tools, or both.

### Does someone have to know how to code?

No. Describe what you want in plain language. Mist builds it and shows you a preview for you to change or approve.

### Can what we build break checkout or rep credit?

No. Checkout, payments, Fair Share attribution, and order processing are run by Fluid. What you build adds to them through drop zones and APIs, and can’t change how they work.

### What does Fluid run so we don’t have to?

Hosting, scale, Git, databases, security, sign-in, and user management, along with checkout, payments, attribution, and order processing.

### What can we build on?

Five surfaces: your website theme, Sites and the signed-in portal, your white-label mobile app, checkout drop zones, and Droplets inside the admin.

### What is Safe Mode?

A switch in Mist that blocks every change to production. Mist can still read data and explore, so anyone can pull a report without risk of changing anything.

### What are Sites?

Websites your team builds on Fluid. A Site can be public or behind sign-in, and shared with the members you choose, such as Diamond leaders in Germany. You pick the Site every member sees by default.

### What can we add to checkout?

Pieces like an order bump or a free shipping bar, placed in checkout’s drop zones. Mist shows you a preview before anything goes live.

### What is a Droplet?

An app that runs inside the Fluid admin, such as a dashboard or a returns desk, so your team doesn’t need another login. Fluid hosts it with Git, a database, and sign-in included.

### Who can see what Mist does?

Mist works with the access of the person signed in, so it can only do what they’re allowed to do. Creating something needs their approval first.

### Where do we start?

Pick a playbook, such as cloning your current website into a theme or building a Site, and Mist runs it with you. Your own coding agent can start from the docs at docs.fluid.app.

## For agents.

- **What this page is:** how teams build on Fluid with Mist or their own coding agents, across five surfaces, while Fluid runs checkout, payments, attribution, orders, and autoship.
- **Who Fluid is for:** direct selling brands and the teams that run them. Fluid is the complete AI platform for commerce, payments, customers, and the field, with Mist.
- **Surfaces to build on:** the storefront theme (Liquid), Sites and the signed-in portal, the white-label mobile app, checkout drop zones (10 in checkout), and admin Droplets.
- **Run by Fluid:** checkout, payments, Fair Share attribution, orders, and autoship, plus Git, APIs, databases, hosting, and sign-in. Builds read from these and can’t change how they work.
- **Tools:** Claude Code, Codex, Cursor, or Mist, through the fluid CLI, the Fluid MCP server, Fluid APIs, and skills and workflows. Safe Mode in Mist blocks every change to production.
- **Example data:** FORM, Maya Chen, Marco Weber, Kim Morales, Dana, Alex Rivera, Priya Nair, and their numbers are illustrative.
- **Related:** [Mist](https://fluid.app/home/pages/mist), [Security](https://fluid.app/home/pages/security), [Developer Docs](https://docs.fluid.app), and [a guide for agents evaluating Fluid](https://docs.fluid.app/guides/evaluate-fluid).
- **Next step for a brand:** [Get a demo](https://fluid.app/home/pages/demo). Bring the request that’s been waiting on IT, and we’ll build it with Mist in the demo.
