Data Fetching
Async UI for remote data — loading, error, retry, empty, stale, cache boundaries. Use when building lists, detail pages, dashboards fed by API, React Query/SWR, fetch/loaders, or "ambil data", "loading state API", "retry".
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill data-fetchinggit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/data-fetching ~/.claude/skills/data-fetchingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Fetching ## Overview Separate **server state** from UI chrome. Every remote surface needs loading / error / empty / success — with retry where useful. Parity with Conventions **States** line. ## When to use - Lists, detail, search results, dashboards from API - Introducing React Query, SWR, router loaders, `useEffect` fetch - Fixing spinner-forever or silent failure UIs ## When to skip - Static content / mock-only prototypes with no async - Pure presentational components receiving props only - Generated catch/toast that ignores field cases / other modules → load `anti-slop-code` for taxonomy, then this skill for retry chrome ## MUST (ship) | State | Required UX | |-------|-------------| | **Loading** | Skeleton/placeholder — not a blank hole (prefer local to the widget) | | **Error** | User-safe message + **Retry** (or clear next step) | | **Empty** | Real empty copy + optional action (not Lorem) | | **Success** | Render data; don’t leave stale error UI | Also: abort/cancel on unmount when using raw `fetch`; don’t block the whole app shell for one panel. ## Workflow 1. **Choose ownership** — server state in query/loader; local UI state stays in the component 2. **Required states** — loading · error (message + retry) · empty · success 3. **UX** — skeleton preferred; isolate loading to the widget when possible 4. **Errors** — user-safe message; log details; retry for transient failures
Details
- Skill name
data-fetching- Repository
- sukirman1901/frontend-expert
- Path
skills/data-fetching/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Data Fetching skill do?
Async UI for remote data — loading, error, retry, empty, stale, cache boundaries. Use when building lists, detail pages, dashboards fed by API, React Query/SWR, fetch/loaders, or "ambil data", "loading state API", "retry".
How do I install the Data Fetching 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 Data Fetching popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/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.
Anti Slop Code
9sukirman1901/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.
Anti Slop Design
9sukirman1901/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.
Design Color
9sukirman1901/frontend-expert
Use when creating or repairing a palette, semantic color roles, OKLCH scales, dark mode, contrast pairs, gamut fallbacks, “buat palet”, “warna brand”, “dark theme”, or color that must measurably pass accessibility requirements.
Components
9sukirman1901/frontend-expert
Build composable UI with a small public props contract, loading/error/empty states, Reicon icons by default, and mobile-first layout. Use when implementing or refactoring pages, screens, components, dialogs, tables, navigation, “buat component”, “prop terlalu banyak”, “API component”, or “bikin form”. Report Conventions check before done.
Design Direction
9sukirman1901/frontend-expert
Senior frontend judgment before building UI — offer 2–3 approaches on distinct design axes (hierarchy, layout, density, interaction, expression) with tradeoffs; max 1–2 clarifying questions; optional inspiration (Linear/Stripe/…). Use at the start of non-trivial UI work and whenever direction is unclear. Skip for obvious bugfixes, single-token tweaks, or “just implement”. Runs before domain skills.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.