# Examples repository > **Not Yet Implemented.** Intended development areas are plans, not available features. [Examples on GitHub](https://github.com/Rustic-Game-Engine/examples). ## Current contents and development language As checked in the available checkout on 12 October 2026, this repository contains only `LICENSE` (Apache 2.0). **Implementation has not begun.** There are no published example games, scripts, build manifests or runnable samples. This is intentional; no implementation language is established. Its planned purpose is to host small example games, sample projects and code demonstrations of Rustic features and workflows. Until those exist, use the [first playable scene](https://rustic-game-engine.pages.dev/markdown/tutorials/first-playable-scene.md), [engine guides](https://rustic-game-engine.pages.dev/markdown/engine.md) and [API reference](https://rustic-game-engine.pages.dev/markdown/api/overview.md). ## Prerequisites Git is sufficient to inspect the current repository. Creating a sample also requires a working Rustic installation and the toolchain for its chosen scripting language. ## Start your own example project Fork the repository and coordinate a small sample with maintainers. Create the project in Rustic, use public APIs, preserve project metadata and licensed assets, and reopen it from a fresh checkout. Include a README naming the engine revision, language, setup, attachment, controls and expected result. This is contribution guidance, not an existing repository layout or runnable project. ## Main scripts and useful starting points There are no current entry scripts, package commands or automated checks. A future sample should identify its scene and callbacks and link to the matching language guide. Add focused sample pages when actual projects are published. ## License and common pitfalls Preserve Apache 2.0 and attribution notices, and verify separate asset licenses. A checkout containing only `LICENSE` is the expected state. Existing topic URLs remain aliases to this overview.