Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/nextjs-fullstack

@9125e02
Run it yourself

Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.

  • 1 file
  • 1.7 KB
  • Updated 6 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/nextjs-fullstack

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈371 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈180 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Next.js Fullstack

Ship Next.js features with correct boundaries between server, client, data, and UI.

Grok Build Mode

  • Use Plan Mode for routing, auth, persistence, caching, or data-fetching changes.
  • Use subagents for broad changes:
    • routes: app router structure, layouts, metadata.
    • data: DB queries, server actions, validation.
    • client: components, state, forms, accessibility.
    • tests: unit/e2e/build verification.
  • Arena-style comparison: compare server action vs API route vs client-only approaches and choose by security, simplicity, and cache behavior.

Workflow

  1. Detect Next version, package manager, styling, auth, DB, and test setup.
  2. Keep server-only code out of client components.
  3. Validate inputs on the server.
  4. Respect existing caching/revalidation patterns.
  5. Add loading/error/empty states.
  6. Run the narrowest relevant checks:
    • npm run lint
    • npm run typecheck
    • npm run build
    • project tests.

Rules

  • Do not leak secrets into NEXT_PUBLIC_*.
  • Avoid unnecessary client components.
  • Do not mutate data without auth and ownership checks.
  • Keep forms progressive and resilient.
  • Use existing UI primitives and route conventions.

Example Prompts

Use nextjs-fullstack. Plan a server-action implementation for this feature, including validation, auth, tests, and loading/error UI.
Review this Next.js diff for server/client boundary bugs and cache invalidation issues.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/nextjs-fullstack