deploy
Skill49 starsChanged 25 days agoApache-2.0View on GitHub
Make a Rust off Rails app deployable and ship it (Docker, Fly.io, Kamal, Railway, Render), including production database setup and migrations on deploy. Use when the user asks to deploy, ship, host, or put an Off Rails app in production.
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-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 versions155 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 155
- 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
145 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, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 139 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Only for Rust off Rails apps (a .offrails/ directory exists).
- Very specific: line 13
Read .offrails/guides/deployment.md, .offrails/guides/config.md and .offrails/cli.md#migrations-on-deploy.
- Very specific: line 14
If the target changed, update DEPLOY_TARGET in AGENTS.md and log it in docs/decisions.md.
- Very specific: line 16
Verify locally: /offrails:check is green and docker build .
- Very specific: line 18
After deploying, curl https://<host>/up, check the deploy logs for db migrate, and report the URL.
“Common” is measured: kept by at least 6 in 10 of the 139 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
/offrails:deploy
Only for Rust off Rails apps (a .offrails/ directory exists).
Target: $ARGUMENTS (otherwise DEPLOY_TARGET from the app's AGENTS.md, otherwise ask Round 2 Q3 of .offrails/interview.md).
- Read
.offrails/guides/deployment.md,.offrails/guides/config.mdand.offrails/cli.md#migrations-on-deploy. - If the target changed, update
DEPLOY_TARGETinAGENTS.mdand log it indocs/decisions.md. - Generate or update the
Dockerfile,bin/docker-entrypointand the target's config file only, per the guide. EveryConfigenv var must appear in the deploy config, with secrets referenced rather than inlined. - Verify locally:
/offrails:checkis green anddocker build .succeeds (if Docker is available). Run the image against SQLite andcurl /up. - Stop and confirm before anything outward-facing. List the exact commands (creating the app or database, setting secrets, deploying), what each one costs or changes, and the secrets the human must supply. Never invent or echo secret values. Run them only after an explicit yes.
- After deploying,
curl https://<host>/up, check the deploy logs fordb migrate, and report the URL.
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.

