Skip to content

Comparison

Industrial Brutalist UI (leonxlnx) vs Theme Factory (anthropics)

Industrial Brutalist UI (leonxlnx) and Theme Factory (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

Theme Factory

anthropics/skills

Put a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.

4 scenarios in the bank answer to it

What is the difference between Industrial Brutalist UI (leonxlnx) and Theme Factory (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.
Theme Factory (anthropics)
Put a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.

Should I use Industrial Brutalist UI or Theme Factory?

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 Theme Factory when

The deck is finished and the structure is right. Problem: six slides use three different blues and two fonts, because four people built it. Make it look like one deck.

It is a .pptx, so pptx is the reflex, and pptx is the right skill when slides go in or out. Nothing is going in or out here. The artifact already exists and the job is putting one consistent colour-and-font system across it, which is theme-factory's whole purpose. frontend-design decides how UI should look, and this is not UI.

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