Architecture

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.

9 stars 1 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sukirman1901/frontend-expert

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sukirman1901/frontend-expert --skill architecture
Manual install
git clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/architecture ~/.claude/skills/architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the 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)

| Decision | Default |
|----------|---------|
| **Folders** | Feature cohesion (`features/x/`) over dumping everything in `components/` |
| **Remote data** | Query/loader (`data-fetching`) — not a global store of server entities |
| **URL state** | Shareable filters/tabs in the URL |
| **Global store** | **Last resort** — only after local → lift → URL → server cache → context |
| **File size** | Split 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
Read the full skill on GitHub

Details

Skill name
architecture
Path
skills/architecture/SKILL.md
License
MIT
Repo updated
5 November 2026

FAQ

What does the Architecture skill do?

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.

How do I install the Architecture skill?

Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Architecture popular?

It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.

Related skills

Accessibility

9

sukirman1901/frontend-expert

Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.

Frontend & Design

Anti Slop Code

9

sukirman1901/frontend-expert

Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.

Software Development

Anti Slop Design

9

sukirman1901/frontend-expert

Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.

Frontend & Design

Network Debug

5

franco-bianco/claude-skills

Inspect HTTP traffic captured by PowHTTP MCP proxy. Use when fixing request mismatches in existing code or building new API flows from browser traffic.

Software Development

Cloudflare Architecture

9

zllovesuki/cloudflare-agent-skills

Choose Cloudflare Developer Platform primitives and architecture shapes before writing code. Use for Cloudflare Workers, Durable Objects, D1, R2, Queues, Workflows, Containers, Realtime, Workers AI, Vectorize, AI Search, Agents, cost, limits, and migration decisions.

Software Development

Prior Art Scout

5

tlzmw001/naiyue-skills

项目开工前的技术方案调研引擎——给定项目想法,优先核验用户明确提供的项目、URL、工具或技术方向,再搜索最相关的整体方案并把任务拆成流程环节;从 GitHub、Web、X 等来源广泛保留轻量候选,覆盖开源、托管 API、SDK+闭源后端、MCP 等供应形态,对方向命中、完整方案和流程补位候选先核验是否真实可用、文档是否详细、接入是否不过度复杂,每个来源最多选择 5 个做代码或一手材料深验,最终聚焦回答别人解决什么问题、使用什么工具/流程/技术、能否直接使用或借鉴,并给出证据可追溯的评估与建议。当用户说“我想做一个 XX,先调研一下”“优先看看这个项目/方向”“看看有没有人做过类似的”“找现有方案/竞品/prior art”“开工前查一查”时使用。

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.