use-railway（使用铁路）

Use Railway

Use Railway CLI from evidence, not memory.

Trigger boundary

Use this skill when the task is about:

• exact railway commands, flags, aliases, arguments, or nested subcommands
• choosing between nearby Railway CLI commands for deploys, logs, environments, domains, scaling, SSH, functions, volumes, or database access
• reconciling the installed Railway CLI with newer first-party Railway docs or releases
• using first-party Railway runbooks as supporting context for a CLI-first answer

Do not use this skill when:

• the task is purely dashboard-only, GraphQL-only, or API-only Railway work
• the job is general cloud architecture or infrastructure planning with no Railway CLI decision to make
• a generic shell, Git, or deployment skill can answer the question without Railway-specific context

Non-negotiable rules

1. Treat the local extracted help snapshot as the source of truth for the installed binary.
2. Treat newer docs and releases as upstream context, not proof that a command exists locally.
3. Route to one workflow guide first, then pull exact flags from the command reference.
4. Explain close command splits when Railway has look-alike choices.
5. Stay read-safe by default; do not mutate Railway resources unless the user explicitly wants an operational action.
6. Never guess flags, aliases, or possible values from memory.

Recommended workflow

1. Establish version scope

Run railway --version when version drift could matter.

Read references/research/version-drift.md first if:

• the user says latest, current, today, or most recent
• the docs show a command the installed CLI does not
• the question mentions newer families such as skills, agent, bucket, or starship

2. Choose the smallest reference set

• Exact syntax, flags, aliases, nested subcommands, arguments, or possible values:

- references/cli/railway-cli-command-reference.md

• Raw help wording or formatting proof:

- references/cli/railway-cli-live-help-snapshot.md

• Top-level completeness audit:

- references/cli/command-family-coverage.md

• Workflow choice:

- one matching references/cli/*.md router - then references/cli/railway-cli-command-reference.md

• Upstream Railway guidance beyond the installed CLI:

- one matching file under references/upstream/ or references/database/ - plus references/research/version-drift.md when local and upstream may differ

3. Answer case by case

For each answer:

1. state whether the scope is local CLI, upstream Railway sources, or both
2. choose the best command or reference route
3. include exact flags, aliases, nested subcommands, or possible values when asked
4. explain the closest confusing alternative when needed
5. add a version-drift note only if it materially changes the answer

Common decision splits

Quick routing

• "What flags does railway X support?" -> references/cli/railway-cli-command-reference.md
• "Show the exact help text for railway X" -> references/cli/railway-cli-live-help-snapshot.md
• "Show me every local Railway command family this skill covers" -> references/cli/command-family-coverage.md
• "Which Railway command fits this task?" -> references/cli/common-workflows.md
• "I need to link, init, add, delete, or inspect project context" -> references/cli/context-projects-and-linking.md
• "I need to deploy, redeploy, restart, or roll back the latest deployment" -> references/cli/deployments-and-releases.md
• "I need run, shell, or dev" -> references/cli/local-development-and-shells.md
• "I need logs, status, connect, or ssh" -> references/cli/observability-and-access.md
• "I need env vars, config edits, domains, or scale" -> references/cli/configuration-networking-and-scaling.md
• "I need functions or volumes" -> references/cli/functions-and-volumes.md
• "The docs show a command I do not have" -> references/research/version-drift.md
• "I want Railway's own setup or deploy runbook, not just local CLI syntax" -> references/upstream/operations/setup.md or references/upstream/operations/deploy.md
• "I pasted a Railway dashboard URL and need a safe starting point" -> references/upstream/resource-model-and-preflight.md
• "I need first-party Railway database analysis guidance" -> references/database/analyze-db.md

Refresh the local snapshot

When the Railway CLI changes, refresh the generated references from this skill directory:

node scripts/extract-railway-cli-help.mjs
railway --version

Reference routing

Output contract

Return answers in this order unless the user wants a different format:

1. scope line: local installed CLI, upstream official sources, or both
2. best command or routed next step
3. important flags, aliases, subcommands, or possible values
4. near-neighbor distinction when confusion is likely
5. version-drift note only when it changes the answer

Guardrails

• Do not treat railway deploy and railway up as synonyms.
• Do not treat railway delete and railway unlink as synonyms.
• Do not treat railway redeploy and railway restart as synonyms.
• Do not present upstream-only commands as locally available without saying so explicitly.
• Do not default to dashboard instructions when the user asked about the CLI.
• Do not let the copied upstream runbooks override the local extracted CLI when the user is asking about the installed binary's exact command surface.
• Do not trust the linked directory over an explicit Railway dashboard URL or explicit project/environment/service identifiers.
• Do not mutate Railway resources unless the user explicitly asked for an operational action; this skill is reference-first.
• Do not use this skill for purely dashboard, GraphQL, or infrastructure-only Railway work unless the CLI question is central.