What problem does it solve? Serving CSS, JavaScript, fonts, and build artifacts through your application server wastes bandwidth and slows global delivery. This Skill guides you through uploading static assets to Tigris public buckets with correct cache headers and wiring your framework's asset URL to the Tigris CDN endpoint. ## Core Features & Use Cases - Cache Header Configuration: Set Cache-Control: public, max-age=31536000, immutable on content-hashed assets and short-lived headers on mutable files via the Tigris CLI or SDK. - Framework Integration Guides: Step-by-step configs for Next.js (assetPrefix), Remix (Vite base), Rails (config.asset_host with S3 sync), Django (collectstatic with S3StaticStorage), Laravel (ASSET_URL with S3 disk), and Express (redirect pattern). - Cache-Busting Strategies: Compare content-hashed filenames, query strings, and directory versioning to pick the right invalidation approach. - Use Case: After running next build, upload .next/static/ to a public Tigris bucket with immutable cache headers, then set assetPrefix to the bucket URL so all static assets are served from Tigris edge locations. ## Quick Start Ask the assistant to deploy your Next.js static assets to Tigris with immutable cache headers and configure the asset prefix.