agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/nextjs-site-architecture/SKILL.md

nextjs-site-architecture

Skill136 starsChanged 5 months agoMITView on GitHub

Coordinate the Next.js foundation and ownership.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/nextjs-site-architecture-guide.md when this skill triggers for a concrete website build, redesign, visual review, or …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Next.js Site Architecture

For substantial web work, reuse the scoped web contract when available; it replaces duplicated policy here. Match the requested scope and existing decisions; a missing optional sibling does not block this local procedure.

Overview

Set a clean, maintainable Next.js foundation. Architecture should let the design stay consistent while keeping pages easy to refine.

Workflow

  1. Identify the requested component or architecture outcome, affected files and existing decisions; reuse established content and visual direction.
  2. Inspect the project before editing when code exists.
  3. Apply this skill's specific rules from references/nextjs-site-architecture-guide.md.
  4. Explain material implementation choices while continuing authorized work.
  5. Implement when requested, inspect affected output, fix observed defects, and run the smallest decisive relevant checks.

Reference

Read references/nextjs-site-architecture-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

Ownership

Own the Next.js foundation and integration map. Let nextjs-app-router-routing own detailed route-file/navigation behavior and nextjs-server-client-boundaries own import, serialization and rendering boundaries. Apply only the relevant specialist rather than repeating their full workflows.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.