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
- Mozurok/fhorja.devtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mozurok/fhorja.dev★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- backend-architectureSkill
- build-review-loopSkill
- capability-intakeSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- dev-patternsSkill
- idea-validatorSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
- update-mdSkill
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
- Very specific: line 26
Read the relevant section of ~/.claude/skills/external/awesome-front-end-system-design/README.md (sections: General · Applications · …
- Very specific: line 38
If pairing with superpowers brainstorming/writing-plans, this supplies the FE-architecture content for the spec.
≈ “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.
Files
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
- 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. - 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
- Feed that checklist into the design BEFORE coding. Surface the 3-5 decisions the user must make.
- 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.
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
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.

