frontend-design-direction

frontend-design-direction is a skill for Claude Code, Codex from Oriolshhh/runware-image-mcp. It costs 21 tokens per session (523 once invoked), scanned A, original, MIT.

A planning guide for choosing the visual direction of a new user-facing interface. It turns product goals and existing design evidence into guidance for layout, colors, type, spacing, imagery, and motion.

In plain words
What is it for?
Use it before building a new page, screen, or major visual redesign to define hierarchy, responsive behavior, a signature element, and boundaries for the implementation.
Why use it?
It prevents developers from making disconnected visual choices while implementing a screen. It also clarifies which existing brand and interface elements must remain.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it before building a new page, screen, or major visual redesign to define hierarchy, responsive behavior, a signature element, and boundaries for the implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oriolshhh/runware-image-mcp/frontend-design-direction
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.

Any agent
npx skills add Oriolshhh/runware-image-mcp --skill frontend-design-direction
Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Claude Code, Codex.

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 frontend-design-direction

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/frontend-design-direction"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/frontend-design-direction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 523 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.00021 $0.00523
Opus 5 $0.00010 $0.00262
Sonnet 5 $0.00004 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured 7d ago against content hash 050b183d1b37, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

frontend-design-direction 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 7d 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.

.agents/skills/frontend-design-direction/SKILL.md · 50 lines

How it starts

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

Frontend Design Direction

Purpose

Translate product intent and repository evidence into a coherent visual brief an implementer can follow without inventing taste mid-diff.

When to use it

  • Before building a new user-facing surface or materially changing visual language.

Instructions

  1. State the target users, their primary task, the surface, constraints, and the requested degree of change. Ask only questions that alter the direction.
  2. Audit existing brand assets, tokens, components, typography, icons, content, and nearby screens. Label what must be preserved.
  3. If one aesthetic pack is enabled, read it as the primary voice. Do not blend conflicting primary packs; explain which one controls.
  4. Propose one direction, or two only when a real unresolved tradeoff exists.
  5. Define: design principles; information hierarchy; color roles; typography roles; spacing/density; radius/elevation; imagery/iconography; and motion tone.
  6. Sketch key layouts and responsive transitions using compact prose or ASCII.
  7. Name one signature element and justify it from the product—not fashion.
  8. List anti-goals and exact elements of the existing system to reuse.
  9. Review the direction for generic AI defaults, inconsistent personality, content mismatch, accessibility risk, and implementation cost.

Output format

A compact frontend brief: user/job, evidence, preservation constraints, chosen direction, tokens, type roles, layout, responsive behavior, states, signature, anti-goals, reused primitives, risks, and approval needs.

Anti-patterns

  • Designing from an aesthetic adjective without product evidence.
  • Replacing the local design system or brand by default.
  • Presenting many moodboards to avoid making a recommendation.
  • Treating a gradient, oversized heading, card grid, or animation as a concept.

Verification checklist

  • Every major visual choice traces to the brief, content, brand, or repository.
  • The direction covers mobile and desktop, real content, operational states, and accessibility constraints before implementation begins.

Read the full file on GitHub · 50 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. 7d ago First seen · 50 lines · 21 tokens per session scan A 050b183d1b37

Subscribe to this mod's changes

frontend-design-direction is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 523 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.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

reveal-hover-effect

Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…

MengTo/Skills · 66 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens