Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay.
Passed 20 of 21 test cases with the skill, and 7 of 21 without it.
and 14 more in the full report
14 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the standard `## Don't want this validation?` section, what configuration property path in `next.config` is documented for setting app-wide validation to manual warning mode?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies experimental.instantInsights.validationLevel set to 'manual-warning' in next.config. | Missed | Passed |
The instructions your model reads when the skill loads.
Write or audit an errors/<slug>.mdx insight-kind page that ships from this repo to nextjs.org and mirrors the fix-card set in the Next.js dev overlay.
Terminology: the frontmatter uses
kind: insightbut the body text calls these "errors" — never "insights". Write "this error", "error pages", "dismiss the error".
next-prerender-random", "write the sync IO docs"errors/*.mdx insight pages (frontmatter has kind: insight)Every decision traces back to one of these. When in doubt, read the source — don't guess.
| What | Source file | How to read it |
|---|---|---|
| Card titles, IDs, groups, snippets, link URLs | packages/next/src/next-devtools/dev-overlay/components/instant/instant-guidance-data.ts | Each FixCard[] array is one error family |
| Error headline (literal text user sees) | packages/next/src/server/app-render/sync-io-messages.ts, blocking-route-messages.ts, etc. | createSyncIOError, createDynamicBodyError, etc. — the template string is the headline |
| Existing page (content to preserve) | errors/<slug>.mdx in this repo | Read the full file; relocate useful content that doesn't fit fix cards into Gotchas or Other options |
| Canonical API docs (terminology) | docs/01-app/ in this repo | Cross-check every API name, directive name, and concept against the published docs |
| Template structure | This skill file (below) | The canonical shape of the page |
| Vercel writing style | The vercel-technical-writing skill in vercel/front (not present here) | Apply end-to-end; see "Voice and style" below for the rules condensed |
FixCard[] in instant-guidance-data.ts. Note every card's id, title, group, link, and snippets.createSyncIOError, createSyncIOClientError, createDynamicBodyError, etc. The headline template (minus the Route "..." prefix) becomes the page title.errors/<slug>.mdx if it exists. Note every pattern, code example, and caveat. You must preserve all useful content — relocate it if the new structure doesn't have a 1:1 slot for it.use cache, cacheLife, cacheTag, connection, Suspense, useEffect, use client, generateStaticParams, etc. Use the exact terminology from the published docs.vercel-technical-writing skill lives in vercel/front; the condensed rules below are the minimum bar.Every page follows this exact shape. Do not add, remove, or reorder sections.
---
title: <literal dev-overlay headline, no period, strip Route "..." prefix>
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.