signage
Skill4 starsChanged 16 days agoMITView on GitHub
Create realistic signage, markings, labels and decals for futuristic Three.js WebGPU environments such as trains, stations, roads, buildings, habitats and industrial infrastructure.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- howells/skillstheir own version, first seen Nov 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- howells/skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- character-cameraSkill
- character-inputSkill
- character-kitSkill
- character-modelSkill
- character-walkingSkill
- engineered-environmentsSkill
- megacitySkill
- station-maglevSkill
- greenhouseSkill
- pipesSkill
- procedural-geometrySkill
- indirect-lightingSkill
- lightingSkill
- glassSkill
- interior-mappingSkill
- material-compositionSkill
- metalSkill
- paintSkill
- rustSkill
- tsl-materialsSkill
- waterSkill
- threejs-directorSkill
- card-grassSkill
- far-shadeSkill
- ocean-waterSkill
- photo-skySkill
- snow-weatherSkill
- jolt-drivingSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Prefer texture-based decals or dedicated sign geometry for most signage.
- Distinctive: line 14
Use a decal/texture when:
- Distinctive: line 23
Use actual geometry when:
- Distinctive: line 41
use correct colour space
- Distinctive: line 42
use sufficient resolution for viewing distance
- Distinctive: line 43
use alpha only when necessary
- Distinctive: line 44
keep the sign substrate separate from lettering when material response differs
- Distinctive: line 45
avoid enormous unique textures for tiny signs
- Distinctive: line 74
Use a coherent visual language across the environment:
- Distinctive: line 106
Do not make every sign emissive.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Signage
Target: Three.js 0.187.0, WebGPU renderer (three/webgpu) and TSL node materials (three/tsl); WebGPU only, no WebGL fallback, no GLSL strings.
Prefer texture-based decals or dedicated sign geometry for most signage. Do not create individual 3D letters for every ordinary sign unless the letters are physically raised, illuminated or close enough to justify geometry.
Choose the representation
Use a decal/texture when:
- the sign is essentially printed
- it is flat
- it is numerous
- it is viewed at medium/far distance
- the lettering does not need physical relief
- the sign needs many text variants
Use actual geometry when:
- letters are raised
- letters are illuminated
- the sign has substantial thickness
- it is a hero object
- side visibility matters
- shadows from the lettering matter
For flat signage, a small dedicated sign plane or decal-style mesh is often preferable to TextGeometry.
Three.js provides DecalGeometry for projecting detail onto meshes, but projections can distort around corners. Avoid projecting across sharp/complex curvature when accuracy matters.
Texture approach
For a sign texture:
- keep text crisp
- use correct colour space
- use sufficient resolution for viewing distance
- use alpha only when necessary
- keep the sign substrate separate from lettering when material response differs
- avoid enormous unique textures for tiny signs
A sign face drawn to a canvas, on a thin board with real thickness:
import * as THREE from 'three/webgpu';
import { texture, uv } from 'three/tsl';
export function createSign(text, { w = 1.2, h = 0.3, px = 512, lit = false } = {}) {
const c = Object.assign(document.createElement('canvas'), { width: px, height: Math.round(px * h / w) });
const g = c.getContext('2d');
g.fillStyle = '#1d2329'; g.fillRect(0, 0, c.width, c.height);
g.fillStyle = '#f2f2ee'; g.font = `600 ${c.height * 0.55}px sans-serif`;
g.textAlign = 'center'; g.textBaseline = 'middle'; g.fillText(text, c.width / 2, c.height / 2);
const map = new THREE.CanvasTexture(c);
map.colorSpace = THREE.SRGBColorSpace; map.anisotropy = 8;
const face = new THREE.MeshStandardNodeMaterial({ roughness: 0.6, metalness: 0 });
face.colorNode = texture(map, uv());
if (lit) face.emissiveNode = texture(map, uv()).mul(0.8); // a lit panel glows; most signs do not
const edge = new THREE.MeshStandardNodeMaterial({ color: 0x5a6068, roughness: 0.45, metalness: 0.8 });
// BoxGeometry face order: +x, -x, +y, -y, +z (the sign face), -z
return new THREE.Mesh(new THREE.BoxGeometry(w, h, 0.03), [edge, edge, edge, edge, face, edge]);
}Share one atlas across many small signs rather than a canvas each when they are numerous.
Futuristic signage
Use a coherent visual language across the environment:
- station identifiers
- platform numbers
- route markings
- safety markings
- maintenance labels
- directional arrows
- emergency signs
- service identifiers
Signs should communicate real information.
Physical construction
Model:
- sign board
- frame
- brackets
- mounts
- recessed displays
- illuminated housings
when these are visible.
For printed graphics, let the texture provide the lettering rather than adding unnecessary geometry.
Lighting
Illuminated signs should use appropriate emissive treatment, but still have physical housing, thickness and mounting.
Do not make every sign emissive.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

