Questions & conversation

Seven capabilities read and respond without ever changing your site. The signal that selects them: your message reads as a question or conversation, not a command — ending with ? is the strongest cue.

Project questions

“what color is the footer?” · “which page is the longest?” · “какой тут шрифт?”

Genesis reads your project’s actual files and answers in a couple of seconds with the concrete value — a hex code, a font name, a page list. Select an element first and the question is answered about that element specifically.

The answer carries an Ask badge, and when it describes something doable, a Build this now chip — one click turns the answer into the actual change.

Web questions

“how do I integrate Stripe?” · “what image size is best for OG tags?”

When the answer needs outside knowledge, Genesis searches and reads the web, then answers with concrete, sourced information. Slower than project questions (it’s actually researching), and still read-only.

Suggestions & variants

“give me some options for the hero” · “что посоветуешь?” · “which is better, X or Y?”

Genesis proposes 3–5 concrete variants as clickable chips. Click one and it’s applied as a real edit; or type your own take. Great for when you know something’s off but not what you want instead.

Clarifications

When a message is genuinely ambiguous, Genesis asks a short question — often with answer chips — instead of guessing. One tap and the work continues. The cheapest way to avoid this: phrase the request specifically in the first place.

Small talk & the fallback

Greetings and off-topic chat get a friendly short reply, no project touched. And if a message matches nothing at all, Genesis says so and asks you to rephrase — that’s the safety net at the very bottom of the routing.

The one habit worth keeping

End questions with ? and phrase edits as commands. “can you make the header sticky?” reads as a question — “make the header sticky” is the edit.