Design Direction

Senior frontend judgment before building UI — offer 2–3 approaches on distinct design axes (hierarchy, layout, density, interaction, expression) with tradeoffs; max 1–2 clarifying questions; optional inspiration (Linear/Stripe/…). Use at the start of non-trivial UI work and whenever direction is unclear. Skip for obvious bugfixes, single-token tweaks, or “just implement”. Runs before domain skills.

9 stars 1 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sukirman1901/frontend-expert

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sukirman1901/frontend-expert --skill design-direction
Manual install
git clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/design-direction ~/.claude/skills/design-direction

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frontend Judgment

## Overview

Feel like a senior frontend engineer: **decide with the user, then build**. Do not dump a generic UI for blank-canvas work. This skill is a short gate before `tokens` / `components` / etc.

This pack-authored workflow uses independent design-axis analysis; no external exploration tool is bundled.

## When to use (mandatory gate)

Run this **before** domain skills when any of these apply:

- New page, screen, flow, or blank-canvas layout
- Unspecified information architecture / navigation / density
- **Marketing / landing page** without a section recipe → load `marketing` after approaches (or with “langsung saja”)
- Multiple reasonable visual or interaction directions
- User ask is vague for a **new** screen (“bikin dashboard”, “UI modern”) — not mere “rapihin” on existing UI (that’s `polish` / `quality-loop`)

## When to skip

- Clear bugfix with known expected behavior
- Tiny change (one component prop, one token color, copy tweak)
- User already chose a direction or said “langsung saja” / “just implement”
- Pure `/design` audit with no implementation request
- Follow-up turn continuing an already-approved plan
- User only wants micro polish on existing UI (“rapihin detail”, “feels off”) → use `polish`
- User wants iterate until audit-clean (“sampai bagus”) → use `quality-loop`, which may call judgment only on first blank-canvas pass

## Workflow

### 0. Quick context (silent — no questions yet)
Read the full skill on GitHub

Details

Skill name
design-direction
Path
skills/design-direction/SKILL.md
License
MIT
Repo updated
5 November 2026

FAQ

What does the Design Direction skill do?

Senior frontend judgment before building UI — offer 2–3 approaches on distinct design axes (hierarchy, layout, density, interaction, expression) with tradeoffs; max 1–2 clarifying questions; optional inspiration (Linear/Stripe/…). Use at the start of non-trivial UI work and whenever direction is unclear. Skip for obvious bugfixes, single-token tweaks, or “just implement”. Runs before domain skills.

How do I install the Design Direction skill?

Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Design Direction popular?

It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.

Related skills

Accessibility

9

sukirman1901/frontend-expert

Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.

Frontend & Design

Anti Slop Code

9

sukirman1901/frontend-expert

Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.

Software Development

Anti Slop Design

9

sukirman1901/frontend-expert

Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.

Frontend & Design

Design Foundations

9

sukirman1901/frontend-expert

Use when creating or repairing the structural layout of a web screen: grid, spacing rhythm, alignment, hierarchy, density, composition, whitespace, or content grouping. Trigger for blank layouts, inconsistent spacing, weak hierarchy, cluttered screens, "layout terasa berantakan", "struktur layout", or "rapikan struktur". Skip isolated color, typography, component-state, motion, and micro-polish changes.

Frontend & Design

Design Color

9

sukirman1901/frontend-expert

Use when creating or repairing a palette, semantic color roles, OKLCH scales, dark mode, contrast pairs, gamut fallbacks, “buat palet”, “warna brand”, “dark theme”, or color that must measurably pass accessibility requirements.

Frontend & Design

Design Surfaces

9

sukirman1901/frontend-expert

Use when styling cards, dialogs, modals, panels, borders, shadows, elevation, overlays, nested radii, “radius terasa aneh”, “shadow kasar”, or surfaces that lose hierarchy between light and dark themes.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.