Token导航 LogoToken导航

Agent Skill · 开发规范

accelint-nextjs-best-practices(accelint Next.js 最佳实践)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

accelint-nextjs-best-practices 是开发规范类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发规范类的 1,265 个 Skill 里排第 268。

总安装 4,889周安装 210GitHub Stars 10下载 1,714核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:accelint-nextjs-best-practices(accelint Next.js 最佳实践)
来源仓库:https://github.com/gohypergiant/agent-skills
仓库路径:skills/accelint-nextjs-best-practices
安装命令:
npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-nextjs-best-practices
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-nextjs-best-practices

这个 Skill 是做什么的

开发规范类 Skill 用来统一代码风格、目录结构和评审口径,产出多为检查清单或改写建议。

用于 Next.js 应用的性能优化和最佳实践指导,支持 Server/Client 组件开发。适用于数据获取、API 路由、Suspense 边界设置及组件重构等场景。可协助减少序列化开销、优化并行操作,并提供构建和性能检查建议。需结合项目现有路由和构建方式,配合本地预览确认代码改动效果。

accelint-nextjs-best-practices 属于开发规范类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/accelint-nextjs-best-practices

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-nex…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

accelint-nextjs-best-practices 怎么安装?

在终端执行 npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-nextjs-best-p…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

accelint-nextjs-best-practices 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

accelint-nextjs-best-practices 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

accelint-nextjs-best-practices 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

accelint-nextjs-best-practices 用的人多吗?

公开数据是累计安装 4,889 次,近一周安装 210 次,下载 1,714 次,GitHub 10 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

accelint-nextjs-best-practices 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发规范类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发规范类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
vercel-react-best-practices

Vercel React 最佳实践 · Codex、Claude

8,490,72025,918操作浏览器MIT通过
web-design-guidelines

网页设计指南 · Codex、Claude

6,686,01625,885需要联网MIT有提醒
remotion-best-practices

Remotion 最佳实践 · Codex、Claude

6,505,6323,027操作浏览器MIT有提醒
supabase-postgres-best-practices

Supabase Postgres 最佳实践 · Codex、Claude

3,175,5232,030需要联网MIT通过
next-best-practices

Next.js 最佳实践 · Codex、Claude

1,848,240841操作浏览器MIT通过
accelint-nextjs-best-practices

accelint Next.js 最佳实践 · 本页

4,88910需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Next.js Best Practices

Comprehensive performance optimization and best practices for Next.js applications, designed for AI agents and LLMs working with Next.js code.

When to Activate This Skill

Use this skill when the task involves:

Writing Next.js Code

  • Creating Server Components or Client Components
  • Implementing Server Actions with "use server"
  • Writing API route handlers
  • Setting up data fetching in RSC (React Server Components)
  • Implementing Suspense boundaries
  • Using Next.js-specific APIs (headers(), cookies(), after())

Refactoring Next.js Code

  • Optimizing server-side data fetching
  • Reducing RSC serialization overhead
  • Converting sequential to parallel operations
  • Restructuring component composition for better performance
  • Migrating between Server and Client Components

Performance Optimization

  • Eliminating server-side waterfalls
  • Reducing response times in API routes and Server Actions
  • Minimizing data transfer at RSC boundaries
  • Implementing request deduplication with React.cache()
  • Using after() for non-blocking operations

Next.js-Specific Issues

  • Authentication/authorization in Server Actions
  • RSC serialization duplication problems
  • Import optimization (barrel file issues)
  • Server vs Client Component decision-making
  • Parallel data fetching patterns

Code Review

  • Reviewing Next.js code for performance anti-patterns
  • Identifying security issues in Server Actions
  • Checking proper Server/Client Component boundaries
  • Ensuring proper authentication patterns
  • Validating Suspense boundary placement

When NOT to Use This Skill

