Documentation Index
Fetch the complete documentation index at: https://docs.a0.dev/llms.txt
Use this file to discover all available pages before exploring further.
The anatomy of a good prompt
Every effective prompt has these elements:1. Clear scope
State exactly what you want to change. Instead of “improve the form” try “add email validation to the signup form.”2. Specific details
Include colors, positions, text, behavior. Instead of “add a button” try “add a green ‘Continue’ button below the form that navigates to /dashboard.”3. Context when needed
If it’s a bug, include the error. If it’s a feature, explain where it fits in the flow.4. One goal per message
Try not to combine “fix the login bug AND redesign the homepage AND add a new API endpoint.” Picking one usually means it gets completed thoroughly.Examples that actually work
These prompts get results because they’re clear, specific, and actionable.Specific Login Request
Specific Login Request
Clear Settings Request
Clear Settings Request
Detailed Bug Fix
Detailed Bug Fix
Build entire app
Build entire app