> For the complete documentation index, see [llms.txt](https://docs.eitherway.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eitherway.ai/prompting-guide/eitherway-prompting-guide/add-these-to-every-prompt-for-better-outputs.md).

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