What problem does it solve?
Designing a data layer where a single API response feeds several domain entities often leads to duplicated fetching logic, inconsistent validation, and tangled cross-package dependencies in the Ledger Wallet monorepo. This Skill provides canonical guidance for orchestrating that pattern correctly.
Core Features & Use Cases
- Cross-Entity Orchestration: Guides structuring domain/api layers so one API response hydrates multiple entities using RTK Query, createAsyncThunk, or both.
- Response Validation: Covers validating shared API responses before distributing data across domain packages.
- Multi-Package Testing: Directs how to write tests that span multiple domain/entity packages.
- Use Case: When adding a new Ledger Live feature whose backend endpoint returns account, transaction, and token data in one payload, use this Skill to design the Redux data layer without duplicating fetch logic across entity packages.
Quick Start
Ask the assistant to apply the ddd-data-layer-advanced skill when creating or reviewing a cross-entity data layer that uses RTK Query or createAsyncThunk in the Ledger Wallet repository.