engine-overview

Explain FlatRedBall2 engine responsibilities and required game code structure.

11|3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/vchelaru/FlatRedBall2 --skill engine-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engine-overview
Source: https://github.com/vchelaru/FlatRedBall2/tree/main/frb-skills/engine-overview
Command: npx skills add https://github.com/vchelaru/FlatRedBall2 --skill engine-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly understand the responsibilities of FlatRedBall2, distinguishing automated engine behavior from custom game code, so new projects can bootstrap correctly and avoid misconfigurations.

Core Features & Use Cases

  • Engine auto-handles physics integration, collision resolution, rendering order, input polling, Gum UI updates, screen transitions, and camera transforms.
  • Provides a clear blueprint for onboarding, architecture planning, debugging startup flow, and team knowledge transfer.
  • Guides how to structure code using Entities, Screens, Factories, and the bootstrapping sequence to get a playable result quickly.

Quick Start

Boot a new FlatRedBall2 project and observe how the engine bootstraps, initializes screens, and drives the frame loop.

Frequently Asked Questions about engine-overview

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

FAQPage Schema
What does FlatRedBall2 handle automatically for game development?

FlatRedBall2 automatically handles physics integration, collision resolution, rendering order, input polling, Gum UI updates, screen transitions, and camera transforms so developers can focus on custom game logic.

How do I structure code in FlatRedBall2 using Screens and Entities?

Structure FlatRedBall2 code by organizing game objects into Entities, managing game flow through Screens, and instantiating objects via Factories to ensure proper bootstrapping and frame loop integration.

Does FlatRedBall2 require MonoGame to bootstrap a new game project?

FlatRedBall2 operates on the MonoGame framework, requiring developers to bootstrap their project correctly to initialize screens, wire entities, and drive the frame loop for a playable result.

What is the best way to understand FlatRedBall2 engine behavior for debugging?

Understand FlatRedBall2 engine behavior by reviewing its core subsystems like physics, collision, and rendering to distinguish automated processes from custom game code during debugging and startup flow analysis.

Can I use FlatRedBall2 for planning screen transitions and Gum UI integration?

FlatRedBall2 supports planning screen-entity wiring and automatically processes Gum UI updates and screen transitions, providing a clear architectural blueprint for onboarding and team knowledge transfer.

Why does my FlatRedBall2 game code conflict with engine automation during the frame loop?

FlatRedBall2 game code conflicts often arise from misconfiguring custom logic that overlaps with automated engine tasks like input polling or collision resolution, requiring a clear separation of responsibilities.