nuqs
Skill5 starsChanged 9 months agoMITView on GitHub
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 103
Read individual reference files for detailed explanations and code examples:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Community nuqs Best Practices for Next.js
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.
When to Apply
Reference these guidelines when:
- Implementing URL-based state with nuqs
- Setting up nuqs in a Next.js project
- Configuring parsers for URL parameters
- Integrating URL state with Server Components
- Optimizing URL update performance
- Debugging nuqs-related issues
Rule Categories by Priority
| 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- |
Quick Reference
1. Parser Configuration (CRITICAL)
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 values
2. Adapter & Setup (CRITICAL)
setup-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 file
3. State Management (HIGH)
state-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 access
4. Server Integration (HIGH)
server-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+
5. Performance Optimization (MEDIUM)
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 update
6. History & Navigation (MEDIUM)
history-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 navigation
7. Debugging & Testing (LOW-MEDIUM)
debug-enable-logging- Enable debug logging for troubleshootingdebug-common-errors- Diagnose common nuqs errorsdebug-testing- Test components with URL state
8. Advanced Patterns (LOW)
advanced-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 adapters
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| 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 |
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- trycompai/crm★ 12k76% same
- PyModel/react-frontend-skills★ 2397% same
- Aver005/agent-skills★ 2100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- skills/feature-arch/AGENTS.mdAGENTS.md
- skills/msw/AGENTS.mdAGENTS.md
- skills/nextjs/AGENTS.mdAGENTS.md
- skills/nuqs/AGENTS.mdAGENTS.md
- skills/playwright/AGENTS.mdAGENTS.md
- skills/react-hook-form/AGENTS.mdAGENTS.md
- skills/shadcn/AGENTS.mdAGENTS.md
- skills/tailwind/AGENTS.mdAGENTS.md
- skills/tanstack-query/AGENTS.mdAGENTS.md
- skills/tdd/AGENTS.mdAGENTS.md
- skills/ui-design/AGENTS.mdAGENTS.md
- skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/vitest/AGENTS.mdAGENTS.md
- skills/zod/AGENTS.mdAGENTS.md
- feature-archSkill
- mswSkill
- nextjsSkill
- playwrightSkill
- react-hook-formSkill
- reactSkill
- shadcnSkill
- tailwindSkill
- tanstack-querySkill
- tddSkill
- typescriptSkill
- ui-designSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- vitestSkill
- web-design-guidelinesSkill
- zodSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

