ChronicStone/nuxt-ui-tools / skills/consumer/query-state
nuxt-ui-tools-query-state
VerifiedUse this skill when building or debugging URL-backed state with nuxt-ui-tools as a package consumer. Covers codecs, useQueryState, useQueryStates, dynamicQueryState, grouped state, dynamic keys, and practical query-string examples.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1011 B |
| references/codecs.md | markdown | 785 B |
| references/complex-patterns.md | markdown | 2.3 KB |
| references/dynamic-query-state.md | markdown | 1.5 KB |
| references/getting-started.md | markdown | 1.1 KB |
| references/integration.md | markdown | 568 B |
| references/overview.md | markdown | 676 B |
| references/patterns.md | markdown | 943 B |
references/dynamic-query-state.md
View on GitHub# Dynamic Query State
Use `dynamicQueryState(...)` when the URL key set depends on runtime definitions.
This is useful when a static schema like:
```ts
{
page: ...,
size: ...,
}
```
is not enough because the keys themselves are created from runtime data.
## What It Looks Like
You provide:
- `definitions`
the runtime definitions that describe what can exist
- `resolve`
how each definition maps to one or more URL keys and codecs
- `parse`
how URL entries become your domain value
- `serialize`
how your domain value becomes URL entries again
## Concrete Example: Table Filters
The current table runtime uses dynamic query state for UI filters.
The URL namespace is:
```txt
f.ui.{filterKey}
f.ui.{filterKey}~{operator}
```
Examples:
```txt
?f.ui.department=Engineering
?f.ui.salary~gte=100000
?f.ui.hiredAt~before=2024-01-01T00:00:00.000Z
```
In that setup:
- the runtime definitions are the current filter definitions
- `resolve` decides which URL keys each filter may occupy
- `parse` turns matching URL entries into table filter rules
- `serialize` turns filter rules back into URL entries
## When To Use It
Use dynamic query state when:
- the active definitions come from runtime config
- different definitions may expose different query keys
- one domain value needs to fan out into multiple possible URL keys
## When Not To Use It
Do not use it when a fixed grouped schema is enough.
If your key set is known ahead of time, `useQueryStates(...)` is usually the better fit.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |