Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionruntime-debugExecute the skills CLI command in your project's root directory to begin installation:
Fetches runtime-debug from vercel/next.js and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate runtime-debug. Access via /runtime-debug in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
138.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
138.7K
stars
Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.
IS_WEBPACK_TEST=1 forces webpack (turbopack is default), NEXT_SKIP_ISOLATE=1 skips packing next.js.NEXT_SKIP_ISOLATE=1.Set __NEXT_SHOW_IGNORE_LISTED=true to disable the ignore-list filtering in dev server error output. By default, Next.js collapses internal frames to at ignore-listed frames, which hides useful context when debugging framework internals. Defined in packages/next/src/server/patch-error-inspect.ts.
When user next build starts bundling internal Node-only helpers unexpectedly:
.next/server/.../page.js.nft.json).next/dist/server/stream-utils/node-stream-helpers.js, node:stream/promises).test-start-webpack assertion that reads the route trace and traced server chunks, and fails on forbidden internals. This validates user-project bundling (not publish-time runtime bundling).To prove what user bundling includes, emit webpack stats from the app's next.config.js:
// next.config.js
module.exports = {
webpack(config) {
config.profile = true
return config
},
}
Then use stats.toJson({ modules: true, chunks: true, reasons: true }) and diff webpack-stats-server.json between modes. This gives concrete inclusion reasons (e.g. which module required node:stream/promises) and is more reliable than analyzer HTML alone.
$flags - flag wiring (config/schema/define-env/runtime env)$dce-edge - DCE-safe require patterns and edge constraints$react-vendoring - entry-base boundaries and vendored ReactMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
runtime-debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added runtime-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
runtime-debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added runtime-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 70