eng-data-boundaries
FeaturedData-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs. Use when adding, changing, or debugging those paths. Don't use for presentational-only UI or backend work with no public read-model impact.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- compozy
- Repository
- compozy/compozy
- Created
- 7 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
backend-contract-boundary
Use when a REQ adds or changes backend services, APIs, events, workers or persistence, to keep contracts explicit and stable at the boundary — validated input, typed errors, transport and providers out of the domain — so that later REQs extend them instead of breaking them. The error and status scenarios are in journey-api-contract, journey-data-lifecycle and journey-integration.
file-boundaries
Pattern for respecting file ownership boundaries during implementation. Prevents conflicts in parallel work.
enforcing-consistency-boundaries
Use when deciding what one transaction must cover, when two entities have to stay in step, or when identity and equality of domain values are unclear.