How aduimperfect/stroblitzengine works
Project type and purpose
• From the file tree and README (“StroblitzEngine”) it appears to be a game-engine or real‐time 3D/2D engine library rather than a web app or microservice.
• As a library/engine, its primary goal will be to expose rendering, physics, audio, input, resource management, and scripting subsystems for host applications (games or simulations).
File structure
• src/ (core engine code)
• / (public headers)
• modules/ or plugins/ (graphics backends, physics backends, audio backends)
• tests/ or examples/
• docs/ or tools/ (editor, scripting REPL)
• Configuration and build files (e.g., CMakeLists.txt, package.json) will define how modules are built and linked.
Detailed capturing of architectural elements
• Drill down if needed: within Rendering show “Command Queue”, “Shader Manager”, “Frame Buffer”, etc.
• If ECS is central, show “Entity Manager”, “Component Stores”, “System Processors”.