agentleFS
Sign inStart free
sukirman1901sukirman1901/frontend-expert/skills/architecture/SKILL.md

architecture

Skill9 starsChanged 2 months agoMITView on GitHub

Frontend structure — feature folders, state ownership, server/client boundary, when not to add a global store. Use for "arsitektur FE", folder structure, refactor large UI, state management choice, or modularizing an app.

136 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, bash-linux and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 6 projects that use this

  • xenitV1Skill

    bash-linux

    Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

    Also in 8 projects that use this

  • xenitV1Skill

    red-team-tactics

    Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

    Also in 8 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • +8 more from xenitV1

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 118 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep UI modular and owned.

    line 13
  2. Distinctive:

    Must not: Add Redux/Zustand “by default”.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 118 edited versions of this file we could read. “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

FE Architecture

Overview

Keep UI modular and owned. Prefer local state and server cache over inventing a global store.

When to use

  • Greenfield folder layout
  • Refactors of tangled components
  • Debates: Redux vs context vs query vs URL

When to skip

  • Single-file prototype the user wants kept flat
  • Pure visual polish with no structure ask
  • Generated-hook soup without a folder/state ask → anti-slop-code

MUST (agent decisions)

DecisionDefault
FoldersFeature cohesion (features/x/) over dumping everything in components/
Remote dataQuery/loader (data-fetching) — not a global store of server entities
URL stateShareable filters/tabs in the URL
Global storeLast resort — only after local → lift → URL → server cache → context
File sizeSplit presentational files >~200 lines; colocated tests when testing

Workflow

  1. Boundaries — feature folders over type-only dumps
  2. State ladder — local → lifted → URL → server cache → context (theme/auth) → global store last
  3. Server/client — fetch on server when the stack allows; mark client islands explicitly
  4. Deps — UI primitives don’t import feature screens; features may use shared UI
  5. Size — split files >200 lines; colocated tests

Agent boundaries

  • May decide: Feature vs route folder names; query lib; whether auth lives in context/session
  • Must not: Add Redux/Zustand “by default”; put every form field in a global store; create circular feature imports

Checklist

  • Feature ownership clear
  • No unnecessary global store
  • Server state not duplicated in client stores without reason
  • Shared UI stays presentational
  • State ladder documented in handoff when non-trivial

Depth

references/fe-architecture.md + references/architecture.md.

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.

Check your setup, free