What problem does it solve? Applications on Neon Postgres often need file storage for uploads, avatars, and documents, but adding a separate provider like AWS S3 or Cloudflare R2 introduces extra accounts, credentials, and drift between files and database rows across environments. This Skill sets up S3-compatible object storage that branches alongside the database, keeping files and rows in sync across dev, preview, and production branches. ## Core Features & Use Cases - Branch-aware buckets: Declare private or public_read buckets in a neon.ts infrastructure-as-code file and provision them with neon deploy, with copy-on-write storage inherited by child branches. - Standard S3 tooling: Works with the AWS SDKs, boto3, the AWS CLI, and presigned URLs using injected AWS-standard environment variables, with path-style addressing enforced. - Files SDK integration: Provides a unified upload, download, list, copy, delete, and presign API through the files-sdk neon adapter. - Use Case: An agent generates an image, uploads it to the images bucket, stores the object key in a Postgres row on the same branch, and returns a presigned URL on read, so a preview branch inherits a consistent snapshot of both rows and files. ## Quick Start Ask the AI to set up a Neon Object Storage bucket for user uploads and wire an S3 client to the injected environment variables.
