agentleFS
thongdn-itthongdn-it/react-agent-skills/skills/nuqs/SKILL.md

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
  1. Common:

    Read individual reference files for detailed explanations and code examples:

    line 103

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

PriorityCategoryImpactPrefix
1Parser ConfigurationCRITICALparser-
2Adapter & SetupCRITICALsetup-
3State ManagementHIGHstate-
4Server IntegrationHIGHserver-
5Performance OptimizationMEDIUMperf-
6History & NavigationMEDIUMhistory-
7Debugging & TestingLOW-MEDIUMdebug-
8Advanced PatternsLOWadvanced-

Quick Reference

1. Parser Configuration (CRITICAL)

  • parser-use-typed-parsers - Use typed parsers for non-string values
  • parser-with-default - Use withDefault for non-nullable state
  • parser-enum-validation - Use enum parsers for constrained values
  • parser-array-format - Choose correct array parser format
  • parser-json-validation - Validate JSON parser input
  • parser-date-format - Select appropriate date parser
  • parser-index-offset - Use parseAsIndex for 1-based URL display
  • parser-hex-colors - Use parseAsHex for color values

2. Adapter & Setup (CRITICAL)

  • setup-nuqs-adapter - Wrap app with NuqsAdapter
  • setup-use-client - Add 'use client' directive for hooks
  • setup-import-server - Import server utilities from nuqs/server
  • setup-nextjs-version - Ensure compatible Next.js version
  • setup-shared-parsers - Define shared parsers in dedicated file

3. State Management (HIGH)

  • state-use-query-states - Use useQueryStates for related parameters
  • state-functional-updates - Use functional updates for derived state
  • state-clear-with-null - Clear URL parameters with null
  • state-controlled-inputs - Handle controlled input value properly
  • state-avoid-derived - Avoid derived state from URL parameters
  • state-options-inheritance - Use withOptions for parser-level configuration
  • state-setter-return - Use setter return value for URL access

4. Server Integration (HIGH)

  • server-search-params-cache - Use createSearchParamsCache for Server Components
  • server-shallow-false - Use shallow:false to trigger server re-renders
  • server-use-transition - Integrate useTransition for loading states
  • server-parse-before-get - Call parse() before get() in Server Components
  • server-share-parsers - Share parsers between client and server
  • server-next15-async - Handle async searchParams in Next.js 15+

5. Performance Optimization (MEDIUM)

  • perf-throttle-updates - Throttle rapid URL updates
  • perf-clear-on-default - Use clearOnDefault for clean URLs
  • perf-avoid-rerender - Memoize components using URL state
  • perf-serialize-utility - Use createSerializer for link URLs
  • perf-debounce-search - Debounce search input before URL update

6. History & Navigation (MEDIUM)

  • history-push-navigation - Use history:push for navigation-like state
  • history-replace-ephemeral - Use history:replace for ephemeral state
  • history-scroll-behavior - Control scroll behavior on URL changes
  • history-back-sync - Handle browser back/forward navigation

7. Debugging & Testing (LOW-MEDIUM)

  • debug-enable-logging - Enable debug logging for troubleshooting
  • debug-common-errors - Diagnose common nuqs errors
  • debug-testing - Test components with URL state

8. Advanced Patterns (LOW)

  • advanced-custom-parsers - Create custom parsers for complex types
  • advanced-url-keys - Use urlKeys for shorter URLs
  • advanced-eq-function - Implement eq function for object parsers
  • advanced-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

FileDescription
AGENTS.mdComplete compiled guide with all rules
references/_sections.mdCategory definitions and ordering
assets/templates/_template.mdTemplate for new rules
metadata.jsonVersion and reference information

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.