---
name: vercel-known-pitfalls
description: |
Execute identify and avoid Vercel anti-patterns and common integration mistakes.
Use when reviewing Vercel code for issues, onboarding new developers,
or auditing existing Vercel integrations for best practices violations.
Trigger with phrases like "vercel mistakes", "vercel anti-patterns",
"vercel pitfalls", "vercel what not to do", "vercel code review".
allowed-tools: Read, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---
# Vercel Known Pitfalls
## Prerequisites
- Access to Vercel codebase for review
- Understanding of async/await patterns
- Knowledge of security best practices
- Familiarity with rate limiting concepts
## Instructions
### Step 1: Review for Anti-Patterns
Scan codebase for each pitfall pattern.
### Step 2: Prioritize Fixes
Address security issues first, then performance.
### Step 3: Implement Better Approach
Replace anti-patterns with recommended patterns.
### Step 4: Add Prevention
Set up linting and CI checks to prevent recurrence.
## Output
- Anti-patterns identified
- Fixes prioritized and implemented
- Prevention measures in place
- Code quality improved
## Error Handling
See `{baseDir}/references/errors.md` for comprehensive error handling.
## Examples
See `{baseDir}/references/examples.md` for detailed examples.
## Resources
- [Vercel Security Guide](https://vercel.com/docs/security)
- [Vercel Best Practices](https://vercel.com/docs/best-practices)
