Agent skill

Frontend Design

by tobihagemann in tobihagemann/turbo

Create distinctive, production-grade frontend interfaces with high design quality.

MITAuto-check passedFrontend & Design

Install Frontend Design

skills CLI
$ npx skills add tobihagemann/turbo --skill frontend-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tobihagemann/turbo frontend-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/frontend-design .claude/skills/frontend-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frontend-design
GitHub stars
408
Token cost
~2.4k tokens
SKILL.md length
1,293 words
Files
1
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Create distinctive, production-grade frontend interfaces with high design quality.

  • Works in 4 steps: Hero: brand or product, promise, CTA,… → Support: one concrete feature, offer, or… → Detail: atmosphere, workflow, product… → …
  • The user asks to build landing pages
  • SKILL.md covers Design Thinking, Beautiful Defaults, Aesthetics and Motion, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frontend Design is an agent skill from tobihagemann/turbo. Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Landing pages, Frontend development and Design review and critique. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.

When your agent uses it

  • The user asks to build landing pages
  • Any frontend UI

Example prompts

  • “/frontend-design”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Hero: brand or product, promise, CTA, and one dominant visual
  2. Support: one concrete feature, offer, or proof point
  3. Detail: atmosphere, workflow, product depth, or story
  4. Final CTA: convert, start, visit, or contact

What it can do on your machine

Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontend Design loads about 2.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 1,293 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 1,293 words, ~2,357 tokens.

