railway-tools
Use when deploying to Railway, editing railway.toml, railway.json, Procfile, configuring Railway services, databases, workers, environment variables, or troubleshooting Railway deployments.
Best use case
railway-tools is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when deploying to Railway, editing railway.toml, railway.json, Procfile, configuring Railway services, databases, workers, environment variables, or troubleshooting Railway deployments.
Teams using railway-tools should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/railway-tools/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How railway-tools Compares
| Feature / Agent | railway-tools | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when deploying to Railway, editing railway.toml, railway.json, Procfile, configuring Railway services, databases, workers, environment variables, or troubleshooting Railway deployments.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Railway Deployment (Flow Tools)
<workflow>
## 🚀 Official Railway Skills (Highly Recommended)
For full project management, deployment automation, and service orchestration, we highly recommend installing the official Railway agent skills:
- **use-railway**: Master skill for setting up projects, services, and handling deployments.
**Installation:**
```bash
npx skills add railwayapp/railway-skills
```
## Supplemental Patterns
The patterns below provide additional context for Flow-specific multi-service architectures and serverless constraints.
### Serverless / App Sleeping
Railway's serverless feature puts services to sleep after 10 minutes of no **outbound** traffic.
**When to disable serverless (`sleepApplication: false`):**
- Background workers (Celery, SAQ, RQ, Sidekiq)
- Queue processors
- Cron services
- Any service without an HTTP endpoint
### Multi-Service Architecture (Web + Worker)
For applications with background task processing, use distinct configuration files (e.g., `railway.app.json` and `railway.worker.json`) to manage different runtime requirements.
</workflow>
<guardrails>
## Guardrails
- **Disable Serverless for Workers:** Always set `sleepApplication: false` for background worker services.
- **Use Variable References:** Prefer `${{Service.VARIABLE}}` syntax (e.g., `${{Postgres.DATABASE_URL}}`) instead of hardcoding values.
- **Dynamic Port Binding:** Never hardcode the port. Always reference `${{PORT}}` for application port injection.
</guardrails>
<validation>
## Validation
- **Verify `sleepApplication: false` for Workers:** Ensure any background worker has `sleepApplication` explicitly set to `false`.
- **Check PORT Dynamic Reference:** Confirm that start commands and environment variables reference `${{PORT}}`.
</validation>
<example>
## Multi-Service Worker Example
**Configuration (`railway.worker.json`):**
```json
{
"service": {
"name": "worker",
"sleepApplication": false
},
"deploy": {
"startCommand": "python -m saq my_app.tasks.worker --workers 4"
}
}
```
</example>Related Skills
shadcn-tools
Use when editing shadcn/ui code, components.json, cn() utility, Radix primitives, shadcn add workflows, dialogs, forms, data tables, command palettes, or Tailwind component composition.
mojo-tools
Use when editing Mojo code, .mojo files, fire emoji files, SIMD kernels, Python-Mojo interop, GIL-free parallelism, C FFI, hatch-mojo build hooks, or packaging Mojo extensions.
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.
tanstack
Use when editing TanStack code, @tanstack imports, useQuery, createRouter, React Query, TanStack Router, Table, Form, Store, file-based routing, data fetching, or SPA state management.
tailwind
Use when styling with Tailwind CSS, editing tailwind.config.ts, tailwind.config.js, @tailwind directives, utility classes, responsive layouts, @apply, cn(), @theme config, dark mode, or forms.
svelte
Use when editing Svelte components, .svelte files, svelte.config.js, Svelte 5 runes, $state, $derived, SvelteKit, component state, or migrating away from Svelte 4 patterns.