Cloudflare Pages

Deploy a static site's build output to Cloudflare Pages with wrangler (installed as a dev dependency, run through bunx), covering production deploys from the default branch, preview deploys for pull requests, and headers and redirects config.

Category: deploy

In your existing repository

Ask your agent to check compatibility, follow this fragment’s brief, and verify the resulting project. What happens next

Applies to:: astro-blog

Add to your project

Paste the prompt into the coding agent working on your project.

View prompt

Add the cloudflare-pages fragment to this existing repository. 1. Run npx @steamfield/stacks show cloudflare-pages --json and check that it fits the project. If it does not, explain why before changing files. 2. Run npx @steamfield/stacks add cloudflare-pages and follow the brief it prints. 3. In this repository, run npx @steamfield/stacks verify. Fix failures without weakening or skipping verification steps. 4. Summarize what changed and the verification result. Quote published stats only when they are available, including their interval and sample size. The stacks docs, written for agents, are at https://stacks.steamfield.io/llms.txt.

Or use the terminal

npx @steamfield/stacks add cloudflare-pages

Verify steps
Step	Phase	Layer	Command

No additional verify steps declared. Run the project’s existing verification after applying the brief.

Use with a new stack

Starting fresh instead? These stacks support this fragment.

astro-blogoptional
npx @steamfield/stacks new astro-blog --with cloudflare-pages

Files

This fragment supplies instructions rather than project files.

Usage

Among stacks projects in the 28 days through 30 Oct 2026: 435 projects; 69% reached a green verify (64–74%, n=275).

Weekly projects by stack

Projects whose final fragment set included this fragment, grouped by stack.

12 weeksAvailable history

astro-blog

astro-blog

Stacks projects per UTC week through 30 Oct 2026. Published stack counts only.

Data table

Week ending	Stack	Projects
5 Jul 2026	astro-blog	20
12 Jul 2026	astro-blog	30
19 Jul 2026	astro-blog	50
26 Jul 2026	astro-blog	70
2 Aug 2026	astro-blog	50
9 Aug 2026	astro-blog	55
16 Aug 2026	astro-blog	90
23 Aug 2026	astro-blog	60
30 Aug 2026	astro-blog	85
6 Sept 2026	astro-blog	85
13 Sept 2026	astro-blog	80
20 Sept 2026	astro-blog	115
27 Sept 2026	astro-blog	120
4 Oct 2026	astro-blog	95
11 Oct 2026	astro-blog	115
18 Oct 2026	astro-blog	115
25 Oct 2026	astro-blog	115

By stack

How often this fragment stays in a default composition, or gets attached as an option.

astro-blog

Optional · attached17%

435 projects including the fragment

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table

Stack	Projects	Role	Share
astro-blog	435	Optional · attached	17%

Green rate with and without it

This compares projects; it isn't an effect of the fragment.

astro-blog

With

69%64–74%, n=275

Without

69%67–72%, n=1,355

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table

Stack	With	Without
astro-blog	69% (64–74%, n=275)	69% (67–72%, n=1,355)

Often used with

Co-occurrence above the baseline, within a stack. Required fragment pairs are excluded.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.