Design Foundations
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.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill design-foundationsgit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/design-foundations ~/.claude/skills/design-foundationsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Design Foundations ## Overview Build structural order from content priority and user tasks. This skill owns relationships and layout logic, then hands token values and domain styling to their canonical owners. ## When to use - Creating a screen or materially restructuring its layout - Repairing inconsistent spacing, weak hierarchy, clutter, or broken grouping - Choosing grid, container, alignment, density, whitespace, or section cadence - Checking whether realistic content destabilizes the composition ## When to skip - Isolated color or theme work → `design-color` - Type selection or type-scale work → `design-typography` - Component states or composition without layout change → `components` - Motion-only or micro-polish changes → `motion` / `polish` ## Ownership | Concern | Owner / handoff | |---|---| | Product emphasis and primary task | `design-direction` sets intent; foundations turns it into focal composition | | Grid, containers, cadence, alignment, grouping, density, whitespace | `design-foundations` | | Spacing and size values | Foundations defines relationships; `tokens` supplies values | | Type roles, scale, wrapping rules | `design-typography` | | Palette and contrast system | `design-color` | | Radius, border, elevation, and surface styling | `design-surfaces` | | Reusable UI behavior and states | `components` | | Breakpoint transformations and device verification | `responsive` | | Optical cleanup after structure is sound | `polish` | ## MUST
Details
- Skill name
design-foundations- Repository
- sukirman1901/frontend-expert
- Path
skills/design-foundations/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Design Foundations skill do?
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.
How do I install the Design Foundations 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 Foundations popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/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.
Anti Slop Code
9sukirman1901/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.
Anti Slop Design
9sukirman1901/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.
Design Surfaces
9sukirman1901/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.
Design Direction
9sukirman1901/frontend-expert
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.
Design Typography
9sukirman1901/frontend-expert
Use when choosing fonts, defining or repairing a type scale, loading webfonts, or fixing text wrapping, truncation, numeric alignment, mixed-direction text, “tipografi”, “font apa”, “teks kepotong”, or “heading berantakan”.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.