visual-craft

visual-craft is a cursor rule for Cursor from Oriolshhh/runware-image-mcp. It costs 23 tokens per session (894 once invoked), scanned A, original, MIT.

A set of rules for improving an existing product interface's layout, typography, colors, spacing, imagery, and visual consistency.

In plain words
What is it for?
Use it to define a visual direction, refine hierarchy and composition, preserve important brand elements, and set constraints against low-quality interface patterns.
Why use it?
It helps prevent generic-looking redesigns by tying visual decisions to the product, its users, and the main task.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to define a visual direction, refine hierarchy and composition, preserve important brand elements, and set constraints against low-quality interface patterns.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/oriolshhh/runware-image-mcp/visual-craft
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for visual-craft

README.md
[![agentmods](https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft/github.svg)](https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft)
Your own site
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for visual-craft

Your own site · 80×15
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 894 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00894
Opus 5 $0.00012 $0.00447
Sonnet 5 $0.00005 $0.00179
Haiku 4.5 $0.00002 $0.00089

Measured 6d ago against content hash 26797db4c4be, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

visual-craft scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/visual-craft.mdc · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: visual-craft

Visual Craft

Purpose

Turn an existing interface into a coherent, product-specific visual system without replacing its brand, design system, or usability with fashionable defaults.

This is a concise HarnessKit adaptation informed by the MIT-licensed frontend-ui-engineering skill from addyosmani/agent-skills and baseline-ui from ibelick/ui-skills. Exact provenance is recorded in references/frontend/sources.md.

When to use it

  • When a rendered page or flow needs a material visual redesign.
  • When hierarchy, density, typography, color, spacing, or component treatment feels generic, inconsistent, or recognizably AI-generated.

Instructions

  1. Inspect the real rendered surface, nearby product screens, brand assets, design tokens, components, content, and supported themes. Record what must remain recognizable and what demonstrably fails.
  2. State one visual thesis tied to the product, audience, content, and primary task. Reject any direction that could be transplanted unchanged into an unrelated SaaS product.
  3. Define composition and hierarchy before decoration: reading order, primary action, information density, grouping, alignment, and deliberate asymmetry or emphasis where it serves the task.
  4. Define restrained typography roles with actual families or existing tokens, sizes, weights, line heights, measure, numeric treatment, and responsive behavior. Test real long and short content.
  5. Define semantic color roles for surfaces, text, borders, actions, feedback, selection, and focus. Preserve contrast and non-color cues. Do not default to purple-blue gradients, glass, glow, or a new palette without product evidence.
  6. Use the repository spacing scale. Specify page rhythm, component density, alignment anchors, section transitions, and intentional exceptions. Reject mechanically equal gaps, giant empty bands, and arbitrary one-off values.
  7. Make radius, border, elevation, iconography, imagery, and data visualization form one system. Avoid rounded-container soup, repetitive equal-card grids, random blobs, emoji-as-product-icons, and decorative charts without meaning.
  8. Specify every control's visible hover, active, focus, disabled, pending, success, and error treatment when applicable. Coordinate behavior and motion with ui-state-design, accessible-ui-engineering, and motion-design.
  9. Use real content and honest data. Do not invent testimonials, metrics, product claims, or filler decoration to make the composition look complete.
  10. Compare baseline and proposed/final rendered evidence. Prefer fewer, stronger decisions over adding visual effects until the page feels different.

Read the full file on GitHub · 77 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 77 lines · 23 tokens per session scan A 26797db4c4be

Subscribe to this mod's changes

visual-craft is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 894 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.