skill-sukirman1901-frontend-expert-data-fetching · by Install
$ agentstack add skill-sukirman1901-frontend-expert-data-fetching ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sukirman1901-frontend-expert-data-fetching) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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,
useEffectfetch - Fixing spinner-forever or silent failure UIs
When to skip
- Static content / mock-only prototypes with no async
- Pure presentational components receiving props only
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
- Choose ownership — server state in query/loader; local UI state stays in the component
- Required states — loading · error (message + retry) · empty · success
- UX — skeleton preferred; isolate loading to the widget when possible
- Errors — user-safe message; log details; retry for transient failures
- Cache — stale-while-revalidate when the stack supports it; invalidate on mutations
- Hand off — presentation via
ui-components; tokens +responsive-uistill apply - Conventions — report
States: loading / empty / error covered? yes
Agent boundaries
- May decide: Query lib vs loader vs
useEffectmachine; skeleton vs spinner; toast vs inline error - Must not: Swallow errors to
console.logonly; ship success-only UI; invent off-token loading colors
Checklist
- [ ] Loading / error / empty / success covered
- [ ] Retry or clear next step on error
- [ ] Empty copy is real (not Lorem)
- [ ] Fetch logic not tangled inside giant presentational files
- [ ] Race/unmount handled for raw fetch
- [ ] Responsive + tokens still apply to async UI
- [ ] Conventions States line filled when shipping
Depth
Patterns: references/data-fetching.md. State org: references/architecture.md. Ship gate: references/compliance-gates.md (States).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sukirman1901
- Source: sukirman1901/frontend-expert
- License: MIT
- Homepage: https://github.com/sukirman1901/frontend-expert
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.