Skip to content
TrustedSkillsbeta
Back to all skills

Nextjs Client Cookie Pattern

Checked
wsimmonds·vlatest·frontend·MIT

Helps with Next.js, client-side as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wsimmonds/claude-nextjs-skills --skill nextjs-client-cookie-pattern -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wsimmonds

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 wsimmonds/claude-nextjs-skills at 9e0aa5f99b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9e0aa5f99b
Manifest
nextjs-client-cookie-pattern/SKILL.md
Scanned
1 file, 367 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

This pattern enables AI agents to securely manage client-side cookies within Next.js applications, ensuring session persistence and user state retention across page transitions without server round-trips. It leverages the cookies package to handle secure storage of sensitive data like authentication tokens directly in the browser environment.

When to use it

  • Implementing login flows where users need to stay logged in while navigating between client-side rendered pages.
  • Managing user preferences or shopping cart state that must persist across multiple page views without re-fetching from a database.
  • Building single-page application (SPA) experiences within a Next.js framework that require local session management.
  • Handling temporary tokens or non-sensitive identifiers that need to be read by client-side logic immediately upon page load.

Key capabilities

  • Securely set and read cookies using the cookies package with configurable options like path, domain, and secure flags.
  • Automatically handle cookie serialization and deserialization for complex data structures.
  • Integrate seamlessly with Next.js App Router or Pages Router architectures.
  • Provide a programmatic interface to manage cookie lifetimes and expiration logic.

Example prompts

"Create a login function that stores the JWT token in a secure HttpOnly cookie using the Next.js cookies package." "Implement a client-side state manager that reads user preferences from a localStorage fallback and syncs them to a secure cookie on update." "Write a middleware hook that validates an authentication cookie before rendering protected dashboard components."

Tips & gotchas

Ensure you configure the secure flag correctly; it must be true for cookies to work over HTTPS, but this may prevent them from working in local development environments without specific proxy setups. Always validate cookie contents on the server side immediately after reading them to mitigate potential tampering risks.