Describing what you want

Prompting

Everything MaShop builds starts as a sentence you type in the chat.

The quality of what comes back is decided here, before any model runs. This page describes what MaShop actually reads, what it asks you when it cannot guess, and what it forgets.

What travels with your message

Your message never travels alone. MaShop sends with it:

• the project card: name, type, number of items, categories, currency and language;
• the rules you asked MaShop to remember on this project;
• your pinned objective, if you set one;
• the last twenty messages of the current thread, capped at 12 000 characters.

The project language is sent as the target language for generated content.

Say what the change touches

MaShop sorts every message by radius of impact, not by length.

A long message about a single button is still a small job. A request to rebuild the whole site is a large one. Any request to create a site or an app from a description is always treated as the largest.

So name the page, the section or the file. Change the hero on the home page routes better than make it nicer. Only the first 2 000 characters of your message reach that sorter, so put the target in the first lines.

When MaShop cannot guess, it asks

Rather than invent a fact, MaShop can answer with a card. It holds one to three questions, each offering up to three options. The turn stops there.

Continue sends your answers as your next message. Skip tells MaShop to pick what is most relevant, without inventing your contact details.

Pin the objective once

The /goal command pins an objective for the project, up to 500 characters.

/goal "Sell handmade soaps in France, delivery in 48h"
/goal          shows the current objective
/goal clear    removes it

The objective is injected at every turn with the highest priority. When a later message conflicts with it, MaShop asks before drifting. The command runs locally: no model call, no credits.

Ask MaShop to remember a rule

Telling MaShop to remember your brand colour, your tone, or something it must never do is a real instruction. It is stored on the project and read back in later conversations. Four kinds are kept: brand, preferences, forbidden, and context.

Attaching images

• Two ways: an image from your device, or an image address that MaShop fetches for you.
• Images are converted to WebP in your browser. 5 MB per file.
• The input lets you attach five images. The server accepts four. The fifth is dropped in silence, with no error and no notice.
• Accepted formats: WebP, PNG, JPEG, GIF.
• Any message carrying an image is routed to the model that reads images, whatever you had selected.

What the chat forgets

The Code thread and the Automations thread never share memory. Neither one reads the other's turns.

A long thread does not make MaShop remember more. A fresh conversation with a clear brief beats a hundredth follow up.

The exact ceilings on a conversation, and on a single turn, are listed in How MaShop works.

What is refused before anything is spent

Two refusals land before any model call and before any credit is reserved.

• Sites for explicit pornographic content, illegal drugs, firearms, or dark web goods.
• A missing connection. Without GitHub and Supabase, MaShop explains instead of building.

Two other gates apply: the rate limit on messages, described in The workspace, and the fact that a viewer cannot use the chat at all.

What a message costs

Credits are reserved before the call on an estimate, then adjusted to what the provider actually consumed. A message that returns nothing costs zero: the reservation is cancelled, not confirmed. A generation you stop, or one whose connection drops, is cancelled the same way.