agentsclimarketplace

Visual style bible

Skill newmindsgroup/ai-agent-skills-library/dist/skills/visual-style-bible

Use when the user wants visual system direction, visual language, page aesthetic guidance, UI polish, spacing system decisions, typography system rules, motion system rules, design direction, or a house standard for web or app surfaces. Also use before high-value UI generation, critique, or design review when the work should follow opinionated visual defaults instead of generic UI patterns.From its SKILL.md

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill visual-style-bible

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 282 tokens by cl100k_base, as published. Nobody here has run it

Visual Style Bible

Use this skill as the default visual governor for UI, web, and marketing surfaces.

Read First

  • /Users/newmindsgroup/.codex/knowledge/visual-core/typography-rules.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/spacing-radius-elevation.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/color-usage-rules.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/component-composition-rules.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/motion-rules.md
  • /Users/newmindsgroup/.codex/knowledge/visual-core/avoid-patterns.md

Purpose

  • define the house visual defaults
  • keep design work coherent across screens and pages
  • prevent fallback to generic SaaS UI patterns

Workflow

  1. Decide whether the task is system direction, critique, or implementation guidance.
  2. Apply the visual-core rules most relevant to the surface.
  3. Call out anti-patterns early.
  4. Route system-level questions to design-system when broader governance is needed.

Outputs

  • visual direction packet
  • critique notes
  • house-style recommendations

Guardrails

  • hierarchy before decoration
  • reuse before novelty
  • motion should support meaning

What ships with it: 1 file

222 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,614. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.