agentleFS
Sign inStart free
madebymustafamadebymustafa/design-taste/skills/brutalist-industrial/SKILL.md

brutalist-industrial

Skill1 starsChanged 3 months agoMITView on GitHub

Genre pack: raw mechanical interface — Swiss typographic print fused with military/industrial terminal aesthetics. Rigid visible grids, extreme type-scale contrast, utilitarian color (paper, ink, one signal color), hard edges, zero decoration. Use for data-heavy platforms, developer tools, portfolios, studios, or any brief wanting to feel like a declassified blueprint. Stack on the design-taste core skill.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 gradients, no shadows, no glows.

    line 26
  2. Distinctive:

    NEVER italic, never serif, never lowercase-as-brand (except deliberate design-read exception).

    line 33
  3. Distinctive:

    No emoji. No icons beyond typographic markers (▪, ▸, ■, →) and drawn square/cross glyphs.

    line 45

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

brutalist-industrial

One identity: a declassified blueprint for a machine you haven't been cleared to see.

1. PALETTE (Fixed)

  • Ground: #F2F1EC (aged paper). Dark ground variant: #1B1B18.
  • Ink: #141414 (near-black, neutral).
  • Signal color — exactly one: safety orange #E8540B, industrial yellow #E3B23C, or technical blue #2B5FA8. Pick by brief; then it never changes.
  • Secondary ink for metadata: #6E6C64.
  • Rules/borders: #141414 full opacity — visible, 1px, everywhere.
  • No gradients, no shadows, no glows. Depth comes from offset solid blocks and rules.

2. TYPOGRAPHY (Fixed)

  • Display: heavy grotesk (Archivo, Archivo Black, or Arial Black fallback), weight 700–900, uppercase, tight tracking (−0.01em), huge scale clamp(2.6rem, 7vw, 6rem).
  • Body: same family at 400, 15–17px, 1.5–1.6.
  • Labels/metadata: monospaced (IBM Plex Mono, ui-monospace), uppercase, letter-spacing: 0.08–0.12em, 10–12px. Section coordinates ("01 / 04"), spec numbers ("GS-114"), and status tags all use mono.
  • NEVER italic, never serif, never lowercase-as-brand (except deliberate design-read exception).

3. COMPOSITION (Fixed)

  • Visible grid discipline: hairline rules (1px solid ink) everywhere — section separators, column dividers, table rows. The grid IS the design.
  • Header block: left-aligned wordmark + mono coordinates right ("N-01 / REV 3"); top and bottom 1px rules closing the masthead.
  • Hero: giant condensed uppercase headline spanning full width, kicker line in mono with a signal-color marker (▪ or ▸), body right-blocked in a 5/12 column, exit line at the bottom: mono small print + signal CTA box.
  • Data as structure: features/pricing rendered as indexed tables or ledger rows with rules — never rounded cards. If cards: square, 1px ink border, no shadow. Selected/featured row gets a signal-color fill (#E8540B with ink text).
  • Buttons: rectangles, 1–2px ink borders, hard offset shadow 4px 4px 0 ink (or signal), press = offset removed.

4. CONTENT TREATMENT

  • No emoji. No icons beyond typographic markers (▪, ▸, ■, →) and drawn square/cross glyphs.
  • Numbers are the decoration: every section gets a mono index number; metrics typeset in mono columns like an instrument panel.
  • Photography: none by default. Full-bleed halftone/greyscale image with a 1px ink frame only if the read demands it.
  • CTAs: one solid CTA (signal fill or ink), plus a plain mono text link. Never two equal buttons.

5. MOTION (Mechanical, Not Pretty)

  • Instant or 80–150ms snaps — machine response, not choreography.
  • Hover: invert (ink→ground), 1px border flip to signal. No float, no wobble, no parallax.
  • One allowed entrance: sections reveal via clip/translate up 8px, 150ms.

6. CHECKLIST (Fail the page if…)

  • Any border-radius above 2px on a major surface.
  • Any gradient, glow, drop-shadow, or blur.
  • More than one signal color in use.
  • Any emoji or whimsical iconography.
  • Display type not uppercase or not heavy.
  • Any italic or serif in a label position.
  • The grid is invisible (no rules, no alignment evidence).
  • A standard rounded-card row of three appears.

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.

Check your setup, free