> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/prompting/debugging-with-prompts.md).

# Debugging with Prompts

***

{% stepper %}
{% step %}

### Clearly Describe the Issue

Be specific about what’s going wrong.
{% endstep %}

{% step %}

### Share Context

Add a screenshot or image of the issue, or paste the exact error message into the prompt box.
{% endstep %}

{% step %}

### Ask for a Targeted Fix

Request a specific solution or explanation.
{% endstep %}

{% step %}

### Follow Up as Needed

Continue the thread with updated prompts if new errors appear.
{% endstep %}
{% endstepper %}

***

### Tips for Effective Debugging

* Focus on one issue per prompt.
* Share the full, unedited error message.
* Test the fix, then provide any new errors to continue debugging.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/prompting/debugging-with-prompts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.