Supabaseintermediate
Add File Uploads
Private file storage with type and size limits, and access checked per request.
When to use it
Documents and images
Lovable Prompt
Add file uploads to [FEATURE]. Requirements: - Store files in a private bucket. Do not use public URLs. - Restrict allowed file types to [LIST] and a maximum size of [SIZE]. - Validate the type and size on the server, not just in the browser. - Generate short-lived access links when a permitted user requests a file. - Record each upload against the owning user and record in the database. - Show upload progress, and handle failed uploads with a retry. Acceptance criteria: another signed-in user cannot open my file, and a signed-out visitor cannot either.
Build your version of this prompt
Fill in your details and the prompt below updates as you type. Anything you skip stays as a square-bracket placeholder so you can see what's still missing.
Your prompt
Add file uploads to [Feature]. Requirements: - Store files in a private bucket. Do not use public URLs. - Restrict allowed file types to [List] and a maximum size of [Size]. - Validate the type and size on the server, not just in the browser. - Generate short-lived access links when a permitted user requests a file. - Record each upload against the owning user and record in the database. - Show upload progress, and handle failed uploads with a retry. Acceptance criteria: another signed-in user cannot open my file, and a signed-out visitor cannot either.
3 fields still empty — the prompt works better when they're filled in.
How to use this prompt
- Fill in the fields above — plain language beats jargon.
- Copy the prompt and paste it into Lovable as a single message.
- Let it finish before you send anything else, then read what changed.
- If the result is close but not right, describe the difference rather than restating the whole prompt.
Suggested follow-up prompt
Review what you just built for Add File Uploads. 1. List anything you changed that I did not ask for, and undo it. 2. Check it works on a 375px-wide phone screen: no horizontal scrolling, tap targets at least 44px. 3. Confirm every form shows a clear error and a clear success state. 4. Tell me in plain language what is still missing before this is safe to publish. Do not add new features in this step.
Why it works
It makes privacy and server-side validation explicit requirements with a testable acceptance criterion.
Was this prompt helpful?
