Skills nextjs-best-practices
๐Ÿ“ฆ

nextjs-best-practices

Content revision r2 Safe โš™๏ธ External commands

Build Better Next.js App Router Applications

App Router decisions can create unnecessary client code, stale data, and weak route structure. This skill provides concise guidance for components, fetching, routing, caching, metadata, and performance.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "nextjs-best-practices" from https://skillstore.io/skills/sickn33-nextjs-best-practices.md and its manifest at https://skillstore.io/api/skills/sickn33-nextjs-best-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "nextjs-best-practices". A product page fetches database data and opens an interactive cart drawer.

Expected outcome:

  • Keep the product page as a Server Component for direct data access.
  • Move cart state and event handlers into a focused Client Component.
  • Add loading and error files at the route boundary.

Using "nextjs-best-practices". A dashboard must refresh summary data every minute.

Expected outcome:

Use time-based revalidation for shared summary data. Use uncached fetching only for information that must reflect every request.

Using "nextjs-best-practices". A form server action accepts account settings.

Expected outcome:

Validate every field on the server, return a typed result, handle failures, and revalidate the affected route after a successful update.

Security Audit

Safe
v6 โ€ข 8/4/2026 Open versioned report

All 14 static findings are false positives caused by Markdown code fences and inline code formatting. The skill is documentation-only and contains no executable commands, prompt injection, or malicious intent.

1
Files scanned
214
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-nextjs-best-practices/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-nextjs-best-practices/security.svg)](https://skillstore.io/skills/sickn33-nextjs-best-practices?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-nextjs-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-nextjs-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-nextjs-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). nextjs-best-practices security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-nextjs-best-practices/audits/6

BibTeX citation

@techreport{sickn33-sickn33-nextjs-best-practices-2026, author = {sickn33}, title = {nextjs-best-practices security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/sickn33-nextjs-best-practices/audits/6}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "nextjs-best-practices security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-nextjs-best-practices/audits/6" identifiers: - type: other value: "skillstore:sickn33-nextjs-best-practices:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a New App Router Feature

Select component boundaries, data flow, route files, and cache behavior before implementation.

Review a Pull Request

Identify unnecessary client components, missing states, weak validation, and avoidable bundle costs.

Define Team Conventions

Create consistent guidance for routing, server actions, metadata, caching, and project organization.

Try These Prompts

Choose a Component Type
Review this component requirement. Decide whether it should be a Server Component, Client Component, or split composition, and explain the decision.
Plan an App Router Page
Plan this App Router page. Recommend route files, data fetching, loading behavior, error handling, metadata, and cache strategy.
Audit a Next.js Feature
Review the supplied Next.js feature against App Router best practices. Prioritize findings for components, validation, caching, routing, images, and bundle size.
Design a Complex Route Architecture
Design an App Router architecture for these requirements. Evaluate route groups, parallel routes, intercepting routes, server actions, cache invalidation, and deployment constraints.

Best Practices

  • Start with Server Components and add client boundaries only for state, effects, or browser events.
  • Match each data source to an explicit caching and revalidation strategy.
  • Provide loading, error, and not-found states at appropriate route boundaries.

Avoid

  • Do not place the client directive across entire route trees without an interaction requirement.
  • Do not fetch server-accessible data in Client Components by default.
  • Do not ship heavy components eagerly when dynamic loading fits the user flow.

Frequently Asked Questions

Does this skill generate a complete Next.js application?
No. It provides architecture, review, and implementation guidance for App Router projects.
Can it choose between Server and Client Components?
Yes. It uses data access, interactivity, state, effects, and event handlers to guide the decision.
Does it cover Next.js caching?
Yes. It covers static caching, time-based revalidation, on-demand revalidation, and uncached requests.
Can it review route handlers and server actions?
Yes. It checks input validation, status handling, typed responses, errors, mutations, and revalidation.
Does it replace official Next.js documentation?
No. Confirm version-specific APIs and deployment behavior with current official documentation.
What context improves its recommendations?
Provide requirements, relevant files, Next.js version, deployment target, data sources, and performance constraints.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

9 downloads ยท 123 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all