Compress Next.js quickstart prompt for Cursor deeplink limit

[mwickett]

Summary

• Compresses prompts/nextjs-quickstart.md from 10,805 → 4,969 URL-encoded chars (limit is 8,000)
• Same sections preserved: keyless mode, code samples, rules, verification, after-setup steps
• All grader keywords retained
• Adds scripts/check-prompt-deeplink-length.ts CI check that fails if any prompt in prompts/ exceeds the 8,000 encoded char limit
• Adds lint:check-prompt-deeplink-length script and CI workflow step

Related

• PR to clerk-evals is here: Compress nextjs eval prompts for Cursor deeplink limit clerk-evals#49

Context

Cursor's "Open in Cursor" deeplink has an 8,000 char limit on the URL-encoded text. The previous prompt was 7,375 raw chars but 10,805 encoded — always exceeding the limit and causing "Invalid text for prompt" errors.

Test plan

• pnpm run lint:check-prompt-deeplink-length passes locally
• Verify "Open in Cursor" button works on the Next.js quickstart docs page
• CI lint job passes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Mar 4, 2026 10:51pm

[manovotny]

I updated the prompt deeplink length check to be stricter and more flexible. 02b1eb1

• Improved output — Color-coded results (green/yellow/red), accurate summary counts that account for excluded files, and actionable failure messages that explain how to fix or bypass.
• Accurate URL measurement — Now measures the full deeplink URL length (using URLSearchParams) instead of just the encoded content length, matching what's actually generated on the site. + works just fine, and is two characters less per space than encodeURIComponent's %20, giving us more of our own characters to work with.
• Fail by default — All prompts now fail CI if they exceed the 8,000 char deeplink URL limit (they were silently failing). Previously, only quickstart prompts were enforced while others just warned. The "Open in Cursor" button won't render for prompts over the limit, so failures should be explicit. There is logic on the clerk.com side that will auto-hide the button if the prompt is over 8,000 characters, but we want an early indicator here stating that's what will happen.
  
• Exclusion list — Added an EXCLUDED_PROMPTS array for prompts that intentionally exceed the limit (e.g., core-3-upgrade.md). This keeps the check strict while allowing deliberate opt-outs.