ElmonyDocs

Guides

Debugging

Great prompting skills make debugging with AI dramatically easier. If you haven’t yet, read the Chatting guide for core prompting tips, then use the strategies below when errors pop up.

Prompting tips

Describe the issue clearly

Imagine you're handing the bug to a teammate: include the button you clicked, what you expected, and what actually happened.

Too vague

“Fix broken app.”

Better

“After I click the sign-up button, the UI goes blank instead of redirecting to the dashboard.”

Include detailed error messages

Copy/paste stack traces or UI errors directly into the chat. Many errors have a “Fix with AI” button, but you can always paste them manually.

No error message?

Describe what you see (“After logging in, the screen stays empty”) and ask Elmony to add error handling or surfacing toasts. Once errors surface, paste them back to get precise fixes.

Use Bug Finder first

Open Bug Finder in Builder's right-side workspace and run a check. It combines static, runtime, interaction, and TypeScript findings, groups them by file, and lets you filter source and preview problems. Select the findings you want to address and send them to Builder as a focused fix request, then recheck the project.

Bug Finder is a diagnostic aid, not proof that every flow works. Reproduce the original problem in Preview after each fix and verify the affected user journey yourself.

Example workflow

Suppose the Sign-in button throws a generic failure. Prompt something like:

“Add error handling to the sign-in flow and show detailed error toasts.”

After Elmony adds logging/toasts, reproduce the issue, copy the specific error message, and ask it to address that exact failure.

Workflow tips

  • Test often + use undo: Preview major flows every few prompts. If something breaks, undo via the Versioning guide recommendations, then retry.
  • Try another model: Re-running the same request with another configured model or subscription agent can produce a different approach. Restore the last working version first when the earlier attempt changed project files.
  • Manage context: Use Smart Context or manually select only the relevant files. If a long chat becomes noisy, start a focused new chat and include a concise summary of the current problem.