frontend-design

frontend-design is a skill for Claude Code, Codex from markerikson/opencode-config-example. It costs 46 tokens per session (1,898 once invoked), scanned A, original, MIT.

A design guide for creating clear, consistent, production-ready frontend interfaces such as dashboards, tools, pages, and web applications.

In plain words
What is it for?
Use it when building frontend screens or components that need a defined design direction, reusable patterns, readable data presentation, and careful visual details.
Why use it?
It helps teams make deliberate choices about layout, visual style, information density, components, accessibility, and technical constraints instead of assembling disconnected interface pieces.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when building frontend screens or components that need a defined design direction, reusable patterns, readable data presentation, and careful visual details.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markerikson/opencode-config-example/frontend-design
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 markerikson/opencode-config-example --skill frontend-design
Clone the repo
git clone --depth 1 https://github.com/markerikson/opencode-config-example

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/frontend-design"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/frontend-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,898 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.00046 $0.01898
Opus 5.5 $0.00018 $0.00759
Sonnet 5.5 $0.00009 $0.00380
Haiku 4.5 $0.00005 $0.00190

Measured 1mo ago against content hash e31793ddf4a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frontend-design 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 1mo 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.

config/skill/frontend-design/SKILL.md · 138 lines

How it starts

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

Adapted from Impeccable by Paul Bakaus (Apache 2.0 license). Modified for dashboard/tool UI: emphasis shifted from bold creative expression to clarity, information density, scanability, and consistent design systems.

This skill guides creation of polished, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with careful attention to design details and intentional choices.

Design Direction

Establish a clear design direction before writing code:

  • Purpose: What problem does this interface solve? Who uses it? What data matters most?
  • Tone: Choose an appropriate aesthetic — refined minimal, utilitarian, editorial, industrial, soft neutral, etc. Match the tone to the tool's purpose. A trading dashboard and a documentation site need very different treatments.
  • Constraints: Technical requirements (framework, performance, accessibility).
  • Consistency: Define a design system early — tokens, patterns, component conventions. Reuse relentlessly. Every one-off choice is technical debt.

CRITICAL: Choose a clear direction and execute it with precision. The key is intentionality: every color, spacing value, and typographic choice should trace back to a deliberate decision, not a default.

Then implement working code that is:

  • Production-grade and functional
  • Visually clear and scannable
  • Cohesive with a consistent design system
  • Meticulously refined in every detail

Frontend Aesthetics Guidelines

Typography

→ Consult typography reference for scales, pairing, and loading strategies.

Choose fonts appropriate to the interface's purpose. For data-heavy tools, readability and numeric clarity matter more than personality.

DO: Use a modular type scale with fluid sizing (clamp) DO: Vary font weights and sizes to create clear visual hierarchy DO: Use font-variant-numeric: tabular-nums for data columns DON'T: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults — unless they genuinely serve the purpose (system fonts are fine for tools) DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes DON'T: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

Read the full file on GitHub · 138 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. 1mo ago First seen · 138 lines · 46 tokens per session scan A e31793ddf4a3

Subscribe to this mod's changes

frontend-design is a skill published in the GitHub repository markerikson/opencode-config-example (48 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 1,898 once invoked, about $0.0002 per session on Opus 5.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-08-30.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

visual-ralph

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

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

glance-canonical-layouts

Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).

android/skills · 56 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens