Data Fetching

This is LobeHub's opinionated data fetching architecture that enforces a three-layer pattern: Service layer wraps all lambdaClient calls, Zustand stores expose SWR hooks instead of useEffect, and components call useFetchXxx hooks that handle loading states and cache invalidation. The skill covers the complete flow from service class setup through store actions with optimistic updates, including naming conventions like useFetchBenchmarks for reads and refreshBenchmarks for cache busting. It's strict about what not to do, no direct lambdaClient calls in components, no useEffect for data loading, no useState for server data. Works well if you want enforced separation of concerns and are already using this exact stack.