Type-safe URL query state management for Next.js with 42 prioritized best practices across parser configuration, setup, and server integration.
Works with
Covers critical parser configuration (typed parsers, defaults, enums, arrays, JSON, dates) and adapter setup (NuqsAdapter, 'use client' directives, Next.js version compatibility)
Includes high-impact state management patterns using useQueryStates, functional updates, null clearing, and controlled inputs
Provides server integration guidance fo
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnuqsExecute the skills CLI command in your project's root directory to begin installation:
Fetches nuqs from pproenca/dot-skills 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 nuqs. Access via /nuqs 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
4
total installs
4
this week
95
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
95
stars
Comprehensive guide for type-safe URL query state management with nuqs in Next.js applications. Contains 42 rules across 8 categories, prioritized by impact to guide code generation, refactoring, and code review.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Parser Configuration | CRITICAL | parser- |
| 2 | Adapter & Setup | CRITICAL | setup- |
| 3 | State Management | HIGH | state- |
| 4 | Server Integration | HIGH | server- |
| 5 | Performance Optimization | MEDIUM | perf- |
| 6 | History & Navigation | MEDIUM | history- |
| 7 | Debugging & Testing | LOW-MEDIUM | debug- |
| 8 | Advanced Patterns | LOW | advanced- |
parser-use-typed-parsers - Use typed parsers for non-string valuesparser-with-default - Use withDefault for non-nullable stateparser-enum-validation - Use enum parsers for constrained valuesparser-array-format - Choose correct array parser formatparser-json-validation - Validate JSON parser inputparser-date-format - Select appropriate date parserparser-index-offset - Use parseAsIndex for 1-based URL displayparser-hex-colors - Use parseAsHex for color valuessetup-nuqs-adapter - Wrap app with NuqsAdaptersetup-use-client - Add 'use client' directive for hookssetup-import-server - Import server utilities from nuqs/serversetup-nextjs-version - Ensure compatible Next.js versionsetup-shared-parsers - Define shared parsers in dedicated filestate-use-query-states - Use useQueryStates for related parametersstate-functional-updates - Use functional updates for derived statestate-clear-with-null - Clear URL parameters with nullstate-controlled-inputs - Handle controlled input value properlystate-avoid-derived - Avoid derived state from URL parametersstate-options-inheritance - Use withOptions for parser-level configurationstate-setter-return - Use setter return value for URL accessserver-search-params-cache - Use createSearchParamsCache for Server Componentsserver-shallow-false - Use shallow:false to trigger server re-rendersserver-use-transition - Integrate useTransition for loading statesserver-parse-before-get - Call parse() before get() in Server Componentsserver-share-parsers - Share parsers between client and serverserver-next15-async - Handle async searchParams in Next.js 15+perf-throttle-updates - Throttle rapid URL updatesperf-clear-on-default - Use clearOnDefault for clean URLsperf-avoid-rerender - Memoize components using URL stateperf-serialize-utility - Use createSerializer for link URLsperf-debounce-search - Debounce search input before URL updatehistory-push-navigation - Use history:push for navigation-like statehistory-replace-ephemeral - Use history:replace for ephemeral statehistory-scroll-behavior - Control scroll behavior on URL changeshistory-back-sync - Handle browser back/forward navigationdebug-enable-logging - Enable debug logging for troubleshootingdebug-common-errors - Diagnose common nuqs errorsdebug-testing - Test components with URL stateadvanced-custom-parsers - Create custom parsers for complex typesadvanced-url-keys - Use urlKeys for shorter URLsadvanced-eq-function - Implement eq function for object parsersadvanced-framework-adapters - Use framework-specific adaptersRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| AGENTS.md | Complete compiled guide with all rules |
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
Make 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.
pproenca/dot-skills
pproenca/dot-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
I recommend nuqs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
nuqs reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: nuqs is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: nuqs is focused, and the summary matches what you get after install.
I recommend nuqs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
nuqs reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in nuqs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for nuqs matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: nuqs is the kind of skill you can hand to a new teammate without a long onboarding doc.
nuqs is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 44