Download SKILL.mdSave it as .claude/skills/frontend-design/SKILL.md (or your agent's skills folder).
name
frontend-design
description
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.

Frontend Design

Create distinctive, production-grade frontend interfaces that feel deliberate, premium, and current. Implement real working code with exceptional attention to aesthetic details and creative choices.

Design Thinking

Before coding, understand the context and commit to a clear aesthetic direction.

Output three things as text before coding:

  • Visual thesis: one sentence describing mood, material, and energy (e.g., "brutally minimal dark interface with surgical precision" or "high-contrast editorial magazine feel with oversized serif headlines")
  • Content plan: the sections in order (hero, support, detail, final CTA for a marketing page; the working surface first for product UI)
  • Interaction thesis: 2-3 motion ideas that change the feel of the page

For each, consider:

  • Purpose: What problem does this interface solve? Who uses it?
  • Tone: Pick a direction and commit. Brutally minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft pastel, industrial. These are starting points; design one true to the vision.
  • Constraints: Framework, performance, accessibility requirements.
  • Differentiation: What makes this unforgettable? What's the one thing someone remembers?

Match ambition to context. A brand landing page warrants bold, expressive choices. A dashboard warrants calm restraint. Both require intentionality.

Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is production-grade, visually striking, cohesive, and meticulously refined.

Beautiful Defaults

  • Start with composition, not components.
  • Prefer a full-bleed hero or full-canvas visual anchor.
  • Make the brand or product name the loudest text.
  • Keep copy short enough to scan in seconds.
  • Use whitespace, alignment, scale, cropping, and contrast before adding chrome.
  • Limit the system: two typefaces max, one accent color by default.
  • Default to cardless layouts. Use sections, columns, dividers, lists, and media blocks instead.
  • Treat the first viewport as a poster, not a document.
  • Each section gets one job, one dominant visual idea, and one primary takeaway or action.

Aesthetics

Typography

Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font. Avoid generic fonts like Arial, Inter, Roboto, and system defaults. Never converge on common AI-favorite choices (Space Grotesk, for example) across generations.

Color and Theme

Commit to a cohesive palette. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. One accent color unless the product already has a strong system.

Spatial Composition

Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. Match the spatial approach to the visual thesis.

Backgrounds and Visual Details

Create atmosphere and depth rather than defaulting to solid colors. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays. Match effects to the overall aesthetic.

Motion

Use motion to create presence and hierarchy, not noise.

Ship at least 2-3 intentional motions for visually led work:

  • One entrance sequence in the hero (staggered reveals with animation-delay create more delight than scattered micro-interactions)
  • One scroll-linked, sticky, or depth effect
  • One hover, reveal, or layout transition that sharpens affordance

Prefer CSS-only solutions for plain HTML. Use Framer Motion when available in React for section reveals, shared layout transitions, scroll-linked shifts, sticky storytelling, and presence effects.

Motion rules:

  • Noticeable in a quick recording
  • Smooth on mobile
  • Fast and restrained
  • Consistent across the page
  • Removed if ornamental only
  • Wrapped in @media (prefers-reduced-motion: no-preference) to respect accessibility settings

Landing Pages

Default sequence:

  1. Hero: brand or product, promise, CTA, and one dominant visual
  2. Support: one concrete feature, offer, or proof point
  3. Detail: atmosphere, workflow, product depth, or story
  4. Final CTA: convert, start, visit, or contact

Hero rules:

  • One composition only. Full-bleed image or dominant visual plane.
  • On branded landing pages, the hero runs edge-to-edge with no inherited page gutters or shared max-width. Constrain only the inner text/action column.
  • Brand first, headline second, body third, CTA fourth.
  • No hero cards, stat strips, logo clouds, pill soup, or floating dashboards by default.
  • Keep headlines to roughly 2-3 lines on desktop, readable in one glance on mobile.
  • Keep the text column narrow and anchored to a calm area of the image.
  • All text over imagery must maintain strong contrast and clear tap targets.

If the first viewport still works after removing the image, the image is too weak. If the brand disappears after hiding the nav, the hierarchy is too weak.

Viewport budget: if the first screen includes a sticky/fixed header, that header counts against the hero. The combined header + hero content must fit within the initial viewport. When using 100vh/100svh heroes, subtract persistent UI chrome or overlay the header.

Show full SKILL.md (550 more words)Show less

App UI

Default to calm, dense restraint:

  • Strong typography and spacing
  • Few colors
  • Dense but readable information
  • Minimal chrome
  • Cards only when the card is the interaction

Organize around: primary workspace, navigation, secondary context or inspector, one clear accent for action or state.

Avoid: dashboard-card mosaics, thick borders on every region, decorative gradients behind routine product UI, multiple competing accent colors, ornamental icons that do not improve scanning.

If a panel can become plain layout without losing meaning, remove the card treatment.

Utility Copy for Product UI

On dashboards, admin tools, and operational workspaces, default to utility copy over marketing copy.

  • Prioritize orientation, status, and action over promise, mood, or brand voice.
  • Start with the working surface itself: KPIs, charts, filters, tables, status. No hero section unless explicitly requested.
  • Section headings should say what the area is or what the user can do there.
  • If a sentence could appear in a homepage hero or ad, rewrite it until it sounds like product UI.
  • If a section does not help someone operate, monitor, or decide, remove it.

Imagery

Imagery must do narrative work.

  • Use at least one strong, real-looking image for brands, venues, editorial pages, and lifestyle products.
  • Prefer in-situ photography over abstract gradients for hero anchors.
  • Choose or crop images with a stable tonal area for text.
  • Do not use images with embedded signage, logos, or typographic clutter fighting the UI.
  • If multiple moments are needed, use multiple images, not one collage.

The first viewport needs a real visual anchor. Decorative texture alone is not enough for landing pages (though textures and atmospheric effects work well as supporting elements throughout).

Copy

  • Let the headline carry the meaning.
  • Supporting copy: one short sentence.
  • Cut repetition between sections.
  • Do not include prompt language or design commentary in the UI.
  • Give every section one responsibility: explain, prove, deepen, or convert.
  • If deleting 30 percent of the copy improves the page, keep deleting.

Anti-Patterns

Never use generic AI-generated aesthetics:

  • Overused font families (Inter, Roboto, Arial, system fonts)
  • Cliched color schemes (particularly purple gradients on white backgrounds)
  • Cream or off-white page backgrounds
  • Italic accent words inside headings
  • Numbered section labels ("01 / 02 / 03")
  • Monospace labels
  • Pill-shaped buttons

Reject these failures:

  • Generic SaaS card grid as the first impression
  • Beautiful image with weak brand presence
  • Strong headline with no clear action
  • Busy imagery behind text
  • Sections that repeat the same mood statement
  • Carousel with no narrative purpose
  • App UI made of stacked cards instead of layout
  • Split-screen hero where text isn't on a calm, unified side
  • Filler copy or sections that need many tiny UI devices to explain themselves

Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics. No two designs should feel the same.

Litmus Checks

Before delivering, verify:

  • Is the brand or product unmistakable in the first screen?
  • Is there one strong visual anchor?
  • Can the page be understood by scanning headlines only?
  • Does each section have one job?
  • Are cards actually necessary?
  • Does motion improve hierarchy or atmosphere?
  • Would the design still feel premium if all decorative shadows were removed?
  • Would any styling choice carry over unchanged to an unrelated design without the visual thesis calling for it? Name it and replace it with one the thesis calls for.

© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in codex/skills/frontend-design of tobihagemann/turbo.

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Frontend Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frontend Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend Design this skilltobihagemann/turbo408—~2.4kAutomated safety check: PassMIT
Frontend Designudecode/plate17k—~3.6kAutomated safety check: PassCustom licence
Frontend DesignYYH211/Claude-meta-skill2821 repos~2.2kAutomated safety check: PassMIT
Frontend DesignJetBrains/skills366129 repos~1.2kAutomated safety check: PassApache-2.0
Designericrisco/rsc-harness180—~6.6kAutomated safety check: PassMIT
Frontend Designmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Frontend Design

    udecode/plate

    Build web interfaces with genuine design quality, not AI slop.

    17k GitHub stars~3.6k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Frontend Design

    YYH211/Claude-meta-skill

    Creates unique, production-grade frontend interfaces with exceptional design quality.

    282 GitHub starsUsed in 1 repo~2.2k tokens
    Frontend & DesignAuto-check passed
  • Frontend Design

    JetBrains/skills

    Official

    Create distinctive, production-grade frontend interfaces with high design quality.

    366 GitHub starsUsed in 129 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Design

    ericrisco/rsc-harness

    A skill your agent uses when designing or refreshing a web UI or landing page — visual concept, type/color/spacing/motion tokens, composition, rescuing a UI that reads AI-generic, or a graded design…

    180 GitHub stars~6.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Frontend Design

    mohitagw15856/pm-claude-skills

    Produce frontend UI that actually looks designed — a working spacing/type system, deliberate color use, real states, and restraint — instead of the generic AI-generated interface.

    1.4k GitHub stars~1.4k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Design Style

    Castor6/tactus

    A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.

    376 GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed

More from tobihagemann/turbo

All 81 skills in this repo
  • Consult Oracle

    tobihagemann/turbo

    Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.

    408 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Fetch PR Comments

    tobihagemann/turbo

    Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.

    408 GitHub stars~967 tokensUpdated yesterday
    Auto-check passed
  • Recall Rationale

    tobihagemann/turbo

    Recall why a past change was made by locating the Claude Code transcript that produced it.

    408 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed
  • Assess Technical Debt

    tobihagemann/turbo

    Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.

    408 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Questions about Frontend Design

What does Frontend Design do?

Create distinctive, production-grade frontend interfaces with high design quality. Frontend Design is an agent skill from tobihagemann/turbo. Create distinctive, production-grade frontend interfaces with high design quality.

When should I use Frontend Design?

Frontend Design fits situations like: the user asks to build landing pages; any frontend UI.

How do I install Frontend Design in Claude Code?

Run `npx skills add tobihagemann/turbo --skill frontend-design -a claude-code`. Or copy the skill folder (codex/skills/frontend-design in tobihagemann/turbo) into .claude/skills/frontend-design in your project. Claude Code loads it when a task matches its description.

How do I install Frontend Design in Codex?

Run `npx skills add tobihagemann/turbo --skill frontend-design -a codex`. Or copy the skill folder (codex/skills/frontend-design in tobihagemann/turbo) into .agents/skills/frontend-design in your project. Codex loads it when a task matches its description.

Can I use Frontend Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill frontend-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-design, .gemini/skills/frontend-design, .github/skills/frontend-design and .opencode/skills/frontend-design in your project.

What does Frontend Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Frontend Design is instructions for the agent only.

Does Frontend Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Frontend Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frontend Design use?

Frontend Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frontend Design use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Frontend Design?

Skills that share tags, products or a category with Frontend Design: Frontend Design (udecode/plate, 17k stars), Frontend Design (YYH211/Claude-meta-skill, 282 stars), Frontend Design (JetBrains/skills, 366 stars) and Design (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend Design?

tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.

Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.