Conciseness

The body is short overall but spends tokens on persona fluff ('You are a Vercel deployment expert...') and a 'When to Use' list that duplicates the description's triggers; those sections could be trimmed.

Actionability

Pattern subsections are one-line abstractions ('Properly configure environment variables', 'Choose the right runtime'), the Anti-Patterns have no explanation beyond headers, and the Sharp Edges 'Solution' column ends in trailing colons with no actual solution, leaving only minimal high-level hints.

Workflow Clarity

There is no sequenced deployment workflow — only principles, patterns, and lists — and no validation checkpoints for a production-deploy process that is inherently risky, so it sits at a rough/incomplete sequence level.

Progressive Disclosure

Content is organized into clearly headed sections (Capabilities, Requirements, Patterns, Anti-Patterns, Sharp Edges) with no nested references; structure is clean, though the thin pattern/sharp-edge bodies could live in reference files with real detail.

Specificity

The phrase 'Expert knowledge for deploying to Vercel with Next.js' names the domain clearly but offers only one minimal, generic action ('deploying'); it does not enumerate concrete deployment actions like configuring env vars, choosing runtimes, or setting up previews.

Completeness

It includes an explicit 'Use when:' clause (the 'when') and a stated purpose ('deploying to Vercel with Next.js' as the 'what'); the 'what' is somewhat vague ('Expert knowledge') which keeps it just below a 5.

Trigger Term Quality

'Use when: vercel, deploy, deployment, hosting, production.' provides good natural keyword coverage that users would commonly say, though it misses a few synonyms/extensions such as 'ship to vercel' or 'next.js deploy'.

Distinctiveness Conflict Risk

The Vercel + Next.js pairing carves a fairly clear niche, but generic triggers like 'deploy', 'hosting', and 'production' create minor overlap risk with other hosting/deployment skills.