agentleFS
arjun988arjun988/blender-skills/.claude/skills/lowpoly-style/SKILL.md

lowpoly-style

Skill2.2k starsChanged 4 months agoMITView on GitHub

Low-poly art direction for Blender inspired by PS1/PS2, Lethal Company, Mouthwashing, and Fear to Fathom. Use for readable silhouettes, minimal polygons, simple materials, and strong atmosphere.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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
  1. Distinctive:

    No micro-bevels (0 bevel or single segment max)

    line 50
  2. Distinctive:

    Before approving any asset:

    line 82
  3. Distinctive:

    If unreadable → simplify geometry, not add detail

    line 86
  4. Distinctive:

    Create low-poly blockouts via MCP

    line 105
  5. Distinctive:

    Use vertex colors and atlases

    line 116
  6. Distinctive:

    Test at gameplay camera distance

    line 117

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Low Poly Style Specialist

Readable silhouettes. Large shapes. Minimal polygons. Atmosphere over detail.

When to Use

  • Retro aesthetic games (PS1/PS2 era)
  • Lethal Company / Mouthwashing style projects
  • Mobile/low-spec targets
  • Horror with efficient geometry
  • Stylized simplicity

Core Rules

  1. Readable silhouettes — Shape reads at distance without detail
  2. Minimal polygons — Every face must earn its place
  3. Large shapes — Primary forms dominate; micro-detail forbidden
  4. Simple materials — Flat or lightly textured; 512px default
  5. Limited texture sizes — 256–512px most assets; 1024 hero only
  6. Strong atmosphere — Lighting and fog carry visual weight

Polygon Guidelines

AssetTriangle Target
Character500–3,000
Prop50–500
Environment module100–800
Tree200–800
Vehicle2,000–8,000

See ../references/polycount-budgets.md — apply 50–90% reduction.

Modeling Approach

  • No subdivision surface
  • No micro-bevels (0 bevel or single segment max)
  • Flat shading OR auto smooth at 60°+
  • Merge coplanar faces where possible
  • Texture carries detail, not geometry

PS1 Authenticity (Optional)

EffectTechnique
Affine texture warpEngine-side; note in export docs
Vertex jitterSlight snap to low grid
Low resolution320×240 render target reference
No filteringNearest neighbor textures
Z-fighting aestheticIntentional minimal offset (use carefully)

PS2 Era

  • Slightly higher poly budgets
  • Basic normal maps allowed
  • Single directional light + ambient
  • 512–1024 textures

Material Approach

  • Vertex colors for variation (preferred)
  • Single texture atlas per scene/kit
  • Minimal roughness variation
  • Emissive for screens/lights
  • No PBR micro-detail

Silhouette Test

Before approving any asset:

  1. Solid flat color material
  2. View at gameplay distance
  3. Silhouette must communicate identity
  4. If unreadable → simplify geometry, not add detail

Lethal Company Influence

  • Industrial sci-fi interiors
  • High contrast lighting
  • Chunky readable props
  • Fog-heavy environments
  • Multiplayer-readable shapes (clear at distance)

Mouthwashing Influence

  • Soft pastel palette option
  • Surreal but simple geometry
  • Strong color blocking
  • Uncanny but low-detail characters

MCP Integration

  1. Create low-poly blockouts via MCP
  2. Enforce face count limits via MCP queries
  3. Assign flat materials via MCP
  4. Validate triangle budgets continuously
  5. Skip subdiv/bevel modifiers entirely

Constraints

MUST DO

  • Enforce strict poly budgets
  • Prioritize silhouette over surface detail
  • Use vertex colors and atlases
  • Test at gameplay camera distance
  • Coordinate atmosphere with lighting skill

MUST NOT DO

  • Subdivision surfaces
  • High-resolution textures on background assets
  • Micro-bevels or weighted normal stacks
  • Sculpting detail (bake workflow unnecessary)
  • Exceed triangle budgets "just a little"

Reference Guide

TopicReferenceLoad When
PS1 techniquesreferences/ps1-aesthetic.mdRetro authentic look
Asset budgets../references/polycount-budgets.mdBudget setting

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.