Skip to content
TrustedSkillsbeta
Back to all skills

Nextjs App Router Patterns

Checked
wshobson·vlatest·frontend·MIT

Helps with Next.js, patterns 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 wshobson/agents --skill nextjs-app-router-patterns -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Commit
46891e7e60
Manifest
plugins/frontend-mobile-development/skills/nextjs-app-router-patterns/SKILL.md
Scanned
2 files, 522 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

What it does

This skill helps developers implement and optimize routing patterns in Next.js applications using the App Router. It enables dynamic route handling, nested layouts, and efficient data fetching strategies like Server Components and API Routes.

When to use it

  • Building a complex Next.js application with multiple pages and nested routes
  • Implementing dynamic routes for content management systems or e-commerce platforms
  • Optimizing performance by leveraging Server Components and streaming responses

Key capabilities

  • Support for dynamic routing using [slug] and [[...slug]] patterns
  • Integration of nested layouts with layout.js files
  • Use of Server Components for data fetching and rendering
  • API Route creation for handling backend logic within the Next.js app directory

Example prompts

  • "Set up a dynamic route for blog posts using the App Router in Next.js."
  • "Create a nested layout structure for an admin dashboard with the App Router."
  • "Implement Server Components to fetch and display user data from an API endpoint."

Tips & gotchas

  • Ensure your app directory is properly structured before implementing dynamic routes.
  • Be mindful of file naming conventions, as they directly affect route behavior in Next.js.