deploy
Skill0 starsChanged 12 days agoMITView on GitHub
Put the site online with Cloudflare Pages by connecting the GitHub repo. No API tokens needed. Covers the first deploy, custom domains and the contact form.
- Reads credentials
- Commits and pushes
161 other projects use a version of this.
Adopted by
Most recently taken up by
- krystaleicher/claude-skillstheir own version, first seen Nov 16, 2026
- KazKato91/roomi-claude-plugintheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- reloru/new-relotheir own version, first seen Nov 16, 2026
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
Other versions161 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 161
- ok-oldking/ok-wuthering-waves★ 8.6ksame name
- memovai/mimiclaw★ 5.8ksame name
- KingKongRobotics/jumper★ 3.1ksame name
- jhd3197/ServerKit★ 1.8ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- microsoft/power-platform-skills★ 1.2ksame name
- jazzyalex/agent-sessions★ 948same name
- awslabs/agent-plugins★ 943same name
- patrickjaja/claude-desktop-extra★ 761same name
151 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brandSkill
- new-postSkill
- new-team-memberSkill
- onboardSkill
- passionfruit-a11ySkill
- passionfruit-contentSkill
- passionfruit-designSkill
- passionfruit-perfSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 143 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
No template placeholders are left:
- Distinctive: line 35
If this finds anything, stop and tell the user what's missing in plain language.
- Very specific: line 81
Don't also set the CLOUDFLARE_PROJECT_NAME GitHub variable.
- Distinctive: line 89
Ask the user to open the address and check the home page, the contact page and the imprint.
- Distinctive: line 115
If they're happy with email, skip to Step 7.
- Very specific: line 153
The build fails in Cloudflare: ask the user to copy the last lines of the build log into this chat.
- Distinctive: line 155
The site shows old content: check the deployment finished in Deployments, then wait a minute and reload.
“Common” is measured: kept by at least 6 in 10 of the 143 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy to Cloudflare Pages
This skill puts the site online. Cloudflare connects to the GitHub repo and rebuilds the site on every merge to main. Pull requests get their own preview link.
How to work with the user
The user is usually not technical. Tell them exactly where to click, one step at a time, and wait for them to confirm. Do everything else yourself.
Never ask the user to paste passwords, API keys or tokens into this chat. Anything secret goes straight into the Cloudflare dashboard.
When to trigger
- User explicitly runs
/deploy - User asks about hosting, deployment, or "putting the site online"
Prerequisites check
Before starting, verify:
- The GitHub repo exists and has a remote (
git remote -v). If not, help the user create one first, because Cloudflare deploys from GitHub: usegh repo create, or have them create an empty repo at https://github.com/new and add it asoriginyourself. Then rungit push -u origin main, because a new repo has nomainto open a pull request against. - The site builds (
pnpm build). No template placeholders are left:
git grep --untracked -inE 'greenleaf|musterstra|musterstadt|hello@example\.com|\+49 123 456 789|DE123456789|platzhalter|is a placeholder|Brauche ich Programmierkenntnisse|Do I need programming skills|"98%"' -- src/content src/i18n src/data ':!src/data/faqs.ts' ':!src/content/blog'This repo is the template's own marketing site: its real FAQ asks the template's demo question, and its blog posts write about placeholders, so both are excluded.
If this finds anything, stop and tell the user what's missing in plain language. A public German site with a placeholder imprint or privacy policy is a legal risk. Only continue if the user says this is a test site and confirms it.
Step 1: Get the work onto main
Cloudflare publishes main. Commit any open changes on a branch, then get them merged:
gh auth statussucceeds, in a local session: open and merge a pull request withgh pr createandgh pr merge --squash.- Otherwise:
git push -u origin HEAD, then give the user this link to open and merge the pull request:https://github.com/<owner>/<repo>/compare/main...<branch>?expand=1.gh prdoesn't work in cloud sessions (CLAUDE_CODE_REMOTE=true).
Step 2: Cloudflare account
Ask:
"Do you have a Cloudflare account? The free plan is all you need."
If not:
"Sign up at https://dash.cloudflare.com/sign-up, then come back when you're logged in."
Step 3: Connect the repo
Guide the user:
"Now let's connect your site. In the Cloudflare dashboard:
- Open Workers & Pages in the left sidebar
- Select Create application, then the Pages tab
- Select Connect to Git (it may say Import an existing Git repository)
- Sign in to GitHub if asked, and pick your website's repository
Tell me when you see the build settings."
Then:
"Enter these settings:
- Project name: your company name in lowercase, like
my-company. This becomes your address,my-company.pages.dev- Production branch:
main- Framework preset: Astro
- Build command:
pnpm build- Build output directory:
distLeave everything else as it is, select Save and Deploy, and tell me the address it shows when it finishes. It usually takes a few minutes."
The build reads the Node version from .nvmrc and needs no environment variables.
Don't also set the CLOUDFLARE_PROJECT_NAME GitHub variable. That turns on the GitHub Actions deploy in .github/workflows/deploy.yml, and the site would deploy twice.
Step 4: Check the live site
Once the user gives you the address:
- Set
siteinastro.config.mjsto it, for examplesite: "https://my-company.pages.dev". Canonical links, the sitemap and social previews use this. - Ship that change the same way as Step 1.
- Ask the user to open the address and check the home page, the contact page and the imprint.
Tell them:
"Your site is live! From now on, every change I make goes on its own branch. Cloudflare adds a preview link to the pull request, so you can check it before it goes live. Merging publishes it."
Step 5: Custom domain (optional)
Ask:
"Do you want to use your own web address?"
If yes:
"In your Cloudflare project, open Custom domains and select Set up a custom domain. Enter your address, for example
www.example.com, and follow the steps. If your domain is registered somewhere else, you'll need to change a DNS setting there, and Cloudflare will show you what to enter."
Afterwards, update site in astro.config.mjs to the new address and ship it the same way as Step 1.
Warn the user about Cloudflare's own tracking features. Web Analytics, Zaraz and the Google tag gateway add scripts to pages from outside the repo, so they bypass the site's cookie banner. Leave them off unless they're set up to respect consent.
Step 6: Contact form (optional)
Ask:
"Right now your contact form opens the visitor's email app, which needs no setup. Do you want messages delivered straight to your inbox instead? You'd need a free Brevo account, and it takes about 15 minutes."
If they're happy with email, skip to Step 7.
Otherwise, guide them through these one at a time:
1. Spam protection. In the Cloudflare dashboard, open Turnstile and add a widget. Add your site's address, and also your
<project>.pages.devaddress so the form works on preview links. Keep that page open, because it shows a site key and a secret key.2. Email delivery. In https://app.brevo.com:
- Open Senders & IPs and add the address your messages should come from. Brevo emails you a link to confirm it, and nothing is delivered until you click it.
- Open SMTP & API, then API Keys, and create a key.
3. Settings. In your Cloudflare project, open Settings, then Variables and Secrets. Add these for Production yourself. Please don't paste them here.
| Name | Type | Value |
PUBLIC_FORM_ENDPOINT | Text | /api/contact |
PUBLIC_TURNSTILE_SITE_KEY | Text | The Turnstile site key |
TURNSTILE_SECRET_KEY | Secret | The Turnstile secret key |
BREVO_API_KEY | Secret | The Brevo API key |
CONTACT_SENDER | Secret | The sender address confirmed in Brevo |
CONTACT_RECIPIENT | Secret | The inbox that should receive messages |
4. Publish. Open Deployments, find the latest production deployment, and select Retry deployment. Then send yourself a test message through the form.
The PUBLIC_* values are built into the site, so they only take effect after that new deployment. To make the form work on preview links too, repeat the settings for Preview.
Step 7: Protect main (optional, for teams)
For a team, suggest requiring pull requests. In a local session with gh:
gh repo edit --enable-squash-merge --enable-merge-commit=false --enable-rebase-merge=false --delete-branch-on-mergeThen in GitHub, under Settings → Branches, add a rule for main that requires a pull request and passing checks.
Troubleshooting
The build fails in Cloudflare: ask the user to copy the last lines of the build log into this chat. Fix the cause and ship it. Check first that the build command is pnpm build, not npm run build, and that the output directory is dist.
The site shows old content: check the deployment finished in Deployments, then wait a minute and reload.
No preview link on a pull request: Cloudflare only builds pull requests from branches in the same repo. Check the project's Settings → Builds too.
The user can't find a button: Cloudflare's dashboard changes. Ask what they see on screen and adapt, rather than repeating the steps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

