bevy-bsn

Define inline Bevy scenes with the bsn! macro.

125|10|Updated Nov 22, 2022
One-click install
npx skills add https://github.com/nolantait/bevy-starter --skill bevy-bsn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bevy-bsn
Source: https://github.com/nolantait/bevy-starter/tree/main/.agents/skills/bevy-bsn
Command: npx skills add https://github.com/nolantait/bevy-starter --skill bevy-bsn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BSN provides a concise macro-based approach to define inline Bevy scenes with components, relationships, observers, and dynamic props, reducing boilerplate and improving readability.

Core Features & Use Cases

  • Inline scene definitions using the bsn! macro to compose complex scenes from reusable pieces.
  • Scene merging, dynamic props, and reusable scene snippets via Car/Component patterns demonstrated in examples.
  • Observers, named entity references, and hierarchical composition to build rich Bevy scenes.

Quick Start

Spawn a sample scene using BSN by calling the bsn! macro with a Car and its children.

Frequently Asked Questions about bevy-bsn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define inline Bevy scenes without writing extensive boilerplate?

You can define inline Bevy scenes using the bsn! macro, which provides a concise syntax to compose scenes with components, children, and observers while reducing boilerplate.

Can I compose hierarchical Bevy scenes with named entity references and observers?

Yes, BSN supports hierarchical composition by allowing you to build rich Bevy scenes using named entity references, observers, and dynamic props within the inline macro syntax.

What's the best way to merge reusable scene snippets in a Bevy game?

The best way to merge reusable scene snippets is by using BSN's Car/Component patterns, which enable scene merging and dynamic prop expressions for modular scene composition.

Does BSN support dynamic configuration for Bevy scenes at runtime?

BSN supports dynamic configuration across both startup and runtime scenarios by allowing dynamic prop expressions within the inline scene definitions generated by the macro.

When do I need a macro-based scene notation for Bevy game development?

You need macro-based scene notation when your Bevy application requires modular scene composition and reuse, and you want to improve readability over traditional manual entity spawning.