draw-order-and-depth SKILL.md skillA
draw-order-and-depth from yuiseki/map-from-scratch is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/map-from-scratch/draw-order-and-depth@git:20261027.231c915Pins git:20261027.231c915 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/map-from-scratch
- Path
.agents/skills/draw-order-and-depth/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261027.231c915, committed Oct 27, 2026
- First version recorded
- Oct 26, 2026
- Size
- 34,972 bytes
- Repository stars
- 24
- License
- GPL-3.0
How 42 map engines decide what is drawn on top (painter's order, depth buffer as layer order, stencil per tile, offscreen layer compositing, labels-last passes, near/far planes) and what they reverted. Load it before writing the draw-order rule of bake.ts or the pass list of a renderer, when a request has translucent layers, casings, overlapping tiles, labels over geometry, pitch or 3D, and whenever a screenshot shows the wrong thing on top, darker overlaps, double-blended tile seams…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Draw order and depth: decide the order once, at bake time Every map is layered: land under water under roads under labels, casings under road fills, small areas over large ones. A general engine cannot know the layers in advance, so it re-sorts at run time, encodes layer order into the depth buffer, masks tiles with the stencil buffer and composites layers through offscreen buffers, and each of those has a cost and its own bugs. Engines also hit the same three traps again and again: translucent geometry that overlaps itself darkens [7][54], buffered tiles blend twice along their seams [26][68], and anything that shares a depth value with something else flickers or vanishes depending on driver precision [29][87][105]. A renderer made for one request knows its layers when it bakes, so its draw order can be the order of the bytes in the file and of the draw calls in `draw()` [1][2][3]. What it still needs from the engines is the list of situations where order alone is not enough, and the cheapest fix each one found. Per-engine detail, with all numbers: [references/engines.md](references/engines.md). Depth precision (near plane, log and reversed depth) is covered in more …
Read the whole file at its exact version.
How to install
mdr add yuiseki/map-from-scratch/draw-order-and-depth@sha256:fcfff9d0b096ff41The line at the top of this page pins the label git:20261027.231c915, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_h33q5mvsscnblv33)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 26, 2026 and Oct 27, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.231c915 latest | 2026-10-27 | 231c915 | 34,972 B | A | view · diff |
| git:20261026.79a684e | 2026-10-26 | 79a684e | 34,969 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (34972 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuiseki/map-from-scratch · 24 stars · license GPL-3.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h33q5mvsscnblv33 GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/map-from-scratch/draw-order-and-depth GET https://markdownregistry.com/api/v1/blob/fcfff9d0b096ff41cff56f7241850b956b51fc43f08e806950e85292976f6a90
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.