agentleFS
fmindfmind/dotfiles/skills/fmind-visuals/SKILL.md

fmind-visuals

Skill13 starsChanged 4 days agoMITView on GitHub

Create VHS terminal demos and logo or cover variants in Fmind/client branding.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • fmind/dotword for word, first seen Nov 8, 2026

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:

    Explore variants: when the look is open (logo, cover, hero illustration) or the user rejects a draft: follow variants instead of iterating …

    line 21
  2. Distinctive:

    Create: follow recording.md for VHS demos and keep the tape and synthetic inputs.

    line 22
  3. Distinctive:

    Cut decoration: remove decorative nodes, gradients, and generic AI imagery.

    line 27

≈ “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

Fmind Visual Communication

Apply the customer's brand when the work belongs to one; otherwise the Fmind design in ~/.agents/DESIGN.md (source): readable typography, spacious composition, and evidence-backed claims.

Workflow

  1. Select the format: VHS for reproducible terminal demonstrations, unless the user or an existing project names another. Diagrams as code owns diagrams and illustrations (Mermaid, SVG, and D2, including Fmind-branded diagrams).
  2. Apply the brand: customer or employer work uses that organization's design system, palette, fonts, and logo; ask for its brand guide rather than guessing, and never mix brands. An existing project keeps its identity. Otherwise read ~/.agents/DESIGN.md for tokens, components, and do's and don'ts, map it with renderers.md, bundle the fonts with their OFL notices, and use the existing reviewed logo. Preserve published assets when the design changes.
  3. Explore variants when the look is open (logo, cover, hero illustration) or the user rejects a draft: follow variants instead of iterating on one guess.
  4. Create: follow recording.md for VHS demos and keep the tape and synthetic inputs. Fmind diagrams follow diagrams-as-code with the renderers.md mappings and diagram.d2.
  5. Verify: compile success is not visual success. Inspect every rendered frame, image, or diagram for legibility, clipping, font loading, and accessibility, and keep editable sources beside their exports.

Gotchas

  • Cut decoration: remove decorative nodes, gradients, and generic AI imagery.
  • Edit the source, not a copy: change the design in fmind/theme's DESIGN.md; templates and adapters here only carry native values for renderers.

Task guides

<!-- guides:start -->
  • variants: Numbered logo, cover, or illustration variant rounds with a light and dark contact sheet.
<!-- guides:end -->

Documentation

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.