nextjs-app-router
Nextjs App Router
Overview
Use this skill to design App Router implementations that are predictable in rendering, caching, and navigation behavior.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Server/client and cache rules:
references/server-client-and-cache-rules.md
Templates And Assets
- App Router architecture template:
assets/app-router-architecture-template.md
- App Router verification checklist:
assets/app-router-checklist.md
Inputs To Gather
- Route hierarchy, layout composition, and navigation requirements.
- Server/client interaction boundaries.
- Freshness, SEO, and caching constraints.
- Error/loading behavior requirements.
- Route param/search param/request payload contracts and ownership boundaries.
Deliverables
- Route/layout map with rendering strategy.
- Data-fetch and cache/revalidation policy.
- Error/loading/not-found boundary plan.
- Verification evidence for transition and consistency behavior.
Workflow
- Define route/layout architecture in
assets/app-router-architecture-template.md. - Apply server/client boundary rules from
references/server-client-and-cache-rules.md. - Parse and normalize route/search/action inputs at boundaries into explicit typed shapes.
- Configure fetch/cache/revalidation policy per route criticality.
- Implement explicit loading/error/not-found boundaries.
- Validate with
assets/app-router-checklist.md.
Quality Standard
- Route tree and ownership are explicit.
- Server/client boundaries are minimal and intentional.
- Cache policy matches data freshness requirements.
- Navigation preserves data consistency across transitions.
- Server actions and route handlers avoid repeated cast-heavy shape fixes by using boundary-normalized contracts.
Failure Conditions
- Stop when boundaries between server and client are ambiguous.
- Stop when caching strategy risks stale or inconsistent user state.
- Escalate when critical route behavior cannot be made deterministic.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9