[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7387ESFDCW31DB3SSK54VD8":3,"skill-same:01M7387ESFDCW31DB3SSK54VD8":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7387ESFDCW31DB3SSK54VD8","deploy-to-vercel",null,"Deploy a Next.js application to Vercel. Covers project linking, environment variables, preview deployments, custom domains, and production deployment configuration. Use when deploying a Next.js app for the first time, setting up preview deployments for pull requests, configuring custom domains, or managing environment variables in a production Vercel deployment.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeploy-to-vercel\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: deploy-to-vercel\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-23\"\ndescription: >\n  Deploy a Next.js application to Vercel. Covers project linking,\n  environment variables, preview deployments, custom domains,\n  and production deployment configuration. Use when deploying a Next.js\n  app for the first time, setting up preview deployments for pull requests,\n  configuring custom domains, or managing environment variables in\n  a production Vercel deployment.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: web-dev\n  complexity: basic\n  language: TypeScript\n  tags: vercel, deployment, nextjs, hosting, ci-cd\n---\n\n# Deploy to Vercel\n\nDeploy a Next.js application to Vercel with production configuration.\n\n## When to Use\n\n- Deploying a Next.js app for the first time\n- Setting up preview deployments for pull requests\n- Configuring custom domains\n- Managing environment variables in production\n\n## Inputs\n\n- **Required**: Next.js application that builds successfully locally\n- **Required**: GitHub repository (recommended) or local project\n- **Optional**: Custom domain\n- **Optional**: Environment variables for production\n\n## Procedure\n\n### Step 1: Verify Local Build\n\n```bash\nnpm run build\n```\n\n**Got:** Build succeeds with no errors.\n\n**If fail:** Fix build errors before deploying. Common: TypeScript errors, missing dependencies, invalid imports.\n\n### Step 2: Install Vercel CLI\n\n```bash\nnpm install -g vercel\n```\n\n**Got:** The `vercel` command is available globally and `vercel --version` prints the installed version.\n\n**If fail:** If permission errors occur, use `sudo npm install -g vercel` or configure npm to use a user-local prefix. Verify Node.js is installed with `node --version`.\n\n### Step 3: Link and Deploy\n\n```bash\n# Login to Vercel\nvercel login\n\n# Deploy (first time: creates project)\nvercel\n\n# Follow prompts:\n# - Set up and deploy? Y\n# - Which scope? (select your account)\n# - Link to existing project? N (for new projects)\n# - Project name: my-app\n# - Directory: .\u002F\n# - Override settings? N\n```\n\n**Got:** Preview URL provided (e.g., `https:\u002F\u002Fmy-app-xxx.vercel.app`).\n\n**If fail:** If `vercel login` fails, check internet connectivity and try browser-based authentication. If the deploy fails, review the build output for errors -- Vercel uses a clean environment, so all dependencies must be in `package.json`.\n\n### Step 4: Configure Environment Variables\n\n```bash\n# Add environment variables\nvercel env add DATABASE_URL production\nvercel env add API_KEY production preview\n\n# List environment variables\nvercel env ls\n```\n\nOr configure through the Vercel dashboard: Project Settings > Environment Variables.\n\n**Got:** `vercel env ls` shows all required environment variables configured for the correct environments (production, preview, development).\n\n**If fail:** If variables are not appearing at runtime, verify the target environment matches (production vs preview). Redeploy after adding variables -- existing deployments do not pick up new variables automatically.\n\n### Step 5: Deploy to Production\n\n```bash\nvercel --prod\n```\n\n**Got:** Production URL available (e.g., `https:\u002F\u002Fmy-app.vercel.app`).\n\n**If fail:** Check deployment logs with `vercel logs` or in the Vercel dashboard. Common issues include missing environment variables in the production environment and build commands differing from local setup.\n\n### Step 6: Connect GitHub for Auto-Deploy (Recommended)\n\n1. Go to https:\u002F\u002Fvercel.com\u002Fnew\n2. Import your GitHub repository\n3. Vercel automatically deploys on:\n   - Push to main -> Production deployment\n   - Pull request -> Preview deployment\n\n**Got:** The Vercel dashboard shows the GitHub repository connected, and subsequent pushes to main trigger production deployments automatically.\n\n**If fail:** If the repository does not appear in the import list, check that the Vercel GitHub app has access to the repository. Go to GitHub Settings > Applications > Vercel and grant access.\n\n### Step 7: Configure Custom Domain\n\n```bash\nvercel domains add my-domain.com\n```\n\nOr through dashboard: Project Settings > Domains.\n\nUpdate DNS records as instructed by Vercel (typically CNAME or A record).\n\n**Got:** `vercel domains ls` shows the custom domain as configured, and after DNS propagation (up to 48 hours), the domain resolves to the Vercel deployment.\n\n**If fail:** If the domain shows \"Invalid Configuration,\" verify DNS records match Vercel's instructions exactly. Use `dig my-domain.com` or an online DNS checker to confirm propagation.\n\n### Step 8: Optimize Configuration\n\nCreate `vercel.json` for advanced settings:\n\n```json\n{\n  \"framework\": \"nextjs\",\n  \"regions\": [\"iad1\"],\n  \"headers\": [\n    {\n      \"source\": \"\u002Fapi\u002F(.*)\",\n      \"headers\": [\n        { \"key\": \"Cache-Control\", \"value\": \"no-store\" }\n      ]\n    }\n  ]\n}\n```\n\n**Got:** `vercel.json` is saved in the project root and the next deployment picks up the configuration (visible in the Vercel dashboard build logs).\n\n**If fail:** If the configuration is ignored, verify `vercel.json` is valid JSON with `jq . vercel.json`. Check the Vercel docs for your framework version, as some settings may have moved to `next.config.ts`.\n\n## Validation\n\n- [ ] `npm run build` succeeds locally\n- [ ] Preview deployment works and is accessible\n- [ ] Production deployment serves the application correctly\n- [ ] Environment variables are available in production\n- [ ] Custom domain resolves (if configured)\n- [ ] GitHub integration triggers deployments on push\n\n## Pitfalls\n\n- **Build failing on Vercel but not locally**: Vercel uses a clean environment. Ensure all dependencies are in `package.json`, not installed globally.\n- **Environment variables missing**: Variables must be added to Vercel, not `.env.local`. Different environments (production, preview, development) have separate variable sets.\n- **Node.js version mismatch**: Set the Node.js version in Project Settings or `package.json` engines field.\n- **Large deployments**: Vercel has size limits. Use `.vercelignore` to exclude unnecessary files.\n- **API route timeouts**: Vercel serverless functions have a 10s timeout on the Hobby plan. Optimize or upgrade.\n\n## Related Skills\n\n- `scaffold-nextjs-app` - create the app to deploy\n- `setup-tailwind-typescript` - configure styling before deployment\n- `configure-git-repository` - Git setup for auto-deploy integration\n","# Deploy to Vercel\n\nDeploy a Next.js application to Vercel with production configuration.\n\n## When to Use\n\n- Deploying a Next.js app for the first time\n- Setting up preview deployments for pull requests\n- Configuring custom domains\n- Managing environment variables in production\n\n## Inputs\n\n- **Required**: Next.js application that builds successfully locally\n- **Required**: GitHub repository (recommended) or local project\n- **Optional**: Custom domain\n- **Optional**: Environment variables for production\n\n## Procedure\n\n### Step 1: Verify Local Build\n\n```bash\nnpm run build\n```\n\n**Got:** Build succeeds with no errors.\n\n**If fail:** Fix build errors before deploying. Common: TypeScript errors, missing dependencies, invalid imports.\n\n### Step 2: Install Vercel CLI\n\n```bash\nnpm install -g vercel\n```\n\n**Got:** The `vercel` command is available globally and `vercel --version` prints the installed version.\n\n**If fail:** If permission errors occur, use `sudo npm install -g vercel` or configure npm to use a user-local prefix. Verify Node.js is installed with `node --version`.\n\n### Step 3: Link and Deploy\n\n```bash\n# Login to Vercel\nvercel login\n\n# Deploy (first time: creates project)\nvercel\n\n# Follow prompts:\n# - Set up and deploy? Y\n# - Which scope? (select your account)\n# - Link to existing project? N (for new projects)\n# - Project name: my-app\n# - Directory: .\u002F\n# - Override settings? N\n```\n\n**Got:** Preview URL provided (e.g., `https:\u002F\u002Fmy-app-xxx.vercel.app`).\n\n**If fail:** If `vercel login` fails, check internet connectivity and try browser-based authentication. If the deploy fails, review the build output for errors -- Vercel uses a clean environment, so all dependencies must be in `package.json`.\n\n### Step 4: Configure Environment Variables\n\n```bash\n# Add environment variables\nvercel env add DATABASE_URL production\nvercel env add API_KEY production preview\n\n# List environment variables\nvercel env ls\n```\n\nOr configure through the Vercel dashboard: Project Settings > Environment Variables.\n\n**Got:** `vercel env ls` shows all required environment variables configured for the correct environments (production, preview, development).\n\n**If fail:** If variables are not appearing at runtime, verify the target environment matches (production vs preview). Redeploy after adding variables -- existing deployments do not pick up new variables automatically.\n\n### Step 5: Deploy to Production\n\n```bash\nvercel --prod\n```\n\n**Got:** Production URL available (e.g., `https:\u002F\u002Fmy-app.vercel.app`).\n\n**If fail:** Check deployment logs with `vercel logs` or in the Vercel dashboard. Common issues include missing environment variables in the production environment and build commands differing from local setup.\n\n### Step 6: Connect GitHub for Auto-Deploy (Recommended)\n\n1. Go to https:\u002F\u002Fvercel.com\u002Fnew\n2. Import your GitHub repository\n3. Vercel automatically deploys on:\n   - Push to main -> Production deployment\n   - Pull request -> Preview deployment\n\n**Got:** The Vercel dashboard shows the GitHub repository connected, and subsequent pushes to main trigger production deployments automatically.\n\n**If fail:** If the repository does not appear in the import list, check that the Vercel GitHub app has access to the repository. Go to GitHub Settings > Applications > Vercel and grant access.\n\n### Step 7: Configure Custom Domain\n\n```bash\nvercel domains add my-domain.com\n```\n\nOr through dashboard: Project Settings > Domains.\n\nUpdate DNS records as instructed by Vercel (typically CNAME or A record).\n\n**Got:** `vercel domains ls` shows the custom domain as configured, and after DNS propagation (up to 48 hours), the domain resolves to the Vercel deployment.\n\n**If fail:** If the domain shows \"Invalid Configuration,\" verify DNS records match Vercel's instructions exactly. Use `dig my-domain.com` or an online DNS checker to confirm propagation.\n\n### Step 8: Optimize Configuration\n\nCreate `vercel.json` for advanced settings:\n\n```json\n{\n  \"framework\": \"nextjs\",\n  \"regions\": [\"iad1\"],\n  \"headers\": [\n    {\n      \"source\": \"\u002Fapi\u002F(.*)\",\n      \"headers\": [\n        { \"key\": \"Cache-Control\", \"value\": \"no-store\" }\n      ]\n    }\n  ]\n}\n```\n\n**Got:** `vercel.json` is saved in the project root and the next deployment picks up the configuration (visible in the Vercel dashboard build logs).\n\n**If fail:** If the configuration is ignored, verify `vercel.json` is valid JSON with `jq . vercel.json`. Check the Vercel docs for your framework version, as some settings may have moved to `next.config.ts`.\n\n## Validation\n\n- [ ] `npm run build` succeeds locally\n- [ ] Preview deployment works and is accessible\n- [ ] Production deployment serves the application correctly\n- [ ] Environment variables are available in production\n- [ ] Custom domain resolves (if configured)\n- [ ] GitHub integration triggers deployments on push\n\n## Pitfalls\n\n- **Build failing on Vercel but not locally**: Vercel uses a clean environment. Ensure all dependencies are in `package.json`, not installed globally.\n- **Environment variables missing**: Variables must be added to Vercel, not `.env.local`. Different environments (production, preview, development) have separate variable sets.\n- **Node.js version mismatch**: Set the Node.js version in Project Settings or `package.json` engines field.\n- **Large deployments**: Vercel has size limits. Use `.vercelignore` to exclude unnecessary files.\n- **API route timeouts**: Vercel serverless functions have a 10s timeout on the Hobby plan. Optimize or upgrade.\n\n## Related Skills\n\n- `scaffold-nextjs-app` - create the app to deploy\n- `setup-tailwind-typescript` - configure styling before deployment\n- `configure-git-repository` - Git setup for auto-deploy integration\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"vercel, deployment, nextjs, hosting, ci-cd","Philipp Thoss","web-dev","1.0","TypeScript","basic","Julius Brussee homage — caveman","Deploy a Next.js application to Vercel. Covers project linking, environment variables, preview deployments, custom domains, and production deployment configuration. Use when deploying a Next.js app for the first time, setting up preview deployments for pull requests, configuring custom domains, or managing environment variables in a production Vercel deployment.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-04-23","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fdeploy-to-vercel",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill deploy-to-vercel",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill deploy-to-vercel",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill deploy-to-vercel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdeploy-to-vercel\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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]