Build a feature's ecs/actions layer — the operations the app performs.
adobe/data
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 42
- GitHub stars
- 11
- GitHub forks
- 8
Loading the repository README…
Skills in this repository
Showing 40 of 42 collected skills.
Build an application's src/app/ composition root.
Build a feature's ecs/computed layer. Optional.
Build a feature's ECS schema (ecs/core) and its conformance wiring. The first ecs layer.
Build a feature's data/ layer — values, components, resources, entities. The first, foundational phase.
Build a complete feature step by step
Build a game — an application whose features model game state, rules, and rendering.
Build a feature's ecs/indexes layer. Optional.
Build a feature's ecs/services layer — registering services on the database. Optional.
Build a feature's services/ layer — async data services (interface, create, createFake). Optional.
Build a feature's spec/ — the State, its actions and derivations, and their cases. Test tier.
Build a real-time feature's ecs/systems layer — the per-frame tick loop. Optional.
Build a feature's ecs/transactions layer.
Build a feature's ui/ layer.
Review built feature/application output against the @adobe/data feature rules; report whether it is optimal and where any fix belongs. Read-only.
Iteratively build an application or game phase-by-phase in clean subagents, reviewing each phase and refining the build-* skills / rules until each is optimal, then summarizing.
Build an application — a base feature hosting lazily-loaded peer features.
executes a graph of steps
Build a feature's ecs action-database — async orchestration over services and transactions. If the feature has async flows.
Wire built features into a running application — import peer schemas, lazy-load peers, and mount the root UI.
Build an application — a base feature hosting lazily-loaded peer features.
Build a feature's ecs computed-database — derived observable values.
Build a feature's ecs schema — the core-database (components, resources, archetypes). The first ecs layer.
Build a feature's data/ layer — data-type namespaces and the State spec. The first, foundational feature phase.
Build a complete feature by piping the per-layer build-* skills bottom-up.
Build a game — an application whose features model game state, rules, and rendering.
Build a feature's ecs index-database — component/archetype indexes for O(1) lookup. As needed.
Build a feature's ecs service-database — db-bound service factories. If the feature exposes services.
Build a feature's services/ layer — async capability contracts (ports to the outside world). Optional.
Build a feature's ecs system-database — the real-time tick loop (systems the scheduler runs each frame). For real-time features only.
Build a feature's ecs transaction-database — atomic mutations over the store.
Build a feature's ui/ layer — presentation bound to the ecs database. The final, top layer.
Iteratively build an application or game phase-by-phase in clean subagents, reviewing each phase and refining the build-* skills / rules until each is optimal, then summarizing.
Review built feature/application output against the @adobe/data feature rules; report whether it is optimal and where any fix belongs. Read-only.
Use when laying out or reasoning about a feature's file/folder structure and layer dependencies.
executes an input optionally with validate first
Source text: Undetermined
logs all named inputs to chat
executes the input within a subagent
inserts a /x-log call right after every non log piped function
validates nested or piped function calls to determine if output types match all required input types
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/adobe/data.