菜单
Use when user mentions Railway deployment, production environment issues, environment variables, database migrations, deployment failures, or Railway CLI commands - provides Railway.com platform integration for Next.js with PostgreSQL operations, monitoring, and troubleshooting
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pragmatic patterns for building multiplayer games: matchmaking, tick loops, realtime state, interest management, and validation.
Guide for advanced Next.js App Router patterns including Route Handlers, Parallel Routes, Intercepting Routes, Server Actions, error boundaries, draft mode, and streaming with Suspense. CRITICAL for server actions (action.ts, actions.ts files, 'use server' directive), setting cookies from client components, and form handling. Use when requirements involve server actions, form submissions, cookies, mutations, API routes, `route.ts`, parallel routes, intercepting routes, or streaming. Essential for separating server actions from client components.
Identify and fix common Next.js App Router anti-patterns and mistakes. Use when reviewing code for Next.js best practices, debugging performance issues, migrating from Pages Router patterns, or preventing common pitfalls. Activates for code review, performance optimization, or detecting inappropriate useEffect/useState usage. CRITICAL: For browser detection, keep the logic in the user-facing component (or a composed helper that it renders) rather than isolating it in unused files.
Guide for working with Next.js App Router (Next.js 13+). Use when migrating from Pages Router to App Router, creating layouts, implementing routing, handling metadata, or building Next.js 13+ applications. Activates for App Router migration, layout creation, routing patterns, or Next.js 13+ development tasks.
Pattern for client components calling server actions to set cookies in Next.js. Covers the two-file pattern of a client component with user interaction (onClick, form submission) that calls a server action to modify cookies. Use when building features like authentication, preferences, or session management where client-side triggers need to set/modify server-side cookies.
Guide for Next.js App Router dynamic routes and pathname parameters. Use when building pages that depend on URL segments (IDs, slugs, nested paths), accessing the `params` prop, or fetching resources by identifier. Helps avoid over-nesting by defaulting to the simplest route structure (e.g., `app/[id]` instead of `app/products/[id]` unless the URL calls for it).
| name | railway |
| description | Use when user mentions Railway deployment, production environment issues, environment variables, database migrations, deployment failures, or Railway CLI commands - provides Railway.com platform integration for Next.js with PostgreSQL operations, monitoring, and troubleshooting |
BEFORE using this skill, verify the project uses Railway:
railway.json or railway.toml file exists.railway directory existsDO NOT use this skill for:
Railway.com platform skill for deploying and managing Next.js applications with PostgreSQL. Provides CLI workflows for deployment, environment management, database operations, and troubleshooting.
Core principle: Use Railway CLI for deployments, database access, and environment management. Use internal DATABASE_URL (not PUBLIC) to avoid egress fees.
ONLY after verifying this is a Railway project, use this skill when you see:
NEVER use this skill for:
railway run)If uncertain, verify first:
# Check for Railway configuration
ls -la railway.json railway.toml .railway/
# If files don't exist → NOT a Railway project → DON'T use this skill
| Task | Command |
|---|---|
| Deploy | railway up |
| Check status | railway status |
| View logs | railway logs |
| Build logs | railway logs --build |
| Set variable | railway variables --set "KEY=VALUE" |
| List variables | railway variables --kv |
| Connect to DB | railway connect postgres |
| Run migrations | railway run node scripts/migrate.js |
| Open dashboard | railway open |
| Redeploy | railway redeploy --yes |
| Switch env | railway environment [ENV] |
Before running ANY Railway commands, verify project uses Railway:
# Method 1: Check for Railway config files
ls railway.json railway.toml .railway/
# Method 2: Check if linked to Railway
railway status
# Method 3: Ask user
# "Is this project deployed to Railway, or using another platform?"
If no Railway artifacts found → ASK USER before proceeding.
Deploy Workflow:
railway status && railway up && railway logs
Debug Failed Deployment:
railway logs --build # Check build errors
railway variables # Verify env vars
railway run npm run build # Test locally
Database Migration (ALWAYS backup first):
railway run pg_dump -Fc > backup.dump # 1. BACKUP FIRST (mandatory)
railway connect postgres -c "\dt" # 2. Check current state
railway run node scripts/migrate.js # 3. Run migration
railway connect postgres -c "\dt" # 4. Verify changes
1. Using PUBLIC_URL instead of internal DATABASE_URL - causes egress charges
2. Forgetting to redeploy after setting variables - use railway redeploy --yes
3. Not testing locally - always railway run npm run build first
4. Hardcoded PORT - use process.env.PORT || 3000 (Railway assigns PORT)
5. Next.js env vars at build-time - vars must exist during build, not just runtime; use lazy initialization for module-level code
6. Running migrations without backup - ALWAYS backup first: railway run pg_dump -Fc > backup.dump
7. Re-running failed migrations - diagnose state first, don't re-run blindly
Detailed documentation in supporting files:
Official Railway resources:
railway logs --build when debuggingrailway run npm run build before deployingrailway run pg_dump -Fc > backup.dumprailway logs | grep -i errorCRITICAL: Diagnose before acting. Never guess under pressure.
railway logs --build - check build errors FIRSTrailway variables - verify env vars existrailway run npm run build - test locally with Railway envFor database issues: backup → diagnose → fix → verify