#Raylib Examples in MoonBit

#Goals

• Keep examples easy to run and read.
• Keep gameplay logic, rendering, and shared types separated.
• Keep documentation quality high enough for package-level onboarding and API browsing.

#Quick Start

moon check
moon build --target native 2048/
moon run --target native 2048/

#Repository Layout

• moon.mod.json: module metadata and dependencies.
• <game_name>/: example/game packages.
• raygui_demo: raygui-focused demo package.
• tools/: build/publish helper scripts.

• main.mbt: executable entry and frame loop.
• internal/types: exported constants, types, helpers.
• internal/game: state transitions and simulation.
• internal/render: draw pipeline.

#Documentation Standards

• Public declarations must have /// documentation when +missing_doc is enabled.
• Each game should have a README.mbt.md describing:
  • gameplay and controls,
  • build/run instructions,
  • public API summary,
  • architecture notes,
  • refinement roadmap.
• API surface should stay aligned with pkg.generated.mbti output from moon info.

#Validation Workflow

moon check
moon info
moon test

moon check --package-path 2048

#Notes