neo-industrial-design
elithrar/dotfiles · Agent Skill
Sviluppa o rielabora interfacce web in stile neoindustrialista o editoriale-brutalista con tipografia ingegneristica, disciplina della griglia e layout composti fisicamente.
Vai all'installazione ↓Panoramica
| Autore | |
|---|---|
| Repository | elithrar/dotfiles ↗ |
| Cartella dello skill | neo-industrial-design |
| Stelle | 221 |
| Fork | 16 |
| File inclusi | 4 |
| Licenza | MIT |
| Aggiornato | 18 ottobre 2026 |
| Link | Sorgente dello skill ↗ · Repository ↗ |
Verifica Mozgi
Cosa abbiamo trovato nei file dello skill. I dettagli con l’abbonamento.
Installazione
Uno skill è una cartella con un file SKILL.md. Scegli il tuo agente ed esegui i comandi in un terminale (macOS, Linux o Git Bash su Windows) dalla radice del progetto.
Incolla il prompt in Claude, Codex o un altro assistente: controllerà lo skill e lo installerà.
Install the “neo-industrial-design” skill from mozgi.io (https://mozgi.io/skills/elithrar-neo-industrial-design/) for me. 1. Download the archive: https://mozgi.io/skills/elithrar-neo-industrial-design/download If it fails, take the skill folder from the source: https://github.com/elithrar/dotfiles/tree/main/.agents/skills/neo-industrial-design 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “neo-industrial-design” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/neo-industrial-design/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/elithrar/dotfiles.git /tmp/dotfiles mkdir -p .claude/skills cp -r /tmp/dotfiles/.agents/skills/neo-industrial-design .claude/skills/neo-industrial-design
Riavvia Claude Code: lo skill compare nell'elenco; per richiamarlo a mano usa /neo-industrial-design. Per tutti i progetti: ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/elithrar/dotfiles.git /tmp/dotfiles mkdir -p .agents/skills cp -r /tmp/dotfiles/.agents/skills/neo-industrial-design .agents/skills/neo-industrial-design
Codex cerca gli skill in .agents/skills dalla cartella corrente fino alla radice del repo; richiamalo con /skills o $neo-industrial-design. Per tutti i progetti: ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/elithrar/dotfiles.git /tmp/dotfiles mkdir -p .cursor/skills cp -r /tmp/dotfiles/.agents/skills/neo-industrial-design .cursor/skills/neo-industrial-design
Cursor carica lo skill all'avvio; richiamalo con “/” nella chat Agent. Cursor legge anche .claude/skills e .agents/skills. Per tutti i progetti: ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/elithrar/dotfiles.git /tmp/dotfiles mkdir -p .gemini/skills cp -r /tmp/dotfiles/.agents/skills/neo-industrial-design .gemini/skills/neo-industrial-design
Gemini CLI propone di attivare lo skill quando il compito corrisponde: tu confermi. Per tutti i progetti: ~/.gemini/skills.
Leggi SKILL.md e i file correlati prima di installare. Clicca un file per l'anteprima.
Contenuto di SKILL.md
Testo originale dell'autore · sola letturaNeo-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:
1. Mode: editorial, instrumental, or hybrid. Editorial mode is type-led and poster-like. Instrumental mode is image- or interface-led. Hybrid mode alternates them.
2. 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.
3. Grid: columns, outer gutter, and recurring alignment axes. Deliberate violations should remain accountable to those axes.
4. 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
1. Establish section proportions, dominant fields, reading order, and the type/image silhouette.
2. Lock the display, body, and annotation type roles and their scale contrast.
3. Apply the grid to content edges, rules, images, navigation, and repeated modules.
4. Introduce only the graphic motifs that reinforce an alignment, boundary, state, measurement, or interaction.
5. 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.
Domande frequenti
Che cosa fa lo skill neo-industrial-design?
Sviluppa o rielabora interfacce web in stile neoindustrialista o editoriale-brutalista con tipografia ingegneristica, disciplina della griglia e layout composti fisicamente.
Come si installa neo-industrial-design?
Apri il blocco “Installazione” in questa pagina e scegli il tuo agente — Claude Code, Codex, Cursor o Gemini CLI — per i comandi pronti che copiano la cartella dello skill nel posto giusto. Oppure copia il prompt dalla scheda “Con l'assistente” e lascia che sia l'assistente a controllare e installare lo skill.
Con quali modelli AI funziona neo-industrial-design?
Gli skill sono semplici istruzioni in Markdown (formato Agent Skills), quindi neo-industrial-design funziona con qualsiasi agente che legge SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode e altri. Il modello carica le istruzioni solo quando il compito corrisponde alla descrizione dello skill.
neo-industrial-design è gratuito?
Lo skill è pubblicato apertamente da elithrar con licenza MIT. Lo skill in sé non costa nulla: paghi solo il tuo fornitore AI per i token usati.
È sicuro installare gli skill?
Uno skill è un insieme di istruzioni che il tuo agente seguirà: leggi SKILL.md e i file correlati prima di installarlo. Gli script nella cartella dello skill vengono eseguiti solo se li esegue l'agente: controlla cosa fa e non concedere permessi superflui.
In cosa differisce uno skill da un server MCP o da un plugin?
Un server MCP o un plugin danno al modello nuovi strumenti: codice che viene eseguito e restituisce un risultato. Uno skill fornisce conoscenza e metodo: come affrontare il compito, quali passi seguire e com'è un buon risultato. Non servono server né chiavi API.