# Add These to Every Prompt for Better Outputs

#### The more context you give, the more production-ready the result.

* Data sources Specify where the data comes from — wallet address, API, database, or user input.

* Authentication State whether users need to log in and how — email, wallet, OAuth.

* UI direction Describe the layout, tone, and style — "clean and minimal", "dark mode", "dashboard layout with sidebar navigation".

* Error handling Ask for it explicitly — "include error states for failed transactions" or "handle empty states when no data is available".

* Real-time requirements State if data needs to update live — "refresh wallet balance every 30 seconds" or "show live price feed".

* Payment and monetization Specify if the app needs to charge users, accept USDC, or integrate Stripe.


---

# 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.eitherway.ai/prompting-guide/eitherway-prompting-guide/add-these-to-every-prompt-for-better-outputs.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.
