Comparison
Industrial Brutalist UI (leonxlnx) vs Web Artifacts Builder (anthropics)
Industrial Brutalist UI (leonxlnx) and Web Artifacts Builder (anthropics) are both Visual skills, so an agent choosing between them is matching on descriptions that overlap. Here is where they actually diverge.
Industrial Brutalist UI
leonxlnx
Commits a build to one hard-edged look: exposed structure, sizes that jump from tiny to enormous, colour used only to warn, and print or CRT artefacts faked in software. Pick it when the interface should read as machinery rather than a product, and when packing the screen is the point.
1 scenario in the bank answers to it
Web Artifacts Builder
anthropics/skills
Ambitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
8 scenarios in the bank answer to it
What is the difference between Industrial Brutalist UI (leonxlnx) and Web Artifacts Builder (anthropics)?
- Industrial Brutalist UI (leonxlnx)
- Commits a build to one hard-edged look: exposed structure, sizes that jump from tiny to enormous, colour used only to warn, and print or CRT artefacts faked in software. Pick it when the interface should read as machinery rather than a product, and when packing the screen is the point.
- Web Artifacts Builder (anthropics)
- Ambitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
Should I use Industrial Brutalist UI or Web Artifacts Builder?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Industrial Brutalist UI when
A satellite operations team wants their telemetry console to look like the equipment it watches: everything on one dense screen, readings in monospace, sizes that jump from a tiny label to an enormous number, colour only where something is wrong, and a faint scanline over the whole thing. They know it will look hostile to anyone outside the team, and that is the intent.Exposed structure, sizes that jump from tiny to enormous, colour reserved for warning, print or CRT artefacts faked in software, and a screen that is meant to be packed: this is the one option that treats all of that as the goal rather than as damage. The most tempting wrong answer is high-end-visual-design, since it too commits hard to a non-generic look - its trap is that its whole vocabulary is lift, light and easing, so it would soften exactly what this team wants left hard. minimalist-ui shares the refusal of ornament but empties the screen out, where this console wants it dense. design-taste-frontend is scoped to surfaces meant to be scrolled and read, and hands an operations console off.
Reach for Web Artifacts Builder when
For your conference talk you want the demo to run INSIDE the slides look-alike: a fake 'deck' where one slide is actually a live calculator the audience can try afterward from a link.A LIVE, interactive thing shared by link is an artifact wearing a deck costume - real .pptx files can't run calculators. pptx is the deliberate trap: the word 'slides' appears, but the requirement 'audience can try it' rules physical decks out.
What they have in common
Both are filed under Visual, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone - and what makes it pick wrong.
Nearby comparisons
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session