Skip to main content
Cursor Boston

Add art to the Cursor Boston game

The game catalog has slots for hundreds of images — units, spells, buildings, upgrades, castes, and artifacts. Most ship today without art and fall back to a placeholder logo. Your PR replaces the placeholder for every player on the next page load.No code changes needed; the catalogs already wire each entry's image by convention. Drop a PNG in the right folder with the matching filename and you're done.

What we need

Each catalog entry has an id. The UI looks for /game/<category>/<id>.png in the public/tree. Match the id exactly and the image is automatically picked up — there's nothing to register or import.

  • Castes

    /public/game/castes/

    Filename: <caste>.png

    Examples: white.png, blue.png, green.png, red.png, black.png

    Browse the castes catalog on GitHub →

  • Units

    /public/game/units/

    Filename: <id>.png (where id is `<caste>-<type>-<name>`)

    Examples: white-ground-pikeman.png, blue-air-sky-reader.png, green-ground-warden.png, red-air-phoenix-talon.png, black-siege-bone-hurler.png

    Browse the units catalog on GitHub →

  • Spells

    /public/game/spells/

    Filename: <id>.png (where id is `<caste>-<school>-<name>`)

    Examples: white-offense-smite.png, blue-defense-arcane-veil.png, black-attrition-bone-fever.png, red-production-forge-blessing.png, green-disarm-binding-roots.png

    Browse the spells catalog on GitHub →

  • Buildings

    /public/game/buildings/

    Filename: <id>.png (typically `<caste>-<kind>` or shared `<kind>`)

    Examples: white-military.png, blue-magic.png, green-food.png

    Browse the buildings catalog on GitHub →

  • Upgrades

    /public/game/upgrades/

    Filename: <id>.png (matches the upgrade target id + tier)

    Examples: white-ground-pikeman-upgrade-1.png

    Browse the upgrades catalog on GitHub →

  • Artifacts

    /public/game/artifacts/

    Filename: <id>.png (matches the artifact id from the catalog)

    Examples: rare-stormglass-ward.png

    Browse the artifacts catalog on GitHub →

Style notes

  • Format: PNG with transparent background. The UI composites your image over various card backgrounds.
  • Square aspect ratio. Most game UI surfaces render images in a square slot. Suggested working size is 512×512 or 1024×1024; the UI will downscale.
  • Caste palette.Match the existing caste color language where it makes sense — white reads as paladin / cathedral, blue as arcane, green as druidic / wild, red as forge / fire, black as shadow / undead. Stylistic riffs are welcome; you don't have to mimic any one reference.
  • Readable at small sizes. Cards render at ~80–120 px in many places; avoid tiny details that disappear.
  • License.The repo is GPL-3.0. By submitting a PR you certify the work is yours (or compatibly licensed) and you're fine with it shipping under the project license. See LICENSE at the repo root.

How to submit a PR

  1. Fork rogerSuperBuilderAlpha/cursor-boston and clone your fork locally.
  2. Create a branch with a designer-friendly name, e.g. art/your-handle-white-ground-set.
  3. Drop your PNGs into the matching public/game/<category>/ folder. The folder may not exist yet — go ahead and create it if needed. Each filename must exactly match the catalog id with a .png extension. (See the GitHub links above for the catalog ids.)
  4. Commit with a sign-off (the project requires DCO): git commit -s -m "feat(game/art): add white ground unit set".
  5. Push and open a PR against develop. Drop a couple of preview thumbnails in the PR description so reviewers can eyeball the set without checking out the branch.

Submit in batches when you can

A full caste set (e.g. all 9 white units + a few spells) is easier to review than a single one-off. Open a draft PR early if you want feedback on naming or palette before you polish a batch.

Full code-contribution flow (DCO sign-off, commit message conventions, what to expect on review) lives in docs/FIRST_CONTRIBUTION.md — same rules apply to art PRs.

What happens when your art lands

Once your PR merges, the next time a player opens the recruit, spells, threats, attack, or community panels they'll see your artwork instead of the placeholder logo. There's no cache bust or migration step — the catalog already references /game/<category>/<id>.png for every entry; your file just fills in the slot.

You'll show up in CONTRIBUTORS once your PR merges.

Questions?

Open an issue on the repo or email hello@cursorboston.com. Browse what's already in public/game/ to see what's already covered.

Open game world map