Skip to content
Back to search

pixel-path

MarketplaceWorks with Claude CodeGitHub

Pixel Path: pixel-art fly-throughs of real routes between any two places

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jonwheatley--pixel-path/badge.svg)](/listings/jonwheatley--pixel-path)

HTML

<a href="/listings/jonwheatley--pixel-path"><img src="/api/listings/jonwheatley--pixel-path/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**As a plugin.** In Claude Code:

/plugin marketplace add jonwheatley/pixel-path
/plugin install pixel-path@pixel-path

**By hand.** Copy this folder into your skills folder, so that the skill is at `~/.claude/skills/pixel-path/SKILL.md`. For a single project, use `.claude/skills/pixel-path/` inside it.

Then ask Claude: "make me a pixel path from Paris to Versailles".

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "pixel-path",
  3. "description": "Pixel Path: pixel-art fly-throughs of real routes between any two places",
  4. "owner": { "name": "jonwheatley", "url": "https://github.com/jonwheatley" },
  5. "plugins": [
  6. {
  7. "name": "pixel-path",
  8. "source": "./",
  9. "description": "Turn any two places into a pixel-art fly-through of the real road, with scenery art at three levels of detail and a self-check."
  10. }
  11. ]
  12. }
README.md · README · 164 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Pixel Path
  2. A Claude Code skill that turns any two places into a pixel-art fly-through of the real road. Ask Claude for "a pixel
  3. path from Bath to Bristol" and it:
  4. - routes the trip
  5. - bakes the real buildings, land cover, landmarks, hills and horizon along it from OpenStreetMap and elevation data
  6. - generates scenery art for the region with [RetroDiffusion](https://www.retrodiffusion.ai?ref=YBQJM823) (affiliate
  7. link)
  8. - checks its own work with screenshots
  9. - hands you a page where you zoom along the route. Scroll to go faster, slower or backwards.
  10. <img src="docs/demo.webp" width="100%" alt="Flying through Bath, England, at the moderate level">
  11. *Bath, England: real streets from OpenStreetMap, art generated with the `moderate` kit.*
  12. ## What it is for
  13. A first-person, pixel-art view of any real road, built from the real map. Useful wherever you want a real place or route
  14. on screen:
  15. - **Games:** a real road as a level for a driving, racing, idle or endless-runner game, instead of a made-up one.
  16. - **Showing a journey:** a commute, a delivery round, a marathon or cycling stage, a road trip you took, a move between cities.
  17. - **Content:** trip recaps, travel posts, video intros, stream backgrounds and lo-fi loops.
  18. - **Places and history:** Route 66, a pilgrimage route, the road in a news story, a preview of a neighbourhood.
  19. - **Learning:** a commented pseudo-3D renderer and an OpenStreetMap bake pipeline to read or build on.
  20. ## What you get
  21. A folder with an `index.html`. Open it through any static web server and you are moving down the real road:
  22. - **Buildings on their real footprints.** Every building that faces the road is a block on its real line, with the
  23. kind of picture its type and height call for. A long frontage becomes a row of different buildings, and cracks and
  24. short lots are closed.
  25. - **More of the real place.** A second row of buildings shows across squares and car parks, tall buildings make a
  26. skyline, and landmarks stand at their real places.
  27. - **The real ground.** Fields, forest, water, parking lots and sidewalks are drawn per pixel from the map. The hills
  28. are real, and so is the horizon, marched over a 61 × 61 km height grid with the Earth's curvature.
  29. - **Signs drawn by code,** so the names are exact: town names, distances, street names, brown landmark signs and
  30. railway crossings.
  31. - **No interface** apart from a small credits line:
  32. - Scroll (or drag on a touch screen) to speed up from a crawl to very fast. Keep going the other way to slow down
  33. and reverse.
  34. - The arrow keys do the same, and Space pauses.
  35. - `I` shows where you are and `M` shows a small map.
  36. ## Three levels of detail
  37. Before anything slow happens, the first step prints an estimate for your route, and the skill asks you to choose.
  38. Only the art costs money: $0.18 a picture at RetroDiffusion's `rd_pro__default` (October 2026). Cost depends on the
  39. number of regions (distinct looks along the route), not on distance.
  40. | level | pictures per region | 1 region | 2 regions | what you get |
  41. | --- | --- | --- | --- | --- |
  42. | placeholders | 0 | $0 | $0 | code-drawn stand-ins for every picture |
  43. | **sparse** | 4 | $0.72 | $1.44 | three kinds of building and a tree. Every lot is still filled; mirrored and tinted copies stretch the pictures. |
  44. | **moderate** | about 14, + 4 landmarks | $3.24 | $5.76 | about ten buildings across the main kinds, two trees, a shrub, a street prop, the four best-known landmarks |
  45. | **detailed** | about 26, + 10 landmarks | $6.48 | $11.16 | up to six variants of each kind of building, three trees, two shrubs, three street props, ten landmarks |
  46. The levels are nested, so moving up a level only pays for the new pictures. The exact quote is free and comes after
  47. the bake. Allow about 25% on top for re-rolls: in testing, 10% (Bath) to 34% (Manhattan) of pictures came back cut off
  48. or on a background. The cleanup dropped them, and the self-check re-rolled them within the budget.
  49. ### Examples
  50. Bath to Bristol at **moderate** (two regions, Georgian Bath, then Victorian Keynsham and Bristol, 32 pictures, $5.76):
  51. ![Bath to Bristol at moderate](docs/bath-moderate.webp)
  52. Kyoto Station to Kinkaku-ji, Japan, at **sparse** (one region, four pictures, $0.72):
  53. ![Kyoto at sparse](docs/kyoto-sparse.webp)
  54. Both runs passed the full self-check, including the sweep: 627 and 345 moving frames, with no sky through or between
  55. buildings. The estimate printed after routing matched the exact quote in every test run.
  56. ## Install
  57. **As a plugin.** In Claude Code:
  58. ```
  59. /plugin marketplace add jonwheatley/pixel-path
  60. /plugin install pixel-path@pixel-path
  61. ```
  62. **By hand.** Copy this folder into your skills folder, so that the skill is at
  63. `~/.claude/skills/pixel-path/SKILL.md`. For a single project, use `.claude/skills/pixel-path/` inside it.
  64. Then ask Claude: "make me a pixel path from Paris to Versailles".
  65. ## Requirements and setup
  66. - **Node 18 or newer.** No npm packages are needed to build a route.
  67. - **A RetroDiffusion account with credit, for real art:** <https://www.retrodiffusion.ai?ref=YBQJM823>. **This is an
  68. affiliate link** (the author of this skill gets a referral).
  69. - Create an API key and set it in your own terminal with `export RETRODIFFUSION_API_KEY=...`.
  70. - On a Mac you can store it in the Keychain instead: `security add-generic-password -s pixel-path -a retrodiffusion -w`.
  71. - Never paste the key into a chat. The skill never asks for it and never prints it.
  72. - Without an account, placeholders cost nothing.
  73. - **For the self-check's screenshots:** Node 20 or newer with Playwright and Chromium (`npm i -D playwright && npx
  74. playwright install chromium`). Without them, the layout and art checks still run.
  75. - **Network access while baking** to Nominatim, OSRM, Overpass, AWS Terrain Tiles and Wikidata. Baking takes about 20
  76. to 60 seconds per 10 km.
  77. ## How it checks itself
  78. The skill doesn't call a route done when the code runs. It calls it done when the pictures pass:
  79. 1. **Every building is a solid.** Each building is laid along its real line and always gets a shaded end wall, so it
  80. never reads as a flat card. A neighbour that joins it paints over the part it covers.
  81. - Cracks under 3 m are closed.
  82. - In a dense street, a building mapped far back is pulled up to the sidewalk.
  83. - A backing building stands behind every gap in a built-up row.
  84. - A second row of real buildings shows across squares and car parks.
  85. 2. **Cleanup.** Each picture is cleaned and its backdrop flood-filled away. Holes in facades are filled, including a
  86. roof-to-ground gap between two houses drawn in one picture. Pictures that still carry a background, painted sky, a
  87. cut-off edge or a sliver are dropped. A contact sheet of every picture is written for Claude to look at.
  88. 3. **Layout check.** The whole route is laid out exactly as the page will draw it, checking for gaps in street walls
  89. and for a building with the same picture as its neighbour.
  90. 4. **The sweep.** Every 75 m of built-up road, the camera moves and looks straight ahead and 30° to each side. The sky
  91. is painted magenta and every building is drawn into a mask, and it counts:
  92. - sky seen through a building
  93. - slits of sky between two parts of the same street wall that reach down to the ground
  94. The 20 worst frames are written side by side with the problem marked.
  95. 5. **Review.** Claude is told to look at the worst frames and the samples and keep fixing until the sweep is clean.
  96. ## Credits and licences
  97. The page shows a credits line that must stay visible wherever a fly-through is shown.
  98. - **Map data © OpenStreetMap contributors**, under the
  99. [Open Database Licence](https://www.openstreetmap.org/copyright). A route's `data/` folder is a derived database: if
  100. you share it publicly, it stays under the ODbL, with credit.
  101. - **Routing:** [OSRM](https://project-osrm.org/), from OpenStreetMap data. The public servers are for light use.
  102. - **Geocoding:** [Nominatim](https://nominatim.org/), under the OSM Foundation's usage policy.
  103. - **Elevation:** [Terrain Tiles](https://registry.opendata.aws/terrain-tiles/) (Mapzen/Tilezen on AWS Open Data), from
  104. SRTM, GMTED2010, ETOPO1, NED and others
  105. ([attribution](https://github.com/tilezen/joerd/blob/master/docs/attribution.md)).
  106. - **Landmarks:** [Wikidata](https://www.wikidata.org/) (CC0).
  107. - **Art:** generated by you with [RetroDiffusion](https://www.retrodiffusion.ai?ref=YBQJM823) (affiliate link), under
  108. RetroDiffusion's terms of service. The pictures in this README were generated with this skill.
  109. - **Code:** MIT (see `LICENSE`), by Jon Wheatley. The road projection is the classic arcade technique (see Lou's Pseudo
  110. 3D Page and Jake Gordon's Javascript Racer).
  111. ## Known limits
  112. - **OpenStreetMap coverage decides the street.** Where buildings aren't mapped, plausible ones are filled in by land
  113. use (houses on lawns, shops on paved land, a row behind in dense towns). Heights are often missing and are guessed
  114. from building type.
  115. - **Open spaces look open.** Squares, junctions, car parks and parks read as wide paving or grass with buildings across
  116. them, because that is what is there. Some frames in a city centre show more paving than you would expect.
  117. - **The art is the model's.** The cleanup catches backgrounds, painted sky, cut-off pictures and slivers, but not
  118. everything: a building drawn at an angle, for example. Claude is told to look at every picture and re-roll bad ones,
  119. at the cost of a picture each.
  120. - **One look per region.** Every town in a region uses the same kit, and long streets show the same pictures again
  121. further along. Split a long route into more regions for more variety, at more cost.
  122. - **Landmarks are pictures, not models.** A landmark faces the road and does not turn as you pass. You need to
  123. describe what it looks like (the model does not know buildings by name), and a landmark just behind the start point
  124. is not shown.
  125. - **Overpass is the slow, flaky step.** The public servers time out under load. The bake retries across mirrors and
  126. resumes, but a long route can take an hour on a bad day.
  127. - **Driving routes only, in one afternoon light.** Routes come from OSRM's car profile. There is no traffic, no people
  128. and no weather.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.