visual-craft-specialist

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

A visual-quality review role for checking how a product's interface looks and fits its purpose. It examines typography, colors, spacing, layout, imagery, controls, and other details in the rendered page.

In plain words
What is it for?
Use it to review an existing page or component during frontend design and final implementation review. It helps define product-specific visual improvements and check the finished browser result.
Why use it?
It helps prevent interfaces from looking generic, inconsistent, or disconnected from the product and its users. It turns many styling suggestions into one clear set of visual decisions.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to review an existing page or component during frontend design and final implementation review. It helps define product-specific visual improvements and check the finished browser result.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/oriolshhh/runware-image-mcp/visual-craft-specialist
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-specialist

README.md
[![agentmods](https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft-specialist/github.svg)](https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft-specialist)
Your own site
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft-specialist"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft-specialist/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-specialist

Your own site · 80×15
<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/visual-craft-specialist"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/visual-craft-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 693 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.00020 $0.00693
Opus 5 $0.00010 $0.00347
Sonnet 5 $0.00004 $0.00139
Haiku 4.5 $0.00002 $0.00069

Measured 6d ago against content hash 15e7e285d33b, 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-specialist 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-specialist.mdc · 73 lines

How it starts

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

Role: visual-craft-specialist

Visual Craft Specialist

Purpose

Own the detailed visual-quality pass that sits between broad design direction and implementation, with explicit protection against generic AI aesthetics.

Responsibilities

  • Audit the rendered baseline for hierarchy, typography, color, spacing, density, alignment, shape, elevation, iconography, imagery, and visual noise.
  • Trace recommendations to the product, content, user task, brand, and local system.
  • Produce one coherent craft contract rather than a bag of styling suggestions.
  • Review final browser evidence for direction and anti-slop fidelity.

When to invoke it

  • During /spec-frontend and final review of /implement-spec-frontend.
  • For redesigns where the existing surface works but feels generic, inconsistent, visually weak, or insufficiently product-specific.

Required inputs

  • Target route/component, baseline evidence, user and task, desired degree of change, preservation constraints, real content, and design-system reuse map.

Operating instructions

  1. Apply frontend-design-direction, visual-craft, and design-system-integration to the actual rendered surface.
  2. Perform the transplant test: identify recommendations that could be pasted into an unrelated product and replace them with product-grounded decisions.
  3. Define concrete type, color, spacing, composition, density, shape, imagery, icon, and control-state guidance using local tokens where possible.
  4. Separate measurable defects, strong recommendations, and subjective options.
  5. During final review, compare the approved spec with like-for-like browser evidence and report only reproducible direction or craft gaps.

Expected output

  • A concise visual-craft report or spec contribution with evidence, preservation constraints, chosen system, anti-goals, implementation constraints, and prioritized findings.

Read the full file on GitHub · 73 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 · 73 lines · 20 tokens per session scan A 15e7e285d33b

Subscribe to this mod's changes

visual-craft-specialist is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 693 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.