# Getting the AI to do what you want

> The Genesis agent understands plain language — no bracket tags or syntax. Just describe the outcome; here's how to phrase power features so it nails them.

Source: https://knowledge.estage.com/building/steering-with-tags/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
The Genesis chat is an **AI agent**. It reads what you want from a normal sentence and picks
the right tool itself — a fast style edit, a whole new section, a real backend, an editable
catalog, analytics, animation. **You don't need any special syntax.** Describe the outcome and
it does the rest.

> **No more tags:** 
Earlier versions used bracket tags like `[product list]`, `[tracking]`, or `[estage-dedicated]`
to force a specific tool. Those are gone — the agent understands your intent directly. Anywhere
you used to type a tag, just say what you want in plain words.

## The one habit that matters: be specific

The agent is smart, but the clearer the outcome you describe, the better it hits it. Name the
thing and the intent:

| Instead of a tag, just say… | And you get |
| --- | --- |
| *"add an editable product catalog — a flower shop, 12 bouquets with photo, name, price"* | A data-driven catalog you edit from a panel |
| *"add my Google Tag Manager GTM-ABC1234"* (or *"add my Meta Pixel 123…"*) | Analytics / ad pixel wired in |
| *"build a members area with login and a feed people can post to"* | A real backend — database, accounts, realtime |
| *"let me edit these testimonials from the sidebar"* | Live, no-AI-turn editing controls |
| *"when the contact form is submitted, send it to this webhook: https://…"* | A Zapier / Make / webhook hand-off |
| *"add a support chatbot that knows our shipping policy"* | In-site AI |
| *"add a video grid from my Estage library, 3 per row"* | An Estage element |
| *"build a landing inspired by stripe.com, but in my brand"* | A page designed from a reference |
| *"animate the page — parallax, scroll reveals, hover effects"* | Motion added tastefully |
| *"undo that"* | The last change reverted |

## Three levers for great results

1. **Say the outcome, not the mechanism.** *"a feed members can post to"* beats *"add a
   div."* The agent chooses tables, components, and wiring for you.
2. **Select first for precise edits.** Click an element in the preview, then *"make this
   bigger"* or *"remove this"* applies to exactly that element — no ambiguity. See the
   [visual editor](/visual-editor/).
3. **Attach a reference** — an image or a URL — when you want it to match a look. Say whether
   you want an inspired take or a faithful copy.

## When something needs setup

A few features rely on something being configured first — a
[Dedicated Cloud](/cloud/) for backends, [payment gateways](/project-settings/payments/) for
checkouts, a [connected service](/connectors/) for Telegram/Notion. You still just ask for the
feature; if a prerequisite is missing, the agent tells you what to enable and where.

> **Note:** 
Being specific is the whole trick. You're not learning a command language — you're briefing a
capable agent. The more concrete the result you describe, the more reliably it delivers it.