[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74BK2CWTQP0C015TFJS930C":3,"skill-same:01M74BK2CWTQP0C015TFJS930C":46},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M74BK2CWTQP0C015TFJS930C","vercel-cli-with-tokens",null,"Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".","aicreator350\u002FaurionOFFICIELLE","aicreator350","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F217751428?v=4","01M731QVHB22WCM6PDX5VFN1RV","01M731QVJ0TAD058M1SW9MY548",0,"MIT","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.goose\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: vercel-cli-with-tokens\ndescription: Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".\nmetadata:\n  author: vercel\n  version: \"1.0.0\"\n---\n\n# Vercel CLI with Tokens\n\nDeploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`.\n\n## Step 1: Locate the Vercel Token\n\nBefore running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:\n\n### A) `VERCEL_TOKEN` is already set in the environment\n\n```bash\nprintenv VERCEL_TOKEN\n```\n\nIf this returns a value, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull\n```\n\nIf found, export it:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)\n```\n\n### C) Token is in a `.env` file under a different name\n\nLook for any variable that looks like a Vercel token (Vercel tokens typically start with `vca_`):\n\n```bash\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\nInspect the output to identify which variable holds the token, then export it as `VERCEL_TOKEN`:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^\u003CVARIABLE_NAME>=' .env | cut -d= -f2-)\n```\n\n### D) No token found — ask the user\n\nIf none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com\u002Faccount\u002Ftokens.\n\n---\n\n**Important:** Once `VERCEL_TOKEN` is exported as an environment variable, the Vercel CLI reads it natively — **do not pass it as a `--token` flag**. Putting secrets in command-line arguments exposes them in shell history and process listings.\n\n```bash\n# Bad — token visible in shell history and process listings\nvercel deploy --token \"vca_abc123\"\n\n# Good — CLI reads VERCEL_TOKEN from the environment\nexport VERCEL_TOKEN=\"vca_abc123\"\nvercel deploy\n```\n\n## Step 2: Locate the Project and Team\n\nSimilarly, check for the project ID and team scope. These let the CLI target the right project without needing `vercel link`.\n\n```bash\n# Check environment\nprintenv VERCEL_PROJECT_ID\nprintenv VERCEL_ORG_ID\n\n# Or check .env\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\n**If you have a project URL** (e.g. `https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project`), extract the team slug:\n\n```bash\n# e.g. \"my-team\" from \"https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project\"\necho \"$PROJECT_URL\" | sed 's|https:\u002F\u002Fvercel.com\u002F||' | cut -d\u002F -f1\n```\n\n**If you have both `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` in your environment**, export them — the CLI will use these automatically and skip any `.vercel\u002F` directory:\n\n```bash\nexport VERCEL_ORG_ID=\"\u003Corg-id>\"\nexport VERCEL_PROJECT_ID=\"\u003Cproject-id>\"\n```\n\nNote: `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` must be set together — setting only one causes an error.\n\n## CLI Setup\n\nEnsure the Vercel CLI is installed:\n\n```bash\nnpm install -g vercel\nvercel --version\n```\n\n## Deploying a Project\n\nAlways deploy as **preview** unless the user explicitly requests production. Choose a method based on what you have available.\n\n### Quick Deploy (have project ID — no linking needed)\n\nWhen `VERCEL_TOKEN` and `VERCEL_PROJECT_ID` are set in the environment, deploy directly:\n\n```bash\nvercel deploy -y --no-wait\n```\n\nWith a team scope (either via `VERCEL_ORG_ID` or `--scope`):\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nProduction (only when explicitly requested):\n\n```bash\nvercel deploy --prod --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Full Deploy Flow (no project ID — need to link)\n\nUse this when you have a token and team but no pre-existing project ID.\n\n#### Check project state first\n\n```bash\n# Does the project have a git remote?\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# Is it already linked to a Vercel project?\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n```\n\n#### Link the project\n\n**With git remote (preferred):**\n\n```bash\nvercel link --repo --scope \u003Cteam-slug> -y\n```\n\nReads the git remote and connects to the matching Vercel project. Creates `.vercel\u002Frepo.json`. More reliable than plain `vercel link`, which matches by directory name.\n\n**Without git remote:**\n\n```bash\nvercel link --scope \u003Cteam-slug> -y\n```\n\nCreates `.vercel\u002Fproject.json`.\n\n**Link to a specific project by name:**\n\n```bash\nvercel link --project \u003Cproject-name> --scope \u003Cteam-slug> -y\n```\n\nIf the project is already linked, check `orgId` in `.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` to verify it matches the intended team.\n\n#### Deploy after linking\n\n**A) Git Push Deploy — has git remote (preferred)**\n\nGit pushes trigger automatic Vercel deployments.\n\n1. **Ask the user before pushing.** Never push without explicit approval.\n2. Commit and push:\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n3. Vercel builds automatically. Non-production branches get preview deployments.\n4. Retrieve the deployment URL:\n   ```bash\n   sleep 5\n   vercel ls --format json --scope \u003Cteam-slug>\n   ```\n   Find the latest entry in the `deployments` array.\n\n**B) CLI Deploy — no git remote**\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Deploying from a Remote Repository (code not cloned locally)\n\n1. Clone the repository:\n   ```bash\n   git clone \u003Crepo-url>\n   cd \u003Crepo-name>\n   ```\n2. Link to Vercel:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug> -y\n   ```\n3. Deploy via git push (if you have push access) or CLI deploy.\n\n### About `.vercel\u002F` Directory\n\nA linked project has either:\n- `.vercel\u002Fproject.json` — from `vercel link`. Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — from `vercel link --repo`. Contains `orgId`, `remoteName`, and a `projects` map.\n\nNot needed when `VERCEL_ORG_ID` + `VERCEL_PROJECT_ID` are both set in the environment.\n\n**Do NOT** run `vercel ls`, `vercel project inspect`, or `vercel link` in an unlinked directory to detect state — they will interactively prompt or silently link as a side-effect. Only `vercel whoami` is safe to run anywhere.\n\n## Managing Environment Variables\n\n```bash\n# Set for all environments\necho \"value\" | vercel env add VAR_NAME --scope \u003Cteam-slug>\n\n# Set for a specific environment (production, preview, development)\necho \"value\" | vercel env add VAR_NAME production --scope \u003Cteam-slug>\n\n# List environment variables\nvercel env ls --scope \u003Cteam-slug>\n\n# Pull env vars to local .env file\nvercel env pull --scope \u003Cteam-slug>\n\n# Remove a variable\nvercel env rm VAR_NAME --scope \u003Cteam-slug> -y\n```\n\n## Inspecting Deployments\n\n```bash\n# List recent deployments\nvercel ls --format json --scope \u003Cteam-slug>\n\n# Inspect a specific deployment\nvercel inspect \u003Cdeployment-url>\n\n# View build logs\nvercel logs \u003Cdeployment-url>\n```\n\n## Managing Domains\n\n```bash\n# List domains\nvercel domains ls --scope \u003Cteam-slug>\n\n# Add a domain to the project\nvercel domains add \u003Cdomain> --scope \u003Cteam-slug>\n```\n\n## Working Agreement\n\n- **Never pass `VERCEL_TOKEN` as a `--token` flag.** Export it as an environment variable and let the CLI read it natively.\n- **Check the environment for tokens before asking the user.** Look in the current env and `.env` files first.\n- **Default to preview deployments.** Only deploy to production when explicitly asked.\n- **Ask before pushing to git.** Never push commits without the user's approval.\n- **Do not read or modify `.vercel\u002F` files directly.** The CLI manages this directory.\n- **Do not curl\u002Ffetch deployed URLs to verify.** Just return the link to the user.\n- **Use `--format json`** when structured output will help with follow-up steps.\n- **Use `-y`** on commands that prompt for confirmation to avoid interactive blocking.\n\n## Troubleshooting\n\n### Token not found\n\nCheck the environment and any `.env` files present:\n\n```bash\nprintenv | grep -i vercel\ngrep -i vercel .env 2>\u002Fdev\u002Fnull\n```\n\n### Authentication error\n\nIf the CLI fails with `Authentication required`:\n- The token may be expired or invalid.\n- Verify: `vercel whoami` (uses `VERCEL_TOKEN` from environment).\n- Ask the user for a fresh token.\n\n### Wrong team\n\nVerify the scope is correct:\n\n```bash\nvercel whoami --scope \u003Cteam-slug>\n```\n\n### Build failure\n\nCheck the build logs:\n\n```bash\nvercel logs \u003Cdeployment-url>\n```\n\nCommon causes:\n- Missing dependencies — ensure `package.json` is complete and committed.\n- Missing environment variables — add with `vercel env add`.\n- Framework misconfiguration — check `vercel.json`. Vercel auto-detects frameworks (Next.js, Remix, Vite, etc.) from `package.json`; override with `vercel.json` if detection is wrong.\n\n### CLI not installed\n\n```bash\nnpm install -g vercel\n```\n","# Vercel CLI with Tokens\n\nDeploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`.\n\n## Step 1: Locate the Vercel Token\n\nBefore running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:\n\n### A) `VERCEL_TOKEN` is already set in the environment\n\n```bash\nprintenv VERCEL_TOKEN\n```\n\nIf this returns a value, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull\n```\n\nIf found, export it:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)\n```\n\n### C) Token is in a `.env` file under a different name\n\nLook for any variable that looks like a Vercel token (Vercel tokens typically start with `vca_`):\n\n```bash\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\nInspect the output to identify which variable holds the token, then export it as `VERCEL_TOKEN`:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^\u003CVARIABLE_NAME>=' .env | cut -d= -f2-)\n```\n\n### D) No token found — ask the user\n\nIf none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com\u002Faccount\u002Ftokens.\n\n---\n\n**Important:** Once `VERCEL_TOKEN` is exported as an environment variable, the Vercel CLI reads it natively — **do not pass it as a `--token` flag**. Putting secrets in command-line arguments exposes them in shell history and process listings.\n\n```bash\n# Bad — token visible in shell history and process listings\nvercel deploy --token \"vca_abc123\"\n\n# Good — CLI reads VERCEL_TOKEN from the environment\nexport VERCEL_TOKEN=\"vca_abc123\"\nvercel deploy\n```\n\n## Step 2: Locate the Project and Team\n\nSimilarly, check for the project ID and team scope. These let the CLI target the right project without needing `vercel link`.\n\n```bash\n# Check environment\nprintenv VERCEL_PROJECT_ID\nprintenv VERCEL_ORG_ID\n\n# Or check .env\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\n**If you have a project URL** (e.g. `https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project`), extract the team slug:\n\n```bash\n# e.g. \"my-team\" from \"https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project\"\necho \"$PROJECT_URL\" | sed 's|https:\u002F\u002Fvercel.com\u002F||' | cut -d\u002F -f1\n```\n\n**If you have both `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` in your environment**, export them — the CLI will use these automatically and skip any `.vercel\u002F` directory:\n\n```bash\nexport VERCEL_ORG_ID=\"\u003Corg-id>\"\nexport VERCEL_PROJECT_ID=\"\u003Cproject-id>\"\n```\n\nNote: `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` must be set together — setting only one causes an error.\n\n## CLI Setup\n\nEnsure the Vercel CLI is installed:\n\n```bash\nnpm install -g vercel\nvercel --version\n```\n\n## Deploying a Project\n\nAlways deploy as **preview** unless the user explicitly requests production. Choose a method based on what you have available.\n\n### Quick Deploy (have project ID — no linking needed)\n\nWhen `VERCEL_TOKEN` and `VERCEL_PROJECT_ID` are set in the environment, deploy directly:\n\n```bash\nvercel deploy -y --no-wait\n```\n\nWith a team scope (either via `VERCEL_ORG_ID` or `--scope`):\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nProduction (only when explicitly requested):\n\n```bash\nvercel deploy --prod --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Full Deploy Flow (no project ID — need to link)\n\nUse this when you have a token and team but no pre-existing project ID.\n\n#### Check project state first\n\n```bash\n# Does the project have a git remote?\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# Is it already linked to a Vercel project?\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n```\n\n#### Link the project\n\n**With git remote (preferred):**\n\n```bash\nvercel link --repo --scope \u003Cteam-slug> -y\n```\n\nReads the git remote and connects to the matching Vercel project. Creates `.vercel\u002Frepo.json`. More reliable than plain `vercel link`, which matches by directory name.\n\n**Without git remote:**\n\n```bash\nvercel link --scope \u003Cteam-slug> -y\n```\n\nCreates `.vercel\u002Fproject.json`.\n\n**Link to a specific project by name:**\n\n```bash\nvercel link --project \u003Cproject-name> --scope \u003Cteam-slug> -y\n```\n\nIf the project is already linked, check `orgId` in `.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` to verify it matches the intended team.\n\n#### Deploy after linking\n\n**A) Git Push Deploy — has git remote (preferred)**\n\nGit pushes trigger automatic Vercel deployments.\n\n1. **Ask the user before pushing.** Never push without explicit approval.\n2. Commit and push:\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n3. Vercel builds automatically. Non-production branches get preview deployments.\n4. Retrieve the deployment URL:\n   ```bash\n   sleep 5\n   vercel ls --format json --scope \u003Cteam-slug>\n   ```\n   Find the latest entry in the `deployments` array.\n\n**B) CLI Deploy — no git remote**\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Deploying from a Remote Repository (code not cloned locally)\n\n1. Clone the repository:\n   ```bash\n   git clone \u003Crepo-url>\n   cd \u003Crepo-name>\n   ```\n2. Link to Vercel:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug> -y\n   ```\n3. Deploy via git push (if you have push access) or CLI deploy.\n\n### About `.vercel\u002F` Directory\n\nA linked project has either:\n- `.vercel\u002Fproject.json` — from `vercel link`. Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — from `vercel link --repo`. Contains `orgId`, `remoteName`, and a `projects` map.\n\nNot needed when `VERCEL_ORG_ID` + `VERCEL_PROJECT_ID` are both set in the environment.\n\n**Do NOT** run `vercel ls`, `vercel project inspect`, or `vercel link` in an unlinked directory to detect state — they will interactively prompt or silently link as a side-effect. Only `vercel whoami` is safe to run anywhere.\n\n## Managing Environment Variables\n\n```bash\n# Set for all environments\necho \"value\" | vercel env add VAR_NAME --scope \u003Cteam-slug>\n\n# Set for a specific environment (production, preview, development)\necho \"value\" | vercel env add VAR_NAME production --scope \u003Cteam-slug>\n\n# List environment variables\nvercel env ls --scope \u003Cteam-slug>\n\n# Pull env vars to local .env file\nvercel env pull --scope \u003Cteam-slug>\n\n# Remove a variable\nvercel env rm VAR_NAME --scope \u003Cteam-slug> -y\n```\n\n## Inspecting Deployments\n\n```bash\n# List recent deployments\nvercel ls --format json --scope \u003Cteam-slug>\n\n# Inspect a specific deployment\nvercel inspect \u003Cdeployment-url>\n\n# View build logs\nvercel logs \u003Cdeployment-url>\n```\n\n## Managing Domains\n\n```bash\n# List domains\nvercel domains ls --scope \u003Cteam-slug>\n\n# Add a domain to the project\nvercel domains add \u003Cdomain> --scope \u003Cteam-slug>\n```\n\n## Working Agreement\n\n- **Never pass `VERCEL_TOKEN` as a `--token` flag.** Export it as an environment variable and let the CLI read it natively.\n- **Check the environment for tokens before asking the user.** Look in the current env and `.env` files first.\n- **Default to preview deployments.** Only deploy to production when explicitly asked.\n- **Ask before pushing to git.** Never push commits without the user's approval.\n- **Do not read or modify `.vercel\u002F` files directly.** The CLI manages this directory.\n- **Do not curl\u002Ffetch deployed URLs to verify.** Just return the link to the user.\n- **Use `--format json`** when structured output will help with follow-up steps.\n- **Use `-y`** on commands that prompt for confirmation to avoid interactive blocking.\n\n## Troubleshooting\n\n### Token not found\n\nCheck the environment and any `.env` files present:\n\n```bash\nprintenv | grep -i vercel\ngrep -i vercel .env 2>\u002Fdev\u002Fnull\n```\n\n### Authentication error\n\nIf the CLI fails with `Authentication required`:\n- The token may be expired or invalid.\n- Verify: `vercel whoami` (uses `VERCEL_TOKEN` from environment).\n- Ask the user for a fresh token.\n\n### Wrong team\n\nVerify the scope is correct:\n\n```bash\nvercel whoami --scope \u003Cteam-slug>\n```\n\n### Build failure\n\nCheck the build logs:\n\n```bash\nvercel logs \u003Cdeployment-url>\n```\n\nCommon causes:\n- Missing dependencies — ensure `package.json` is complete and committed.\n- Missing environment variables — add with `vercel env add`.\n- Framework misconfiguration — check `vercel.json`. Vercel auto-detects frameworks (Next.js, Remix, Vite, etc.) from `package.json`; override with `vercel.json` if detection is wrong.\n\n### CLI not installed\n\n```bash\nnpm install -g vercel\n```\n",{"name":5,"metadata":23,"description":7},{"author":24,"version":25},"vercel","1.0.0","main","5593cf3c72898ea9fc67225d452fe38f866ba6dd",".goose\u002Fskills\u002Fvercel-cli-with-tokens","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE","https:\u002F\u002Fgithub.com\u002Faicreator350","2026-05-18 03:39:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add aicreator350\u002FaurionOFFICIELLE --skill vercel-cli-with-tokens",{"tool":38,"command":39},"bunx","bunx skills add aicreator350\u002FaurionOFFICIELLE --skill vercel-cli-with-tokens",{"tool":41,"command":42},"pnpm","pnpm dlx skills add aicreator350\u002FaurionOFFICIELLE --skill vercel-cli-with-tokens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002F.goose\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",true,[],[47,56,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":51,"licenseFileUrl":52,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M74CAJWR9WB6DX1HF2V461Y0","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M74CAFWC2H75GJ81B39C9RSW","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M74CA9N2HTGCKJ93AE9NQMHA","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M74CA364D4EVDXZZQRVK1Z73","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M74C9YQZX1GVS18V0AYCYPZE","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-composition-patterns\u002FSKILL.md",[],[],{"skillNo":85,"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":86,"categories":87,"keywords":88,"publishedAt":18},"01M74C9SEYD6F764Q1JACZX3A6","https:\u002F\u002Fgithub.com\u002Faicreator350\u002FaurionOFFICIELLE\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[]]