Frontend Data Mock State

Use this skill when the task involves API integration, server-state design, module adapters, mock-driven delivery, or deciding where state should live.

Use This Skill When

• The frontend needs an API client strategy or query/mutation structure.
• The task involves TanStack Query, adapters, normalization, or transport-to-domain mapping.
• The feature should run independently with mocks before real backend integration.
• The team needs clearer boundaries between local state, URL state, server state, and global state.

Inputs To Confirm Up Front

• API maturity: stable, evolving, mock-first, or backend not ready.
• Required query and mutation flows.
• Which state should be local, URL-based, server-driven, or global.
• Whether optimistic updates or rollback behavior are needed.
• Whether locale affects API payloads, content variants, formatting rules, or translation-resource loading.