Guides
Chatting
Give the agent a clear outcome, add relevant visual context, and verify the working result in the preview.
Use multiple chats
Elmony lets you create multiple conversations for one app. Start a fresh chat when a task needs clean context or when a thread has become too broad. Every chat works against the same local project, so code and version history remain shared.
Craft a detailed opening prompt
State the outcome, audience, constraints, and important states up front. Compare:
Too vague
“Build a landing page.”
Better
“Build a landing page for a focus-tracking browser extension. Add a headline, short explanation, email form, product illustration, three feature cards, and a testimonial section. Keep the existing color tokens and make every section responsive.”
Split unrelated work into separate prompts. Smaller, testable requests make it easier to spot regressions and restore a good version if needed.
Add context from the preview
Use Select component in the preview toolbar and click one or more visible elements to attach their component and source locations to your next message. Use the camera button to attach a screenshot when the problem is visual or spans several elements.
Explain what should change and what should stay untouched. Selected components and images improve context, but they do not replace a clear instruction.
Monitor every run
Auto-approve is enabled by default. Elmony approves code changes and runs them while the agent works, so follow the activity, inspect the summary and file diffs, watch the Console, and test the result in the preview.
If you prefer a confirmation step, disable Settings → Workflow → Auto-approve. With auto-approve off, review proposed changes before accepting them. If a run goes in the wrong direction, stop it, describe the correction, undo the change, or restore an earlier version.
What’s next?
Dive into the Debugging guide for strategies to diagnose issues when the output is not quite right, or open the Previewing guide for a tour of the Builder controls.