api-data-fetching

To structure React Query data fetching, separate your code into client.ts, types.ts, and queries.ts modules. This canonical pattern ensures proper query key conventions and structured cache invalidation for frontend projects.

The canonical pattern for organizing React Query mutations and types involves defining strict module boundaries. You structure client modules, types, and queries separately to maintain clean data fetching workflows and proper mutation patterns.

Yes, this API data-fetching guidance works for legacy React prompts by providing a compatibility alias. It directs legacy prompts to the canonical react-query-data-patterns skill without losing guidance on structuring client modules and queries.

To migrate legacy API data-fetching prompts to current React Query patterns, use this skill as a stable alias. It automatically routes your existing prompts to the canonical react-query-data-patterns guidance for current module structuring.

You need to alias API data-fetch guidance to canonical React Query patterns when maintaining compatibility for older prompts. This ensures teams migrating legacy configurations continue receiving current module boundary and query structuring guidance.

The limitation of using an alias skill for React Query data patterns is that it contains no native guidance itself. It requires alignment with documented module boundaries and depends entirely on the primary canonical skill for current instructions.