agentsclimarketplace

Ecs design

Skill christopher-buss/skills/skills/ecs-design

Curated skills and configurations for AI-assisted developmentFrom the repository description

Install
npx -y skills add christopher-buss/skills --skill ecs-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.7 KB, as published. Nobody here has run it

ECS Design Principles

Design guidance for jecs in Roblox.

Core Mental Model

Think of ECS as a columnar database:

DatabaseECS
TableArchetype (unique component combination)
ColumnComponent type
RowEntity
QuerySystem iteration

Design question: "Would I create a separate database column for this?"

Core References

TopicDescriptionReference
Database ModelECS as columnar database, normalization, fragmentationcore-database-model
Query DesignMulti-entity queries, constraint decomposition, traversalcore-query-design

Best Practices

TopicDescriptionReference
Component DesignGranularity decisions, when to split/combine, tags vs databest-practices-components
System DesignSingle responsibility, avoiding work, ordering, data flowbest-practices-systems
Entity DesignWhen to create entities, lazy creation, scaling patternsbest-practices-entities

Quick Decision Guide

QuestionAnswer
Should this be an entity?Only if it needs per-instance state that changes over time
Split or combine?"Is there a system that needs A but not B?"
Tag or data component?Tags for stable classification (free to add/remove), data for state
Relationship or entity ref?Relationship if reverse lookup needed, entity member otherwise
Is fragmentation bad?Only if thousands of archetypes AND you query broadly
When does DOD matter?Thousands of entities, per-frame, CPU-bound

Common Mistakes

MistakeWhy it's badFix
Monolithic componentsCache waste, tight couplingSplit by access pattern
Over-atomic componentsQuery complexity, invalid statesCombine semantic units
Frequent add/remove on large entitiesCopies all component dataMutate data component instead
Relationships for every linkFragmentation without benefitUse entity members for forward-only
Cached query inside systemCreates new cache every frameCreate cached queries at module scope

Key Principles

  1. Components by access pattern — Group data that systems need together
  2. Archetype transitions copy data — Adding/removing components copies all data to new archetype; cheap on small entities, expensive on large ones
  3. Entity members vs relationships — Use entity members for forward lookup, relationships for reverse lookup or grouping
  4. Cache queries at module scope — Never call .cached() inside a system
  5. Filter in query — Use with/without, not code conditionals
  6. Fragmentation can help — Relationships enable efficient grouped queries
<!-- Source references: - https://github.com/SanderMertens/flecs/blob/master/docs/DesignWithFlecs.md - https://github.com/SanderMertens/ecs-faq -->

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.