deploy
Skill2 starsChanged 3 months agoMITView on GitHub
Deploys to Vercel. Verifies /audit passed. Helps configure domain, DNS, and secret storage. Offers Google Cloud Secret Manager as the recommended store for sensitive API keys. Post-deploy smoke test.
- Reads credentials
- Installs packages
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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- animationSkill
- auditSkill
- blocksSkill
- briefSkill
- buildSkill
- copy-analyzeSkill
- design-lockSkill
- iconsSkill
- inboxSkill
- mediaSkill
- mobileSkill
- refsSkill
- tokensSkill
- typographySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 6 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 143 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
After /audit with pass verdict.
- Distinctive: line 18
No uncommitted changes in git (user commits themselves — CLAUDE.md rule 5).
- Very specific: line 20
All env vars from brief/06-technical.md are configured wherever the user chose to store them (Vercel Dashboard, or Google Cloud Secret …
- Very specific: line 26
Read site/_audit-report.md, verdict must be OK.
- Very specific: line 27
Read brief/06-technical.md — domain, region, env vars.
- Very specific: line 28
Read brief/blocks/contact-form.md — which backend (affects env vars).
- Distinctive: line 44
Ask the user how to store sensitive keys: before writing anything to Vercel.
- Very specific: line 56
Only two values live in Vercel env vars: GCP_PROJECT_ID and GCP_SA_KEY_JSON (base64-encoded service account key).
- Distinctive: line 58
If the user picks Option B, walk them through:
- Distinctive: line 203
Do not commit: Do not run git commands. CLAUDE.md rule 5.
- Very specific: line 209
Do not change vercel.json without user request.
- Distinctive: line 210
Do not wire external services (Cloudflare Workers, Netlify redirect, etc.) without discussion.
- Distinctive: line 211
Do not deploy to staging and prod simultaneously — verify staging first.
- Very specific: line 212
Do not commit sa-key.json or any .env file — verify .gitignore covers them.
“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
Final step. Publishes the landing to production. DOES NOT RUN if /audit did not pass.
When to use
- After
/auditwith pass verdict. - Updates to an already-deployed landing (then the gate is only audit).
Requirements — HARD BLOCKING
site/_audit-report.mdexists with verdict = OK.- No uncommitted changes in git (user commits themselves — CLAUDE.md rule 5).
vercel.jsonpresent.- All env vars from
brief/06-technical.mdare configured wherever the user chose to store them (Vercel Dashboard, or Google Cloud Secret Manager — see Step 3a).
Process
Step 1. Verify readiness
- Read
site/_audit-report.md, verdict must be OK. - Read
brief/06-technical.md— domain, region, env vars. - Read
brief/blocks/contact-form.md— which backend (affects env vars).
Step 2. First deploy vs update
If first deploy:
- User installs Vercel CLI:
npm i -g vercel. - Init:
vercel(asks project, domain, etc.). - Configure secret storage (Step 3a).
- Configure env vars (Step 3b).
- Configure domain (Step 4): DNS at the registrar → Vercel.
If update:
vercel --prod(or via GitHub integration, if wired).
Step 3a. Secret storage choice
Ask the user how to store sensitive keys before writing anything to Vercel. Options:
Option A. Vercel env vars only (simplest, default)
- Secrets live in Vercel Dashboard → Settings → Environment Variables.
- Marked as "Sensitive" so they're write-only after creation.
- Trade-off: rotation is manual, audit log is Vercel Enterprise-tier, and multi-project secret sharing means duplicating values.
- Good fit for: single-landing projects, hobby projects, agencies with one client per Vercel team.
Option B. Google Cloud Secret Manager (recommended for production / multi-project)
- Secrets live in a central GCP project.
- IAM-controlled access, versioning, audit log out of the box, easy rotation.
- Vercel serverless functions read secrets at runtime via
@google-cloud/secret-managerusing a service account. - Only two values live in Vercel env vars:
GCP_PROJECT_IDandGCP_SA_KEY_JSON(base64-encoded service account key).
If the user picks Option B, walk them through:
- Create the GCP project (if none exists):
gcloud projects create <PROJECT_ID> --name="<Client name>" gcloud config set project <PROJECT_ID> gcloud services enable secretmanager.googleapis.com - Create each secret (repeat per key):
(Do NOT paste the real value into chat. User runs the command themselves in their terminal.)echo -n "<the-real-value>" | gcloud secrets create RESEND_API_KEY --data-file=- - Create a service account with read-only access:
gcloud iam service-accounts create landing-secret-reader \ --display-name="Landing Secret Reader" gcloud projects add-iam-policy-binding <PROJECT_ID> \ --member="serviceAccount:landing-secret-reader@<PROJECT_ID>.iam.gserviceaccount.com" \ --role="roles/secretmanager.secretAccessor" gcloud iam service-accounts keys create sa-key.json \ --iam-account=landing-secret-reader@<PROJECT_ID>.iam.gserviceaccount.com - Base64-encode the key file and store in Vercel:
Paste the base64 output into a Vercel env var namedbase64 -w0 sa-key.json # Linux # or [Convert]::ToBase64String([IO.File]::ReadAllBytes("sa-key.json")) # PowerShellGCP_SA_KEY_JSON. Also addGCP_PROJECT_ID. - Read secrets from a Vercel serverless function:
// api/send-form.js import { SecretManagerServiceClient } from '@google-cloud/secret-manager'; const credentials = JSON.parse( Buffer.from(process.env.GCP_SA_KEY_JSON, 'base64').toString('utf8') ); const client = new SecretManagerServiceClient({ credentials }); async function getSecret(name) { const [version] = await client.accessSecretVersion({ name: `projects/${process.env.GCP_PROJECT_ID}/secrets/${name}/versions/latest`, }); return version.payload.data.toString('utf8'); } export default async function handler(req, res) { const apiKey = await getSecret('RESEND_API_KEY'); // ... use apiKey } - Delete
sa-key.jsonlocally after upload — do not commit it. - After setup, the only Vercel env vars are
GCP_PROJECT_ID,GCP_SA_KEY_JSON, and non-sensitive config (FROM_EMAIL,TO_EMAIL,ALLOWED_ORIGIN).
Record the choice in site/_deploy-log.md under "Secret storage:".
Step 3b. Env vars checklist (if backend)
Show which variables must be set (Vercel Dashboard Production; or GCP Secret Manager if Option B):
From brief/blocks/contact-form.md:
- RESEND_API_KEY (Sensitive) ← from resend.com dashboard
- FROM_EMAIL ← e.g. orders@yourdomain.com
- REPLY_TO_EMAIL ← e.g. hello@yourdomain.com
- TO_EMAIL ← where the form submission lands
- ALLOWED_ORIGIN ← e.g. https://www.yourdomain.com
If Secret Manager (Option B):
- GCP_PROJECT_ID
- GCP_SA_KEY_JSON (Sensitive, base64-encoded)User fills these themselves. NEVER read secrets from local .env files or paste them into chat.
Step 4. Domain setup (first time)
- Vercel Dashboard → Domains → Add.
- Show required DNS records:
Arecord:76.76.21.21for apexCNAME:cname.vercel-dns.comfor www
- Pick redirect: www → apex or apex → www (see
brief/06-technical.md). - SSL — auto (Let's Encrypt).
Step 5. First deploy command
vercel login
vercel link
vercel --prodStep 6. Smoke test after deploy
Open production URL:
- Homepage loads in < 2 s?
- LCP good? (Lighthouse mobile.)
- Form submits? (Test submit with a test email.)
- Analytics working? (Open GA DebugView / FB Pixel Helper.)
- Cookie banner fires? (If applicable.)
- Open /privacy — link exists in footer?
- Mobile emulation — no battle-tested breakages?
Step 7. Post-deploy report
site/_deploy-log.md (append per deploy):
## Deploy 2026-08-08 16:00
- URL: https://www.example.com
- Commit: <hash>
- Region: fra1
- Secret storage: GCP Secret Manager (project: landing-clients-prod)
- Lighthouse:
- Perf: 95
- A11y: 100
- Best practices: 100
- SEO: 100
- Smoke test: pass
- Env vars: 3 in Vercel (GCP creds + non-sensitive), 5 in GCP Secret Manager
- DNS: propagated
- Notes: <anything unusual>Step 8. If it fails
Rollback: vercel rollback — return to the previous deployment.
Env var error → update in Vercel Dashboard or GCP → redeploy.
Code error → fix locally → rerun /audit → rerun /deploy.
Rules of behavior
- Do not deploy if audit fails. Full stop.
- Do not set env vars yourself. User does it in Dashboard / gcloud — they're sensitive.
- Do not commit. Do not run git commands. CLAUDE.md rule 5.
- Always smoke-test after deploy. Automatic pipelines do not replace live-eye verification.
- Never paste real secret values into chat. User runs
gcloud secrets create ... --data-file=-themselves.
What NOT to do
- Do not change vercel.json without user request.
- Do not wire external services (Cloudflare Workers, Netlify redirect, etc.) without discussion.
- Do not deploy to staging and prod simultaneously — verify staging first.
- Do not commit
sa-key.jsonor any.envfile — verify.gitignorecovers them.
Next
- Monitor first hours (analytics, Vercel error logs).
- Discuss: post-deploy monitoring?
- Plan next edits (edits → audit → deploy).
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.

