
Opinionated architecture guide for building domain-driven feature modules in React apps organized around a systems/ directory. Walks you through the full stack: API adapters, TanStack Query setup with hierarchical cache keys, mutation patterns with optimistic updates, React contexts, XState stores for complex flows, and proper barrel exports. Written by Pedro Nauck with clear examples and a mandatory companion skills table that tells you to pull in tanstack-query-best-practices for data work and xstate for state machines. Strong on structure and conventions, light on explaining why you'd pick this pattern over alternatives. Best for teams that already bought into domain-driven frontend architecture and want consistent implementation.
$ npx -y skills add pedronauck/skills --skill app-renderer-systems --agent claude-codeInstalls into .claude/skills of the current project.
A systems/<domain>/ module owns its domain's UI-facing adapters, data access, hooks, components, and public barrel. Extend the existing system; create only layers the feature actually needs. A local component edit does not scaffold CRUD adapters, a store, context providers, or tests for every layer.
Read references/directory-layout.md for placement or a new system, and references/patterns.md for the changed API/query/hook pattern. Related skills are conditional: React for component/hook behavior, TanStack for Query/Router/Form, XState Store for that store API, and the existing test runner's guidance when editing tests. Use debugging guidance for an unresolved failure, not every system edit.
Sponsors