Add ECS components to Rogueverse with serialization and inspector registration.
npx skills add https://github.com/clagraff/Rogueverse --skill new-component-clagraff
Please help me install this Agent Skill. Skill: new-component Source: https://github.com/clagraff/Rogueverse/tree/main/.claude/skills/new-component Command: npx skills add https://github.com/clagraff/Rogueverse --skill new-component-clagraff
This Skill standardizes the process of adding a new ECS component to the Rogueverse codebase, ensuring consistent patterns, serialization, and inspector/UI integration.
Create the component in lib/ecs/components.dart, run dart run build_runner build --delete-conflicting-outputs, add inspector metadata, export in sections.dart, and register the metadata in properties_panel.dart.
High-intent search queries and answers about installing and using this skill.
Adding a new ECS component requires defining the class in components.dart, running build_runner to generate mappers, and wiring inspector metadata for UI registration. This ensures consistent serialization and inspector integration.
You can create marker, data, or intent ECS components. Each type follows standardized patterns for serialization, inspector metadata generation, and properties panel registration within the Rogueverse architecture.
Yes, you must register the component metadata in properties_panel.dart and export it in sections.dart. These manual steps ensure the new ECS component appears correctly in the inspector UI.
Running build_runner generates or updates the mapper required for the new ECS component. This step ensures serialization logic is correctly generated before wiring inspector metadata and UI registration.
You should consider adding a System or Interaction Definition when the new ECS component requires active processing or user interaction. The workflow evaluates whether these additional definitions are necessary for component functionality.
The standard workflow involves creating the class in components.dart, running build_runner, adding inspector metadata, exporting in sections.dart, and registering in properties_panel.dart. This repeatable process reduces boilerplate and friction.
flutterGenerate type-safe mock objects for Dart dependencies using mockito and build_runner.
wildbitcaEnforce Dart formatting, linting, and metrics via analysis_options.yaml and dart format.
TheLazyLemurCreate and register data-only ECS components for the Donburi game engine.
lapc506Automate Flutter boilerplate generation with build_runner, freezed, json_serializable, injectable, and auto_route.
