agentleFS
UnfoldCRO-OrganizationUnfoldCRO-Organization/cro-agent-skills/skills/frontend-system-design/SKILL.md

frontend-system-design

Skill0 starsChanged 22 days agoMITView on GitHub

Front-end architecture + UI-component design reference. Auto-invoke (no slash) BEFORE designing or building any non-trivial React/Next.js component, widget, or full client-side app feature — e.g. cart/checkout, autocomplete, carousel, modal, infinite-feed, data-table, design-system component, offline-sync, server-driven UI, i18n, real-time/collab UI. Trigger on intent like "build a cart", "design the checkout UI", "autocomplete component", "infinite scroll feed", "build a carousel", "data table with sort/filter", "real-time/collab feature", "offline sync", "design system component", or any prompt that means architecting front-end state/data-flow/rendering for a complex UI. Pulls battle-tested patterns (state shape, data flow, API design, rendering strategy, accessibility, perf, edge cases) from the curated greatfrontend/awesome-front-end-system-design corpus on disk. SKIP for WordPress theme/Liquid/plain-HTML work and for trivial one-element edits. Reference-only — informs the design, does not write app code by itself.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Read the relevant section of ~/.claude/skills/external/awesome-front-end-system-design/README.md (sections: General · Applications · …

    line 26
  2. Very specific:

    If pairing with superpowers brainstorming/writing-plans, this supplies the FE-architecture content for the spec.

    line 38

≈ “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

frontend-system-design — auto-loaded FE architecture reference

Curated corpus: greatfrontend/awesome-front-end-system-design, cloned at ~/.claude/skills/external/awesome-front-end-system-design/ (pin f56c0f3, MIT). Single source file: README.md (~40KB) + assets/.

When this fires (automatic, no slash command)

Invoke yourself BEFORE writing code for any non-trivial React/Next.js front-end:

  • Full-app features: cart, checkout, news/infinite feed, chat, product grid, dashboard, collaborative editor, video/media UI
  • UI components: autocomplete/typeahead, carousel, modal/dialog, dropdown/menu, tooltip, data-table (sort/filter/paginate), image gallery, design-system primitives
  • Techniques: offline-sync, server-driven UI, i18n, optimistic updates, real-time, AI-integration UI

SKIP for: WordPress themes/plugins, Liquid sections, plain HTML/CSS pages, SEO work, or a one-line/one-element tweak. Those gain nothing here.

What to do when it fires

  1. Read the relevant section of ~/.claude/skills/external/awesome-front-end-system-design/README.md (sections: General · Applications · Techniques/Topics · User Interface Components · Miscellaneous). Grep for the matching pattern, e.g. grep -i -A3 "autocomplete\|e-commerce\|data table" README.md.
  2. Extract the design checklist that corpus implies for this component/app:
    • State shape — what state, where it lives, normalize vs nested
    • Data flow — fetch strategy (SSR/CSR/streaming), caching, optimistic vs pessimistic
    • API surface — endpoints/shape the UI needs; pagination/cursor; error contract
    • Rendering — virtualization for long lists, lazy/suspense boundaries, skeleton states
    • Accessibility — keyboard nav, ARIA roles, focus management (esp. modal/menu/autocomplete)
    • Performance — debounce/throttle, memoization, bundle split, image strategy
    • Edge cases — empty/loading/error/offline, race conditions, stale data, concurrency
  3. Feed that checklist into the design BEFORE coding. Surface the 3-5 decisions the user must make.
  4. If pairing with superpowers brainstorming/writing-plans, this supplies the FE-architecture content for the spec; superpowers owns the loop. Don't duplicate the spec ceremony.

Boundaries

  • Reference-only. Does NOT write app code by itself — informs the plan, then normal build proceeds.
  • Honor locked the agency rules in any code that follows: Lucide-only icons, IST date format, commits without AI attribution.
  • Corpus is a link-list to external eng blogs; for deep dives the README points at source URLs — fetch those only when the on-disk summary is insufficient.

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.