메뉴
Harden a Vercel deployment with security headers, CSP, bot protection, and deployment configuration
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/edfenton/claude-skills --skill vercel-harden명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Scaffold a pnpm + Turborepo MERN monorepo with Next.js, tooling, tests, CI, and optional GitHub repo creation.
Configure GitHub repository security with branch protection, Dependabot, security scanning, and CI workflows. Integrates with mern-scaffold, nean-scaffold, and iOS projects.
Add authentication to an iOS app with Sign in with Apple, biometrics, and Keychain storage.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | vercel-harden |
| description | Harden a Vercel deployment with security headers, CSP, bot protection, and deployment configuration |
| arguments | [--check-only] [--plan hobby|pro] |
Audit and harden a Next.js project deployed on Vercel. Applies security headers at the edge, configures CSP, blocks malicious bots, and provides a dashboard checklist for manual Vercel settings.
--check-only — Audit current security posture without making changes--plan hobby|pro — Target Vercel plan (default: pro). Controls which features are available (WAF rules, bot protection, etc.)Scan the project for existing security configuration:
- next.config.ts: poweredByHeader, headers() (static headers only — NOT CSP)
- proxy.ts: CSP header, bot blocking, honeypot paths
- vercel.json: edge-level headers
- robots.ts: bot disallow rules
Report findings as a checklist with pass/fail for each item.
If not --check-only, apply these changes:
poweredByHeader: falseheaders() function applying non-CSP security headers to /:path*reference/vercel-harden-reference.mdWARNING: Nonce-based CSP and
'strict-dynamic'are incompatible with Next.js. Next.js generates inline<script>tags for hydration, routing, and RSC payloads that cannot receive nonces. Using nonces or'strict-dynamic'will break the app (white page, broken navigation, non-functional interactive elements).
proxy.ts (not next.config.ts headers()) so it runs per-requestscript-src 'self' 'unsafe-inline' — this is the only approach compatible with Next.js@vercel/analytics or @vercel/speed-insights are installedapplication/ld+json must NOT receive noncesproxy.tsrobots.ts to block AI scrapers and SEO botsAfter changes, verify with:
curl -I https://<deployment-url>
Check for presence of all security headers and absence of X-Powered-By.
Also run:
pnpm test
pnpm build
pnpm test:e2e
After deployment, open the browser console and check for CSP violation errors. If any appear, update the CSP directives to allow the blocked resource.
Print actionable checklist for manual Vercel dashboard configuration. Include only items relevant to the --plan argument.
All code changes must follow red-green-refactor:
See reference/vercel-harden-reference.md for: