neo-industrial-design
Skill222 starsChanged 58 days agoMITView on GitHub
Design or restyle web interfaces in the user's neo-industrial or editorial-brutalist style. Use when that visual direction is requested; not for generic dashboards, dark themes, or copywriting.
In this repository13 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- animated-spritesSkill
- anti-slopSkill
- code-reviewerSkill
- create-readmeSkill
- cut-readySkill
- engineering-drawingsSkill
- logging-sucksSkill
- motronicSkill
- prompt-engineerSkill
- summarize-workSkill
- web-perfSkill
- wow-addon-developmentSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 21
Read references/visual-system.md before designing or restyling the interface.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Neo-Industrial Design
Apply a coherent visual system to web content. The result should feel engineered, editorial, and physically composed: typography carries the hierarchy, a disciplined grid controls tension, imagery behaves as evidence, and technical graphics clarify structure or state.
The user's instructions and existing product requirements take precedence. Treat supplied copy, facts, information architecture, and imagery as content inputs. Do not research, fact-check, or rewrite substantive content unless the user explicitly asks. When required content is missing, use neutral placeholders or leave the region open rather than inventing subject matter.
Set the visual thesis
Infer these choices from the supplied brief and existing interface; make routine design decisions without a separate approval round:
- Mode: editorial, instrumental, or hybrid. Editorial mode is type-led and poster-like. Instrumental mode is image- or interface-led. Hybrid mode alternates them.
- Dominant gesture: one primary move, such as an edge-cropped title, a full-bleed image under a grid, a bracketed word, or a giant index.
- Grid: columns, outer gutter, and recurring alignment axes. Deliberate violations should remain accountable to those axes.
- Signal: one accent color with a consistent visual role such as action, selection, position, or emphasis.
Read references/visual-system.md before designing or restyling the interface. Use it as a system of relationships, not as a checklist of effects.
Build from macro to micro
- Establish section proportions, dominant fields, reading order, and the type/image silhouette.
- Lock the display, body, and annotation type roles and their scale contrast.
- Apply the grid to content edges, rules, images, navigation, and repeated modules.
- Introduce only the graphic motifs that reinforce an alignment, boundary, state, measurement, or interaction.
- Compose both mobile and desktop around the primary task. In an instrumental interface, keep the map, data, or working surface dominant; oversized titles and decoration must not displace it.
Preserve semantic HTML, source-order clarity, keyboard access, visible focus, alt text, useful contrast, and readable body sizes. Technical styling does not justify inaccessible text or controls.
Make responsiveness compositional
- Recompose wide grids into fewer columns instead of shrinking the desktop canvas uniformly.
- Set intentional mobile headline breaks and preserve the primary reading path.
- Move secondary rails after main content; remove only redundant decoration.
- Prevent interactive content from clipping or causing horizontal scrolling.
- Retain deliberate display-type cropping only when the title remains understandable and fully available to assistive technology.
Review the rendered result
For implemented changes, use references/review.md to inspect the affected page at wide desktop and narrow phone widths. Fix failures in hierarchy, alignment, legibility, responsiveness, or interaction within the requested implementation. For review-only requests, report findings without changing or publishing the interface. Do not add motifs to compensate for a weak composition.
Output
Deliver a usable, responsive web interface with one legible visual thesis and a consistent design system. In the handoff, state the chosen mode and the most important visual correction made during rendered review.
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
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.

