# Low-poly elevated track racing

> An orange-and-white racing car navigates raised gray tracks amid faceted green hills. Views show bends, steep ramps, overhead structures, checkpoint guidance, and a navy HUD displaying elapsed time, speed, and checkpoint counts.

- Kind: Game
- Live game: https://kodub.itch.io/polytrack
- Page: https://meetreference.com/v/ref-polytrack-low-poly-racing/
- Ready-to-use agent handoff: https://meetreference.com/v/ref-polytrack-low-poly-racing/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Style: Games; low-poly, arcade racing, faceted geometry, sports typography, high-contrast wayfinding, minimal environment
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by Kodub in Website: https://kodub.itch.io/polytrack
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this game

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Use a brightly colored, faceted vehicle against restrained road and landscape colors so the playable subject remains immediately legible. Frame track edges as strong perspective guides, and mark objectives with a contrasting color repeated in both world-space signs and the HUD. Pair slanted interface panels with large timing numerals while keeping secondary metrics at the corners. For a new setting, replace the vehicle silhouette, terrain, and obstacle shapes while preserving the separation between navigation cues, scenery, and performance data.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the captured walkthrough frames, not by the creator.

Stylized low-poly racing game with a small orange-and-white car on geometric tracks; checkpoint prompts and a racing HUD appear in several frames.

- Color: Bright blue sky, green terrain, dark charcoal roads and structures, orange-and-white car, and navy-blue interface panels.
- Type: Bold, slanted block lettering labels the navy controls, timer and speed readout.
- Framing: Third-person view from behind the car, generally centered near the bottom of each frame, with the track and horizon filling the rest of the image. A few frames show large overhead track structures.
- Structure: Rear views of the race car progress through elevated bends, ramps and overhead structures. Checkpoint guidance appears above the track, while timing, speed and checkpoint counts remain along the bottom.

Storyboard, nine frames spread across the captured walkthrough: https://meetreference.com/media/ref-polytrack-low-poly-racing/storyboard.webp

- Frame 1 at 1.0s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f1.webp
- Frame 2 at 2.9s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f2.webp
- Frame 3 at 4.9s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f3.webp
- Frame 4 at 6.8s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f4.webp
- Frame 5 at 8.7s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f5.webp
- Frame 6 at 10.7s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f6.webp
- Frame 7 at 12.6s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f7.webp
- Frame 8 at 14.6s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f8.webp
- Frame 9 at 16.5s: https://meetreference.com/media/ref-polytrack-low-poly-racing/f9.webp

## Links

- Play game: https://kodub.itch.io/polytrack
- Original post: https://kodub.itch.io/polytrack