agentleFS
EduMMorenolpEduMMorenolp/Config-Skill-Agent/skills/frontend-next/next-arquitectura-frontend/SKILL.md

next-arquitectura-frontend

Skill0 starsChanged 31 days agoNo licenceView on GitHub

App Router structure for Next.js: app/ tree, server components by default, minimal use client, route groups and layer rules. Use when creating a new Next project, deciding where a page/layout/component goes, or when imports cross segments or too many files are client components. Triggers: "estructura del frontend", "por feature", "arquitectura frontend", "organizar componentes", "prop drilling", "diseno de componentes", "donde guarda el estado", "app router", "estructura de app", "route groups", "server components".

The file

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.