layer-textures — Claude Code skill: tileable textures with no seams
layer-textures generates repeating textures via Layer API with a tileability filter that eliminates edge seams. Built for game engine materials, trim sheets, and pattern fills.
MIT 4,900 installs ★ 10 updated 2026-09-30
npx skills add layerai/skills --skill layer-textures -a claude-codeWhat layer-textures does
The skill teaches agents to request Layer models that support tiling — without this filter, the left edge does not continue into the right, and the seam shows immediately. Prompts are structured to avoid baked lighting and focal features: 'even diffuse flat lighting, no directional shadows', 'uniform distribution of wear, no dominant crack'. Scale is set through real-world dimensions — 'roughly eight stones across two metres', not just 'cobblestone'.
Evaluation happens at 3×3 repeat: if the tile looks good alone but forms a rhythm or motif when tiled, it has failed. When a model returns normal and roughness maps, the skill takes them in the same run rather than deriving them from the colour map later. For pixel art tiles, there is a separate skill, layer-pixel-art.
What it helps with
- generate a 2×2 metre stone texture with no visible seams for Unreal Engine
- remove baked shadows from a tiling grass texture
- get PBR maps (normal, roughness) together with the colour map in a single run
- check whether a texture forms a grid of repeating cracks when tiled at 3×3
Example prompts for the agent
- Create a mossy stone floor texture for a dungeon, covering roughly 2 metres with about eight stones across, flat lighting, no focal crack
- Make a tileable wood plank texture with planks around 15 cm wide, even lighting, uniform distribution of knots
- Check this texture at 3×3 repeat — does it show a visible motif or seam?
How to install layer-textures
1Skills CLI (Vercel)
npx skills add layerai/skills --skill layer-textures -a claude-code2Manually: put the files in place
~/.claude/skills/layer-textures/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/layer-textures/
1Skills CLI (Vercel)
npx skills add layerai/skills --skill layer-textures -a codex2Manually: put the files in place
.agents/skills/layer-textures/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add layerai/skills --skill layer-textures -a cursor2Manually: put the files in place
.cursor/skills/layer-textures/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install layerai/skills skills/layer-textures2Manually: put the files in place
.github/skills/layer-textures/SKILL.md1Skills CLI (Vercel)
npx skills add layerai/skills --skill layer-textures -a gemini-cli2Platform CLI
gemini skills install https://github.com/layerai/skills --path skills/layer-texturesManually: put the files in place
.devin/skills/layer-textures/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add layerai/skills --skill layer-textures -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about layer-textures
How to install layer-textures in Claude Code?
Run npx skills add layerai/skills --skill layer-textures -a claude-code, and the skill will appear in ~/.claude/skills/layer-textures/SKILL.md.
What does layer-textures do?
The skill teaches agents to generate tiling textures via Layer API with a mandatory tileability: true filter that eliminates edge seams. Without this filter, the left edge does not continue into the right, and the seam is visible immediately.
Why does layer-textures require specifying scale in the prompt?
Without scale, the model does not know how many stones or planks should fit on the tile — it might produce one enormous boulder or a thousand tiny ones. The skill anchors scale to real-world dimensions: 'planks about 15 cm wide', 'grass blades roughly 5 cm'.
Source text
SKILL.md · MIT
---
name: layer-textures
description: "Use when generating a texture with Layer that must repeat without a visible seam: ground, terrain, walls, fabric, foliage, stone, wood, pattern fills, or a tiling material for a game engine. Also when a generated texture shows seams at its edges, an obvious repeating motif across a surface, or baked-in lighting that fights the engine. Keywords: tileable, seamless, tiling, texture, material, pattern, trim sheet, terrain, repeat."
license: MIT
---
# Layer Textures
## Overview
A texture is not an image of a surface. It is an image whose left edge continues into its right edge
and whose top continues into its bottom, so that a plane tiled with it shows no seam. A model will
not do this unless the run asks for it.
The mandatory step is the capability filter: `list_base_models` with
`filter.capabilities: {tileability: true}`. Note the shape: `capabilities` is an object of booleans,
not a list of names. A model without it produces a picture of stone that seams visibly the moment it
repeats, and no editing pass fixes that afterwards. Everything else on this
page is secondary to getting that filter right.
Generation mechanics are in the `layer` skill. If a sibling skill named here is missing from your
available skills, ask the user to install it (`npx skills add layerai/skills --skill <name>`);
unattended, proceed from tool schemas and flag the gap.
## State the scale
Scale is what separates a usable texture from an unusable one, and it is the most commonly omitted
field. Say how much real-world surface the tile covers: "a 2-metre square of cobblestone, roughly
twenty stones across" is a texture. "Cobblestone" could be one boulder or a city square, and the
model will pick.
Anchor it to the feature rather than the tile: "individual planks about 15cm wide", "grass blades
roughly 5cm", "brick courses at standard size". The engine will scale the material, but only if the
density inside the tile is right to begin with.
## Flat light, no hero features
Two prompt clauses do most of the remaining work:
- **Even, diffuse, flat lighting, no directional shadows.** Baked-in shadow is the second-biggest
defect after seams. A texture lit from the upper left looks wrong everywhere the engine's light is
not upper left, and it cannot be removed later.
- **Uniform distribution, no focal point, no single distinguishing feature.** Generative models like
to compose, so they will place one dramatic cracked stone in the middle. Tiled across a floor, that
crack becomes a grid of identical cracks and is the thing every player notices.
Ask for consistent variation instead: "evenly distributed wear and colour variation across the whole
tile, no single dominant feature."
## Judging the result
Do not judge a texture by looking at the tile. Judge it tiled. Check the four edges continue into
each other, then check a 3x3 repeat for a motif that has become a pattern. A tile that looks
excellent alone and shows an obvious rhythm at 3x3 is a failed tile.
If the seam is right but a feature repeats too visibly, the fix is usually a rerun with stronger
uniformity language rather than an edit, since removing the feature locally reintroduces a seam.
## Material maps
A texture for a lit engine scene usually needs more than colour. Where a model declares PBR or
material outputs, take them in the same run rather than deriving normals from the colour map
afterwards, which produces flat-looking surfaces. `get_base_model` is the authority on what a given
model returns.
Pixel-art tiles carry these rules plus their own: see `layer-pixel-art`.
## Worked example
"A seamless mossy stone floor for our dungeon."
1. `list_base_models` with `filter.use_case: "text_to_image"` and
`filter.capabilities: {tileability: true, square: true}`. Take the first result. Without
`tileability` this run is wasted.
2. `get_base_model`, to see whether it exposes a tiling parameter that must also be set, and what
material outputs it offers.
3. Prompt: "Seamless tileable texture of worn dungeon flagstones with moss in the joints, covering
roughly 2 metres square with about eight stones across. Even diffuse flat lighting, no directional
shadows, no cast shadows. Uniform distribution of wear and moss across the whole tile, no focal
point, no single dominant crack or feature. Top-down orthographic view."
4. Estimate, then execute with `batch_size: 4` so there are options.
5. Judge each candidate at a 3x3 repeat before choosing.
## Common mistakes
- Skipping the `tileability` filter, which no later step can compensate for.
- Omitting scale, so the tile is one enormous stone or a thousand tiny ones.
- Accepting directional lighting baked into the tile.
- A dramatic hero feature that becomes a visible grid when repeated.
- Judging the tile on its own rather than tiled at 3x3.
- Deriving normal maps from the colour map when the model could return them directly.
- Requesting a perspective view of a surface instead of a top-down orthographic one.
© layerai · MIT · layerai/skills