# eShop

> Coming soon. eShop plans the store, product pages, and catalog copy. The Coder builds the shop after you Approve. It never takes a payment.

Status: Coming soon

> [!SOON]
> eShop is Coming soon. This page describes what it will do when it opens, so you can plan ahead. Today the [Coder](/docs/personas/coder) is the one available persona.

eShop is the assistant that plans your store. It turns a shop idea into pages, a catalog outline, and the words a customer reads. The Coder builds the shop after you Approve. Marketing writes the campaigns. The Accountant handles payments. Support writes the FAQ and the product manual. In chat, address it as "eShop," or `@eshop`.

## What it will do

- Write a store plan: what the shop sells, the pages, and what the Coder builds.
- Draft product pages from lists you provide.
- Outline the catalog and the collections.
- Draft the words on the order page and the customer-facing notes for shipping and returns.
- Check what is ready before the store opens. A checklist is not a launch.

## Skills

| Skill | What it will do, in plain words |
| --- | --- |
| Store plan | The first win. Turns a shop idea into pages and a handoff the Coder can build. |
| Product page | Drafts one product page from facts you gave. It does not invent stock. |
| Catalog outline | Groups your product list into collections. |
| Order page copy | Writes the words a customer sees while they place an order. |
| Launch checklist | Lists what is ready and what is still missing before the store opens. |
| Store policies draft | Drafts the customer-facing notes for shipping and returns, and leaves a gap where a rule was not given. |

More skills arrive from StellarFirm's skill library without an app update, such as a collection page, a product photo brief, a store announcement, and an inventory note. The skills above stay available even when the library cannot be reached.

## Integrations

| Integration | Status | Used for |
| --- | --- | --- |
| [Gmail](/docs/integrations/gmail) | Coming soon | One announcement draft |
| [Google Calendar](/docs/integrations/google-calendar) | Coming soon | A launch review |
| [Google Drive](/docs/integrations/google-drive) | Coming soon | Catalogs and product sheets |
| [Notion](/docs/integrations/notion) | Coming soon | The catalog notes |
| [Slack](/docs/integrations/slack) | Coming soon | Chatting and sharing drafts |

## Example goals

- Plan an eShop for the products we already sell.
- Write the product page for [product].
- Outline the catalog from the list on Drive.
- Tell me what is still missing before we open.

## Prompts for when it opens

```prompt title="Plan the store"
eShop, plan a store for [what you sell]. List the pages and what the Coder should build. Do not open the store.
```

```prompt title="Write a product page"
eShop, write the product page for [product] from the facts I gave. Leave a gap where a specification is missing.
```

```prompt title="Outline the catalog"
eShop, outline the catalog from [folder or list]. Group the products into collections.
```

```prompt title="Write the order page"
eShop, write the words on the order page. Leave shipping rules blank where I have not given them.
```

## What it never does

> [!IMPORTANT]
> Every write waits for your Approve. eShop does not publish a page, save a file, or hand the build to the Coder until you say so.

It never takes a payment and it never opens the store itself. It never invents a product, a count, or a delivery promise. Campaign mail belongs to Marketing. Payments belong to the Accountant. The build belongs to the Coder.

---

Source: https://stellarfirm.ai/docs/personas/eshop