Steering the AI with tags

Genesis picks one approach per message. For everyday edits, it infers the right one from your words. But for specialized features — a backend, a product catalog, analytics, live controls — inference can be ambiguous, and a plainly-worded request may fall into the generic “edit something” path instead of the dedicated tool that builds it properly.

Bracket tags solve this. A tag is an explicit instruction: “use this exact tool.” When you start your message with a tag, Genesis routes straight to that tool and skips all guesswork.

The core idea

You can’t force the AI to follow a rigid template, and it can’t keep every feature in mind perfectly on every message. A tag removes the guessing entirely — it’s the difference between hoping it understands and telling it exactly what you want.

When to reach for a tag

Use plain language for:

• Visual tweaks (“make the button green”, “bigger heading”)
• Content and layout (“add a testimonials section”, “rewrite the hero copy”)
• Questions (“how do I add a custom domain?”)

Use a tag for:

• A real backend (database, login, realtime) → [estage-dedicated:]
• A data-driven product catalog → [product list]
• Analytics / ad pixels → [tracking]
• Making a component’s options editable → [Live Controls]
• An Estage element (Video, Courses, etc.) → [Estage <Name>:]
• Undoing the last change → [undo]

The tags

[estage-dedicated:] — backend features

The most important tag for serious functionality. It hard-routes your request to the Dedicated Cloud backend builder, which plans your database tables, security rules, realtime, and server functions — then builds the UI on top.

[estage-dedicated: a community feed where members can create and like posts]
[estage-dedicated: a contact form that emails me each submission and stores it]
[dedicated: live chat with moderation]
[backend: user accounts with a private members area]

Aliases (all do the same thing): [estage-dedicated: …], [estage dedicated: …], [dedicated: …], [backend: …].

Why this matters

Anything that needs to store data, sign users in, or run server logic needs the backend builder. If you just ask “make a feed where people can post” without the tag, Genesis might build a pretty but non-functional feed (front-end only). The [estage-dedicated:] tag guarantees the real, working backend is set up. (Your project needs an active Dedicated Cloud — the tag will make sure of it.) Full guide: Building backend features with AI.

[product list:] — product catalogs

Builds a data-driven catalog: a structured list of products you can edit from a panel, instead of hard-coded cards the AI has to rewrite every time.

[product list]
[product list: flower shop, 12 bouquets with prices]
[products: car rentals with daily rates]
[product grid]

[product list], [product grid], and [products] are equivalent. The text after the colon is an optional hint about what to put in the catalog.

[tracking:] — analytics & pixels

Wires a tag manager or ad pixel into your site (the same plumbing as the Marketing Tags settings tab).

[tracking]
[tracking: GTM-ABC1234]
[pixel: add my Meta Pixel 1234567890]
[gtm]

[tracking], [pixel], [gtm], and [tag manager] all trigger it. You can also just write a clear sentence with an ID, like “add GA4 G-XXXXXXXXXX” — but the tag is the reliable way.

[Live Controls:] — make a component editable

Exposes a component’s options (things like items-per-row, a color, a toggle) as live controls in the editor sidebar, so you can tweak them without chatting each time.

[Live Controls]
[Live Controls: perRow, accentColor, showFilters]

The optional hint lists the specific options you want surfaced.

[Estage <Name>:] — Estage elements

Routes to a specific Estage product element. Replace <Name> with the element (case doesn’t matter):

[Estage Video: a video grid, 3 per row, with filters]
[Estage Courses: a paid course catalog]

[undo] — revert

Restores your project to the previous checkpoint.

[undo]
[revert]

How to write a tag

• Put the tag at the start of your message.
• Add a colon and a description for everything except the simplest cases: [estage-dedicated: what you want it to do].
• The description after the colon is where you give Genesis the details — be as specific as you’d be in a normal request.

Quick reference

| You want… | Type this | | --- | --- | | A backend (DB, login, realtime, server logic) | [estage-dedicated: …] | | A product catalog you can edit from a panel | [product list: …] | | Analytics or an ad pixel | [tracking: …] | | Editable component options in the sidebar | [Live Controls: …] | | An Estage element (Video, Courses, …) | [Estage Video: …] | | Undo the last change | [undo] |

Note

Tags are optional. Genesis works fine without them for ordinary edits. They exist for the moments when being explicit beats leaving it to inference — and for power features, that’s almost always.