nuqs

Index nuqs best practices for Next.js URL state management.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/PheonixCodder/Beeclean-Production --skill nuqs-pheonixcodder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuqs
Source: https://github.com/PheonixCodder/Beeclean-Production/tree/main/.agents/skills/nuqs
Command: npx skills add https://github.com/PheonixCodder/Beeclean-Production --skill nuqs-pheonixcodder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

nuqs best practices for type-safe URL query state in Next.js applications. This skill guides writing, reviewing, or refactoring code that uses nuqs for URL state management, including useQueryState, useQueryStates, search params, and server components.

Core Features & Use Cases

  • 42 rules across 8 categories to standardize URL state handling.
  • Guidance for client/server integration, parsers, and shared configurations.
  • Practical examples for Next.js routing with URL state and robust defaults.

Quick Start

Review the AGENTS.md and references to align your project with nuqs best-practice patterns and implement the recommended parsers and options.

Frequently Asked Questions about nuqs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage URL state in Next.js server components?

Manage URL state in Next.js server components by applying type-safe query state patterns with useQueryState and useQueryStates to ensure consistent client/server boundary integration. This skill indexes 42 rules across 8 categories to standardize search params handling.

What is the best way to type-safe URL search params in Next.js?

The best way to handle type-safe URL search params in Next.js is by using parsers and shared configurations to enforce robust defaults. This skill provides guidance for refactoring code with useQueryState to improve correctness and performance.

Can I use useQueryState across client and server boundaries in Next.js?

Yes, you can use useQueryState across client and server boundaries in Next.js by following structured metadata rules. This skill guides developers on safely integrating URL state management to ensure consistency when refactoring or auditing search params.

How do I standardize URL state handling for large Next.js applications?

Standardize URL state handling for Next.js applications by adopting 42 best-practice rules across 8 categories. This skill provides structured guidance for parsers, shared configurations, and robust defaults to maintain safety and consistency during refactoring.

Why does my URL state reset during Next.js server component navigation?

URL state resets during Next.js server component navigation often occur due to incorrect parser configurations or missing defaults. This skill indexes best-practice patterns for useQueryStates to prevent state loss and improve routing correctness.

When should I not use useQueryState for Next.js search params?

You should not use useQueryState for Next.js search params when managing highly ephemeral UI state that does not need to be reflected in the URL. This skill helps audit URL state usage to determine when alternative client-side state management is more appropriate.