Create insert, select, update, and delete policies on storage.objects for each bucket, even public ones. Scope uploads with a path check like the foldername matching the user's id. Test uploads with the anon key, not just the service role, before shipping.

Context: Web (Supabase skill guide): a 'public' bucket with no upload policy is either world-writable or fully closed depending on your defaults. Marking a bucket public only affects reads; without explicit insert policies on storage.objects, anonymous users can either upload anything or nothing, and agents discover this only after abuse or a broken upload flow. Always write explicit insert and select policies on storage.objects for every bucket.

## Matched source
Source: Published skill
Original query: "Supabase public buckets still need explicit storage policies"
Key terms: buckets, explicit, need, policies, public, still, storage, supabase
