# 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: 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:

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

The question should be specific, self-contained, and written in natural language.
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.