Do not activate for:

  • React-specific optimizations (use accelint-react-best-practices skill)
  • Build configuration (webpack, turbopack) unless Next.js-specific
  • General TypeScript/JavaScript questions (use accelint-ts-best-practices skill)
  • Deployment/hosting configuration
  • Testing setup (use accelint-ts-testing skill)

Example Trigger Phrases

This skill should activate when users say things like:

Performance Issues:

  • "This Next.js API route is slow"
  • "My Server Component is blocking the entire page"
  • "Optimize this Server Action"
  • "The page takes forever to load data"
  • "There's a waterfall in my data fetching"

Security Issues:

  • "Add authentication to this Server Action"
  • "This Server Action needs authorization"
  • "Secure this API route"
  • "Validate input in this Server Action"

Debugging Issues:

  • "Why is my RSC props so large?"
  • "This data is being duplicated in the HTML"
  • "My imports are slow in development"
  • "Should this be a Server or Client Component?"

Code Review:

  • "Review this Next.js code for performance issues"
  • "Is this Server Action secure?"
  • "Can you optimize this data fetching?"
  • "Check if this component should be server or client"

Refactoring:

  • "Parallelize these data fetches"
  • "Reduce the serialization size"
  • "Convert this to use Suspense"
  • "Optimize this barrel import"

How to Use

This skill uses a progressive disclosure structure to minimize context usage:

1. Start with the Overview (AGENTS.md)

Read AGENTS.md for a concise overview of all rules with one-line summaries.

2. Load Specific Rules as Needed

When you identify a relevant optimization, load the corresponding reference file for detailed implementation guidance:

General Patterns:

Server-Side Performance:

Misc:

Quick References:

Automation Scripts:

  • scripts/ - Helper scripts to detect anti-patterns

3. Apply the Pattern

Each reference file contains:

  • ❌ Incorrect examples showing the anti-pattern
  • ✅ Correct examples showing the optimal implementation
  • Explanations of why the pattern matters
  • Performance impact metrics
  • Related patterns and references

4. Use the Report Template

When this skill is invoked for Next.js code review, use the standardized report format:

Template: assets/output-report-template.md

The report format provides:

  • Executive Summary with impact assessment
  • Severity levels (Critical, High, Medium, Low) for prioritization
  • Impact analysis (performance, security, data transfer, maintainability)
  • Categorization (Server Actions, RSC Serialization, Data Fetching, Component Architecture)
  • Pattern references linking to detailed guidance in references/
  • Summary table for tracking all issues

When to use the report template:

  • Skill invoked directly via /accelint-nextjs-best-practices <path>
  • User asks to "review Next.js code" or "audit Next.js app" across file(s), invoking skill implicitly

When NOT to use the report template:

  • User asks to "fix this Server Action" (direct implementation)
  • User asks "what's wrong with this code?" (answer the question)
  • User requests specific fixes (apply fixes directly without formal report)

Examples

Example 1: Optimizing Server Action Security

Task: "Add authentication to this Server Action"

Approach:

  1. Read AGENTS.md overview
  2. Identify issue: Server Action needs authentication
  3. Load server-actions-security.md
  4. Apply authentication pattern with validation

Example 2: Eliminating Waterfalls

Task: "This page loads slowly with multiple fetches"

Approach:

  1. Read AGENTS.md overview
  2. Identify issue: Sequential data fetching
  3. Load prevent-waterfall-chains.md and parallelize-independent-operations.md
  4. Start operations immediately and use Promise.allSettled()

Example 3: Reducing Serialization

Task: "The HTML response is huge with user data"

Approach:

  1. Read AGENTS.md overview
  2. Identify issue: Over-serialization at RSC boundary
  3. Load minimize-serialization.md
  4. Pass only necessary fields, transform on client

Additional Resources

Official Next.js documentation:

平台分布

Codex

33.84%
按下载量换算580

Claude

29.04%
按下载量换算498

Cursor

18.97%
按下载量换算325

Gemini CLI

9.03%
按下载量换算155

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills