Nextjs

Next.js App Router best practices — Server Components, data fetching, caching, routing, middleware, metadata, error handling, streaming, Server Actions, and performance optimization for Next.js 14-16+.

This skill is a documentation-style, instruction-only guide for Next.js App Router and is internally consistent with that purpose. It does include deployment and integration examples that show env variable names and connectors (Redis, S3/AWS, analytics/CDNs). That is normal for a guide — but before you copy-run any example code, make sure you: (1) do not paste secrets into public repos or consoles, (2) provide real credentials only in secure runtime environments, and (3) review any third‑party service URLs or SDK usage to avoid unintended data exposure. If you want extra caution, inspect the exact snippets you plan to use and test them in an isolated environment first.

Type: OpenClaw Skill Name: nextjs-guidelines Version: 1.0.0 The skill bundle provides comprehensive documentation and code examples for Next.js App Router best practices. All `bash` commands, `tsx` code snippets, and configuration files (e.g., Dockerfile, next.config.js) are directly related to Next.js development, building, migration, deployment, and testing. There is no evidence of intentional harmful behavior, such as data exfiltration, unauthorized remote control, persistence mechanisms, or obfuscation. Prompt injection surfaces in `SKILL.md` and `README.md` are free of instructions designed to mislead the AI agent into performing malicious actions or accessing unrelated sensitive data. Network calls (e.g., `curl` commands) are for testing local endpoints, and file system access is for legitimate Next.js server-side features like custom font loading or cache handlers.