[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJTDFW0WCKBNSJN101B6DH":3,"skill-same:01M7BJTDFW0WCKBNSJN101B6DH":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M7BJTDFW0WCKBNSJN101B6DH","railway-deploy",null,"Deploy code to Railway using \"railway up\". Use when user wants to push code, says \"railway up\", \"deploy\", \"ship\", or \"push\". For initial setup or creating services, use railway-new skill. For Docker images, use railway-environment skill.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeploy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: railway-deploy\ndescription: Deploy code to Railway using \"railway up\". Use when user wants to push code, says \"railway up\", \"deploy\", \"ship\", or \"push\". For initial setup or creating services, use railway-new skill. For Docker images, use railway-environment skill.\nversion: 1.0.0\nauthor: Railway\nlicense: MIT\ntags: [Railway, Deploy, CI\u002FCD, Push, Ship, Infrastructure, Deployment]\ndependencies: [railway-cli]\nallowed-tools: Bash(railway:*)\n---\n\n# Railway Deploy\n\nDeploy code from the current directory to Railway using `railway up`.\n\n## When to Use\n\n- User asks to \"deploy\", \"ship\", \"push code\"\n- User says \"railway up\" or \"deploy to Railway\"\n- User wants to deploy local code changes\n- User says \"deploy and fix any issues\" (use --ci mode)\n\n## Modes\n\n### Detach Mode (default)\nStarts deploy and returns immediately. Use for most deploys.\n\n```bash\nrailway up --detach\n```\n\n### CI Mode\nStreams build logs until complete. Use when user wants to watch the build or needs to debug issues.\n\n```bash\nrailway up --ci\n```\n\n**When to use CI mode:**\n- User says \"deploy and watch\", \"deploy and fix issues\"\n- User is debugging build failures\n- User wants to see build output\n\n## Deploy Specific Service\n\nDefault is linked service. To deploy to a different service:\n\n```bash\nrailway up --detach --service backend\n```\n\n## Deploy to Unlinked Project\n\nDeploy to a project without linking first:\n\n```bash\nrailway up --project \u003Cproject-id> --environment production --detach\n```\n\nRequires both `--project` and `--environment` flags.\n\n## CLI Options\n\n| Flag | Description |\n|------|-------------|\n| `-d, --detach` | Don't attach to logs (default) |\n| `-c, --ci` | Stream build logs, exit when done |\n| `-s, --service \u003CNAME>` | Target service (defaults to linked) |\n| `-e, --environment \u003CNAME>` | Target environment (defaults to linked) |\n| `-p, --project \u003CID>` | Target project (requires --environment) |\n| `[PATH]` | Path to deploy (defaults to current directory) |\n\n## Directory Linking\n\nRailway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.\n\nFor subdirectory deployments, prefer setting `rootDirectory` via the railway-environment skill, then deploy normally with `railway up`.\n\n## After Deploy\n\n### Detach mode\n```\nDeploying to \u003Cservice>...\n```\nUse railway-deployment skill to check build status (with `--lines` flag).\n\n### CI mode\nBuild logs stream inline. If build fails, the error will be in the output.\n\n**Do NOT run `railway logs --build` after CI mode** - the logs already streamed. If you need\nmore context, use railway-deployment skill with `--lines` flag (never stream).\n\n## Composability\n\n- **Check status after deploy**: Use railway-service skill\n- **View logs**: Use railway-deployment skill\n- **Fix config issues**: Use railway-environment skill\n- **Redeploy after config fix**: Use railway-environment skill\n\n## Error Handling\n\n### No Project Linked\n```\nNo Railway project linked. Run `railway link` first.\n```\n\n### No Service Linked\n```\nNo service linked. Use --service flag or run `railway service` to select one.\n```\n\n### Build Failure (CI mode)\nThe build logs already streamed - analyze them directly from the `railway up --ci` output.\nDo NOT run `railway logs` after CI mode (it streams forever without `--lines`).\n\nCommon issues:\n- Missing dependencies → check package.json\u002Frequirements.txt\n- Build command wrong → use railway-environment skill to fix\n- Dockerfile issues → check dockerfile path\n","# Railway Deploy\n\nDeploy code from the current directory to Railway using `railway up`.\n\n## When to Use\n\n- User asks to \"deploy\", \"ship\", \"push code\"\n- User says \"railway up\" or \"deploy to Railway\"\n- User wants to deploy local code changes\n- User says \"deploy and fix any issues\" (use --ci mode)\n\n## Modes\n\n### Detach Mode (default)\nStarts deploy and returns immediately. Use for most deploys.\n\n```bash\nrailway up --detach\n```\n\n### CI Mode\nStreams build logs until complete. Use when user wants to watch the build or needs to debug issues.\n\n```bash\nrailway up --ci\n```\n\n**When to use CI mode:**\n- User says \"deploy and watch\", \"deploy and fix issues\"\n- User is debugging build failures\n- User wants to see build output\n\n## Deploy Specific Service\n\nDefault is linked service. To deploy to a different service:\n\n```bash\nrailway up --detach --service backend\n```\n\n## Deploy to Unlinked Project\n\nDeploy to a project without linking first:\n\n```bash\nrailway up --project \u003Cproject-id> --environment production --detach\n```\n\nRequires both `--project` and `--environment` flags.\n\n## CLI Options\n\n| Flag | Description |\n|------|-------------|\n| `-d, --detach` | Don't attach to logs (default) |\n| `-c, --ci` | Stream build logs, exit when done |\n| `-s, --service \u003CNAME>` | Target service (defaults to linked) |\n| `-e, --environment \u003CNAME>` | Target environment (defaults to linked) |\n| `-p, --project \u003CID>` | Target project (requires --environment) |\n| `[PATH]` | Path to deploy (defaults to current directory) |\n\n## Directory Linking\n\nRailway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.\n\nFor subdirectory deployments, prefer setting `rootDirectory` via the railway-environment skill, then deploy normally with `railway up`.\n\n## After Deploy\n\n### Detach mode\n```\nDeploying to \u003Cservice>...\n```\nUse railway-deployment skill to check build status (with `--lines` flag).\n\n### CI mode\nBuild logs stream inline. If build fails, the error will be in the output.\n\n**Do NOT run `railway logs --build` after CI mode** - the logs already streamed. If you need\nmore context, use railway-deployment skill with `--lines` flag (never stream).\n\n## Composability\n\n- **Check status after deploy**: Use railway-service skill\n- **View logs**: Use railway-deployment skill\n- **Fix config issues**: Use railway-environment skill\n- **Redeploy after config fix**: Use railway-environment skill\n\n## Error Handling\n\n### No Project Linked\n```\nNo Railway project linked. Run `railway link` first.\n```\n\n### No Service Linked\n```\nNo service linked. Use --service flag or run `railway service` to select one.\n```\n\n### Build Failure (CI mode)\nThe build logs already streamed - analyze them directly from the `railway up --ci` output.\nDo NOT run `railway logs` after CI mode (it streams forever without `--lines`).\n\nCommon issues:\n- Missing dependencies → check package.json\u002Frequirements.txt\n- Build command wrong → use railway-environment skill to fix\n- Dockerfile issues → check dockerfile path\n",{"name":5,"tags":24,"author":25,"license":15,"version":32,"description":7,"dependencies":33,"allowed-tools":35},[25,26,27,28,29,30,31],"Railway","Deploy","CI\u002FCD","Push","Ship","Infrastructure","Deployment","1.0.0",[34],"railway-cli","Bash(railway:*)","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeploy",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill railway-deploy",{"tool":51,"command":52},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill railway-deploy",{"tool":54,"command":55},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill railway-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeploy\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]