What problem does it solve? Applications on Netlify often need to persist unstructured data — user file uploads, form submissions, generated artifacts from background functions — without provisioning a database. This Skill provides the correct patterns for using the @netlify/blobs key-value store from Functions, Edge Functions, and Build Plugins, while avoiding common pitfalls like treating blobs as transactional storage or leaking production data into deploy previews. ## Core Features & Use Cases - Object storage operations: set, setJSON, get, getWithMetadata, list, delete, and deleteAll with metadata, ETag-based conditional reads, and atomic writes via onlyIfNew/onlyIfMatch. - Store scoping guidance: choose between site-scoped stores (shared across all deploy contexts) and deploy-specific stores via getDeployStore for isolated, per-deploy data. - Build-time and client patterns: write blobs from build plugins, upload files at deploy time via .netlify/blobs/deploy, and implement client-side expiration since blobs have no TTL. - Use Case: A user uploads a profile image through a form; a Netlify Function stores it in a blobs store with geolocation metadata, and a later request reads it back with an ETag check to serve a cached copy. ## Quick Start Ask the agent to write a Netlify Function that saves an uploaded file to a Netlify Blobs store and reads it back by key.
