What to include
| Item | Why we ask |
|---|---|
| App URL or repo link | So we can see the problem and the code |
| What tool built the app (Lovable, Bolt, Replit, v0, Cursor, Windsurf, Claude Code, other) | Tells us the likely stack |
| What is broken, in your own words | Your description of the problem |
| Exact error message | Copy the full text from the browser console, terminal, or build log |
| Steps to make it happen | Example: open /signup, enter email, press Create, see blank page |
| What should happen instead | Defines "fixed" |
| Hosting and database (Vercel, Netlify, Cloudflare, Supabase, Firebase, not sure) | Where settings may need to change |
| Screenshot or screen recording (optional) | Saves a round of questions |
| Anything we must not touch (optional) | Files, features, or styling to leave alone |
| Add-on (launch posts) only: what the app does, who it is for, launch date, links | Raw material for the posts |
Please do not send passwords or real customer personal data. By requesting a fix you confirm you own the code or have permission to share it.
How to give us code access
- Open your repo on GitHub, then Settings, then Collaborators.
- Click Add people and enter the GitHub username we send you in our reply.
- Choose write access (we only ever push to a new branch). Remove us any time when the job is done.
No GitHub? Reply with a zip of your project instead (without your .env file).