Nuxt Data
CheckedHelps with Nuxt, data as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add secondsky/claude-skills --skill nuxt-data -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
secondsky
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned secondsky/claude-skills at 8837836131.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8837836131
- Scanned
- 8 files, 4,057 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill provides guidance and reference materials for developing Nuxt 4 applications, specifically focusing on data management techniques. It offers information on composables, data fetching methods (like useFetch, useAsyncData, and $fetch), and state management patterns, including integration with Pinia. The goal is to help developers build robust and efficient frontend user interfaces within the Nuxt framework.
When to use it
- When building custom composables that manage complex application state.
- When debugging issues related to state management or reactivity in your Nuxt application.
- When implementing data fetching logic, especially when dealing with reactive parameters or pagination.
- When setting up and integrating Pinia for more advanced state management needs within a Nuxt project.
Key capabilities
- Data Fetching Methods: Provides details on
useFetch,useAsyncData, and$fetchincluding their use cases, SSR support, caching behavior, and reactivity. - Composable Naming Conventions: Offers guidance on naming conventions for composables (using prefixes like "use" and "fetch").
useStatePattern: Explains how to create shared, reactive state usinguseStatethat persists across component instances (singleton pattern).- Pinia Integration: Provides resources for setting up Pinia stores with getters, actions, and SSR support.
- Reference Materials: Includes references to specific documents covering composables, data fetching, and Pinia integration.
Example prompts
- "How do I use
useFetchin Nuxt 4?" - "What's the difference between
useStateandrefin Nuxt?" - "Can you give me an example of integrating Pinia with SSR in a Nuxt application?"
Tips & gotchas
- Singleton vs. Per-Call Composables: Be mindful of whether your composable should be a singleton (shared across all components) or per-call.
useStatecreates singletons. - Reactivity Issues: Pay attention to shallow versus deep reactivity when implementing data fetching with reactive parameters. The skill's references can help troubleshoot these issues.
- SSR Considerations: When using browser APIs, ensure your patterns are SSR-safe as described in the
references/composables.mddocument.