nuqs Scaffolder

Generate a coherent set of nuqs files from one spec. The skill is template-driven — you read the spec, copy the templates, and substitute placeholders. No build step, no codegen runtime; the templates ARE the artifact.

When to Apply

Use this skill when:

• A new Next.js page needs URL-backed filters, pagination, search, or sort state
• You're standardising an existing page's ad-hoc useState filters onto nuqs
• A code review keeps catching client/server drift in parser definitions — this skill makes drift mechanically impossible because both sides import the same map
• A user asks to "add Standard Schema validation to these query params for tRPC" — the generated searchParams.server.ts already exports the schema

If the codebase has legacy nuqs patterns instead, run the nuqs-codemod-runner skill first.

How to Use

1. Read or create a spec. Start from assets/templates/spec.template.json and fill in name, module, and params. See "Spec Format" below.
2. Render each template by replacing placeholders with values derived from the spec.
3. Write each rendered file to the path computed from config.json (overridable per-call).
4. Show the user the diff before committing — this skill never modifies existing files; if a target path exists, ask before overwriting.