Static assets Worker routing

Static assets Worker routing

Serve static assets through a minimal Worker while keeping API routes isolated.

What it does

This skill keeps the Worker small. Static content comes from Wrangler assets, while the Worker only handles a few read only endpoints.

Use it when

• The site is mostly static.
• You need an API seam for search or future read only data.
• You want a deploy path that stays simple.

Guardrails

• Do not add storage in v1 unless it is clearly required.
• Keep API routes read only by default.
• Let assets serve first unless the route must be handled by the Worker.

Notes

The goal is a clean split: static files for pages, Worker code for the small parts that really need logic.