frontend-data-contracts
A portable, framework-agnostic discipline for type safety at the network edge of any React or React Native app. Establishes one typed API client as the single fetch boundary, a parse-don't-validate rule that turns wire JSON into trusted domain types before it enters the app, a single...
Profile →npx skills add sickn33/agentic-awesome-skills --skill frontend-data-contracts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Frontend Data Contracts (typed network boundary) ## When to Use Use this skill when you need a portable, framework-agnostic discipline for type safety at the network edge of any React or React Native app. Establishes one typed API client as the single fetch boundary, a parse-don't-validate rule that turns wire JSON into trusted domain types before it enters the app, a single... > Portable skill — readable by Claude Code, OpenCode, Codex, Cursor, Windsurf, and others. > This skill describes a **discipline at the network edge** — one client, one envelope, one error > type, validated types — not a state library or a styling system. It pairs with the > **frontend-architecture** skill (the client lives in `shared/api-client/`) and is the foundation > the **frontend-optimistic-mutations** skill builds on. The goal: the moment data crosses from the network into the app, it stops being `any`-shaped wire JSON and becomes a **trusted, typed domain value** — or it becomes a **single, typed error**. There is exactly one place this transformation happens, and nothing untyped escapes it. --- ## 0. The five core ideas 1. **One client is the only fetch boundary.** A single typed `apiClient` wrap
- When to Use
- 0. The five core ideas
- 1. Directory layout
- 2. One client, the only fetch boundary
- 3. Parse, don't validate (the boundary transform)
- 4. One response envelope
- 5. Branded (nominal) identifiers
- 6. One normalized error type
- 6.1 Where side effects live
- 6.2 Per-field errors → form fields
- 7. Library adapters
- 8. Conventions checklist (enforce in review)
- 9. How to apply this skill
- Publishing / installing this skill
What does the frontend-data-contracts skill do?
A portable, framework-agnostic discipline for type safety at the network edge of any React or React Native app. Establishes one typed API client as the single fetch boundary, a parse-don't-validate rule that turns wire JSON into trusted domain types before it enters the app, a single...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill frontend-data-contracts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.