deploy
Skill2 starsChanged 3 months agoMITView on GitHub
Put the app on the internet, or ship a new version of one already there. Use when someone wants their app live, wants to share a link, or wants their latest changes on the live site.
- Reads credentials
155 other projects use a version of this.
Adopted by
Most recently taken up by
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- KingKongRobotics/jumpertheir own version, first seen Nov 8, 2026
- stakeme-team/arc-agent-kittheir own version, first seen Nov 8, 2026
- dockhold/mcptheir own version, first seen Nov 8, 2026
- KhaiTrang1995/nexus-kbtheir own version, first seen Nov 8, 2026
- ribato22/vibechecktheir own version, first seen Nov 8, 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-aiSkill
qa-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 versions155 projects use a version of this.
Word for word · 1
- daveebbelaar/project-template★ 4100% same
Edited · 0
None found.
Wrote their own version · 154
- 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.1ksame name
- jazzyalex/agent-sessions★ 941same name
- awslabs/agent-plugins★ 918same name
- patrickjaja/claude-desktop-extra★ 734same name
144 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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 138 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read the level in .stack-level.
- Very specific: line 33
Every name in .env.example needs a value in the hosting provider.
- Distinctive: line 43
Run the deploy command from the matching page.
- Very specific: line 65
Put the live address and today's date in project/BRIEF.md under "Live at".
- Distinctive: line 73
Never let a failing check through on the grounds that it worked last time.
“Common” is measured: kept by at least 6 in 10 of the 138 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
Get it live: reachable on the internet, by someone who is not them, on a machine that is not theirs.
That is a binary. Running on their laptop is not live.
1. Clear the checks
Work PREFLIGHT.md before running a single deploy command.
A finding gets fixed and the whole list runs again from the top. A check that reports a leak is reporting something true, so the fix is the app.
Done when: ./scripts/preflight.sh exits clean, on a run where nothing was skipped.
2. Pick where it goes
Read the level in .stack-level.
- Levels 1 and 2: the whole app goes to Vercel.
docs/deploy/vercel.md. - Level 3: the backend goes to Railway first, then the website to Vercel with the backend's address, then back to Railway to point it at the website.
docs/deploy/railway-fastapi.md, thendocs/deploy/vercel.md.
Level 3 takes two passes because each piece needs the other's address. Say that up front so it does not look like something went wrong.
Done when: the level is stated and the matching deploy page has been read.
3. Set the settings before the first build
Every name in .env.example needs a value in the hosting provider. A setting added after a build is not in that build.
Type the values in. On Vercel, skip the Supabase marketplace integration: it adds a dozen settings nobody asked for, including a key that ignores row security, and the safety checks read your files rather than Vercel's dashboard.
Then read the list back and count it. Level 1 has exactly four names. Level 2 has exactly two.
Done when: the provider's list of settings matches .env.example exactly, name for name.
4. Ship it
Run the deploy command from the matching page.
Done when: the build log ends green and the live address loads the app's first screen.
5. Do the job on the internet
Have them do the app's main job once, at the live address, in their own browser. Then check the record landed in the Supabase table editor.
This catches settings that are right locally and wrong in production, which a successful build does not.
Done when: they confirm they completed the job at the live address, and the record is visible in Supabase.
6. Look at the advisor
Supabase dashboard, then Advisors, then Security Advisor. Confirm no errors.
It runs Supabase's own review and catches a few things the scripts do not.
Done when: the advisor shows no errors, or each one has been fixed with a migration.
7. Write it down
Put the live address and today's date in project/BRIEF.md under "Live at". Mark the deployed slices as live in project/SLICES.md. Append the hosting choices to project/DECISIONS.md.
Then tell them the one thing they need to know: what it costs per month, and what happens when they stop paying. docs/deploy/costs.md has the numbers.
Shipping an update
Steps 1, 4, and 5. The settings are already there.
Never let a failing check through on the grounds that it worked last time. The check runs against what is about to ship.
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.