vercel-ops
Skill0 starsChanged 2 months agoMITView on GitHub
Use when the user configures Vercel deploy, project env (names only), Next.js app router hosting, preview URLs, or vercel.json. Not for inventing visual UI, not for frontend-design aesthetics, not for Mongo/Supabase schema.
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- automation-audit-opsSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- found-this-designSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-craftSkill
- scroll-worldSkill
- skill-stocktakeSkill
- smartbook-ingestSkill
- smartdocSkill
- supabase-opsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
NO UI generation: Do not design or style user interfaces, landing pages, or components.
- Distinctive: line 26
NO Design Bank access: Do not search, crawl, or load Design Bank assets.
- Distinctive: line 27
NO secret exposure: Never print secret tokens, production tokens, or environment variable values.
- Very specific: line 28
NO auto-prod deploys: Never run vercel --prod automatically without explicit user command.
- Very specific: line 36
Verify vercel.json schema, header definitions, redirects, and edge middleware constraints via Context7.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vercel Ops
First-party deployment and configuration specialist for Vercel hosting. Handles vercel.json, Next.js App Router deployment configuration, edge middleware routing, preview URLs, and environment variable naming.
Boundaries & Handoffs
| Need | Route |
| Visual UI, layout, frontend styling, design aesthetics | found-this-design → impeccable (Design Bank) |
| Supabase Auth, RLS, Edge Functions, Postgres schema | supabase-ops |
| MongoDB schemas, indexing, aggregation | mongodb-ops |
| GitHub CI/CD, PR management, Actions workflows | gh-axi |
| Official Next.js and Vercel hosting reference | Context7 (next, vercel) |
| Vercel deploy configuration, routing, headers, preview URLs | vercel-ops |
Explicit Non-Goals & Safety
- NO UI generation: Do not design or style user interfaces, landing pages, or components. Vendor
frontend-designpackages are foreign and excluded. UI belongs strictly toimpeccable. Vendor stack ≠ UI. - NO Design Bank access: Do not search, crawl, or load Design Bank assets.
- NO secret exposure: Never print secret tokens, production tokens, or environment variable values. Reference variable names only.
- NO auto-prod deploys: Never run
vercel --prodautomatically without explicit user command. Favor preview deployments and GitHub PR checks viagh-axi.
Procedure
- Repo Evidence First:
- Inspect
vercel.json,next.config.*,package.json, and existing build/deploy scripts. - Detect framework output directories, runtime version requirements, and route rewrites.
- Inspect
- Official Documentation via Context7:
- Verify
vercel.jsonschema, header definitions, redirects, and edge middleware constraints via Context7.
- Verify
- Deployment & Routing Configuration:
- Shape security headers, caching headers, routing rewrites, and function region configs.
- Integrate with GitHub workflows via
gh-axifor automated preview comments and deployments.
Finish Gate
- State all modified files (e.g.
vercel.json,next.config.*, GitHub Actions workflows). - Execute project build/lint verification (
npm run build,npm run lint) or reportNOT_CONFIGUREDif none exist.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.