SkillAgentSearch skills...

3d-high-resolution-textures

Build sharp, physically coherent high-resolution materials for 3D rendering with appropriate PBR maps, texel density, UV direction, mipmaps, anisotropic filtering, and progressive asset delivery.

Install / Use

npx skills add MengTo/Skills --skill 3d-high-resolution-textures

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of 3d-high-resolution-textures

3d-high-resolution-textures scores 83/100 on our quality scale, 3064th of 4,698 Development & Engineering skills we index.

Its SKILL.md is 5.6 KB long, split into 6 sections and no code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so 3d-high-resolution-textures is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

3d-high-resolution-textures compared with similar skills

All 4 of these similar skills score higher than 3d-high-resolution-textures; compare them before choosing.

SkillScoreStarsUpdatedFormat
3d-high-resolution-textures (this skill)by MengTo836.3k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install 3d-high-resolution-textures?
Run npx skills add MengTo/Skills --skill 3d-high-resolution-textures. The install tabs above show the steps for each supported agent.
Which AI agents does 3d-high-resolution-textures work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is 3d-high-resolution-textures safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is 3d-high-resolution-textures still maintained?
The repository was last updated about 2 months ago, so 3d-high-resolution-textures is actively maintained.

name: 3d-high-resolution-textures description: Build sharp, physically coherent high-resolution materials for 3D rendering with appropriate PBR maps, texel density, UV direction, mipmaps, anisotropic filtering, and progressive asset delivery. Use for detailed wood, stone, fabric, foliage, and architectural close-ups without excessive download or GPU memory costs.

3D High-Resolution Textures

Make materials hold up at the closest intended camera view. Specify visible surface detail, mapping scale, and delivery cost together.

Choose resolution from the view

Identify hero surfaces, their nearest camera distance, projected pixel coverage, and target render scale. A texture need depends on visible UV coverage: if a surface spans 1200 physical pixels while showing half a tile, a roughly 2400-pixel-wide tile is a useful starting estimate. Inspect the result rather than assigning 4K or 8K to every map.

Use higher resolution for readable close-up albedo/normal details and lower resolution for smooth roughness or distant surfaces when they look equivalent. Match texel density across connected surfaces. Upscaling a small source cannot invent captured detail; obtain a better source or author appropriate procedural detail when necessary.

Build a coherent PBR material

| Map | Role | Color interpretation | | --- | --- | --- | | Base color, emissive color | Surface color or emitted color | sRGB for ordinary PNG/JPEG/WebP color artwork | | Normal, roughness, metalness, AO, height | Numerical material data | No color-space conversion | | HDR lighting image | Radiance for environment lighting | Use the format/loader's linear HDR interpretation |

Keep lighting calculations linear and apply final output conversion once. Configure maps according to the material and renderer version; see Three.js color management.

Use base color without baked directional highlights when dynamic lighting is expected. Orient wood grain along the member, stone scale to actual units, and woven fibers to fabric construction. Share tiling transforms across maps belonging to one material. Check tangent-space normal convention and seams under a moving light. Verify the AO UV channel supported by the installed renderer rather than blindly duplicating an obsolete attribute name.

Combine broad color variation, mid-scale structure, and subtle microdetail. Keep bump/normal intensity plausible. Normal and bump maps alter shading; silhouette detail requires geometry or displacement with enough vertices. Wood, stone, and cloth are generally dielectric surfaces, so increasing metalness to make them shiny is not a material fix.

Preserve detail during sampling

Enable mipmaps and appropriate minification filtering for ordinary static textures. Use anisotropic filtering for grazing-angle floors, roofs, and timber, capped by renderer.capabilities.getMaxAnisotropy(). Compare moderate values before assigning the maximum everywhere; anisotropy improves oblique sampling, not missing source detail.

For foliage cutouts, pad atlas cells, bleed edge color into transparent texels, and preserve alpha coverage across mip levels. Inspect distant cards against a bright sky for dark fringes or disappearing leaves. Do not threshold every mip blindly; choose a method compatible with alpha testing or alpha-to-coverage.

Deliver detail progressively

  • Load the opening view's essential maps first. Use a small useful placeholder or lower-resolution variant, then promote near-visible hero surfaces without changing their UV scale or material identity.
  • Queue optional rooms and detail views shortly before the camera reaches them. DOM loading="lazy" does not schedule WebGL texture requests; use scene visibility, camera distance, or chapter state explicitly.
  • Deduplicate requests and cache texture variants by full asset identity plus sampling/color settings. Do not key by a filename suffix that may collide.
  • Keep assets external and cacheable. WebP/AVIF can reduce network bytes for color imagery; inspect data maps for compression artifacts. They usually decode to uncompressed GPU textures. KTX2/Basis can also reduce GPU storage where supported; configure and verify the transcoder and fallback. See KTX2Loader.
  • Dispose superseded GPU textures when no material still references them. Reusing image bytes across separate WebGL contexts does not share the GPU allocation.

A 4096² RGBA8 texture with a full mip chain is approximately 85.3 MiB in GPU storage before driver overhead. A small compressed download can therefore still produce a large allocation. Budget the entire material set, decoded CPU images, and concurrent upgrades, not just file size.

For procedural maps, bake stable assets ahead of time where useful. Cache shared noise/height fields, process large work in bounded batches or workers, and avoid millions of canvas drawing calls during startup. Yielding around one huge synchronous operation does not divide its stall.

Verify

Inspect close-up and grazing-angle views at the intended display resolution, then compare the same material farther away. Check seams, grain direction, alpha rims, normal orientation, and color under neutral and final lighting. Record opening bytes separately from total assets, requested dimensions, estimated GPU memory, texture promotion hitches, and missing assets on mobile.

Read REFERENCES.md. In Seijaku, inspect barUV, assetTex, the leaf mip/bleed preparation, shared procedural fields, and chapter-based texture scheduling. Those patterns explain its material detail better than source dimensions alone.

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryDevelopment
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions