agentleFS
adymireadymire/CraftLayer/skills/visual-design/SKILL.md

visual-design

Skill0 starsChanged 3 days agoMITView on GitHub

Establish visual hierarchy, typography, color, composition, and imagery that support a product's purpose and brand.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Use when shaping the visual direction of a screen, resolving hierarchy problems, or reviewing typography, color, spacing, imagery, and …

    line 10
  2. Distinctive:

    Do not treat personal taste as objective evidence or add visual effects to compensate for unclear content and product positioning.

    line 15
  3. Distinctive:

    Use a spacing and alignment rhythm appropriate to the content density.

    line 28
  4. Distinctive:

    Use surfaces, borders, shadows, and effects sparingly to separate meaningful layers.

    line 31
  5. Distinctive:

    Use a limited, intentional type system.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Visual Design

When to use

Use when shaping the visual direction of a screen, resolving hierarchy problems, or reviewing typography, color, spacing, imagery, and surfaces.

When not to use

Do not treat personal taste as objective evidence or add visual effects to compensate for unclear content and product positioning.

Inputs and assumptions

Inspect the audience, purpose, content, brand, current tokens, viewport, platform, and any existing visual conventions.

Workflow

  1. Identify the primary message and action, then order supporting content.
  2. Set type roles and readable line lengths before styling individual elements.
  3. Use a spacing and alignment rhythm appropriate to the content density.
  4. Choose colors by semantic role and verify contrast in rendered states.
  5. Select imagery and iconography that clarify the story or task.
  6. Use surfaces, borders, shadows, and effects sparingly to separate meaningful layers.
  7. Review hierarchy at realistic sizes and in high/low content cases.

Decision rules

  • One clear visual entry point is more useful than competing accents.
  • Use a limited, intentional type system; avoid novelty at the expense of readability.
  • Whitespace should group, separate, or focus content.
  • Decorative graphics must not obscure content or imply unsupported facts.

Example

For an editorial article, prioritize a readable text measure, clear title and metadata hierarchy, and consistent image captions; a dense dashboard layout is not a suitable default.

Common failures

  • Changing fonts and colors without improving hierarchy.
  • Low-contrast muted text and tiny interactive targets.
  • Random spacing and inconsistent icon weight.

Validation

Review hierarchy, legibility, contrast, content alignment, visual consistency, and behavior at target viewport widths.

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.