Use this skill when adding or changing framework feature flags in Next.js internals.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionflagsExecute the skills CLI command in your project's root directory to begin installation:
Fetches flags 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 flags. Access via /flags 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 adding or changing framework feature flags in Next.js internals.
All flags need: config-shared.ts (type) → config-schema.ts (zod). If the flag is consumed in user-bundled code (client components, edge routes, app-page.ts template), also add it to define-env.ts for build-time injection. Runtime-only flags consumed exclusively in pre-compiled bundles can skip define-env.ts.
Client/bundled code only (e.g. __NEXT_PPR in client components): define-env.ts is sufficient. Webpack/Turbopack replaces process.env.X at the user's build time.
Pre-compiled runtime bundles (e.g. code in app-render.tsx): The flag must also be set as a real process.env var at runtime, because app-render.tsx runs from pre-compiled bundles where define-env.ts doesn't reach. Two approaches:
next-server.ts + export/worker.ts. Both code paths stay in one bundle. Simple but increases bundle size.next-runtime.webpack-config.js (scoped to bundleType === 'app'), new taskfile tasks, update module.compiled.js selector, and still set env var in next-server.ts + export/worker.ts for bundle selection. Eliminates dead code but adds build complexity.For runtime flags, also add the field to the NextConfigRuntime Pick type in config-shared.ts.
next-runtime.webpack-config.js (rspack) via taskfile.js bundle tasks.src/server/route-modules/app-page/module.compiled.js based on process.env vars.{turbo/webpack} × {experimental/stable/nodestreams/experimental-nodestreams} × {dev/prod} = up to 16 bundles per route type.define-env.ts affects user bundling, not pre-compiled runtime internals.process.env.X checks in app-render.tsx are either replaced by DefinePlugin at runtime-bundle-build time, or read as actual env vars at server startup. They are NOT affected by the user's defines from define-env.ts.next-runtime.webpack-config.js must be scoped to the correct bundleType (e.g. app only, not server) to avoid replacing assignment targets in next-server.ts.$dce-edge - DCE-safe require patterns and edge constraints$react-vendoring - entry-base boundaries and vendored React$runtime-debug - reproduction and verification workflowMake 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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend flags for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added flags from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
flags has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in flags — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
flags fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in flags — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
flags reduced setup friction for our internal harness; good balance of opinion and flexibility.
flags is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
flags has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: flags is focused, and the summary matches what you get after install.
showing 1-10 of 72