Design Typography
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”.
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-typographygit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/design-typography ~/.claude/skills/design-typographyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Design Typography ## Overview Typography is a role system verified with real content, not a fashionable font choice. Preserve project fonts first; change them only when the task requires it. ## When to use - Font selection, type roles, scales, hierarchy, or webfont loading - Poor wrapping, truncation, measure, line-height, or numeric jitter - Variable fonts, OpenType, localization, language, or bidi rendering ## When to skip - Copy meaning or tone only → `content-design` - Heading semantics only → `accessibility` - Palette or surface styling only ## MUST | Rule | Detail | |---|---| | **Recon first** | Inspect project fonts, tokens, content roles, languages, and rendered lengths | | **Role-based system** | Use semantic roles; do not scatter unrelated sizes and weights | | **Content safety** | Meaningful truncated text remains reachable | | **Language-aware** | Set language/direction boundaries and test text expansion | | **Evidence labels** | Numeric recipes are recommendations unless a standard/project owns them | | **Rendered proof** | Verify realistic content at supported widths and zoom | ## Workflow 1. **Inventory** — font files, fallbacks, tokens, roles, languages, and failure cases. 2. **Choose** — keep the system or propose alternatives with licensing/loading tradeoffs. 3. **Systematize** — map roles to a restrained scale, weights, leading, measure, and features. 4. **Harden** — wrapping, long IDs, truncation recovery, numerics, fallback and bidi.
Details
- Skill name
design-typography- Repository
- sukirman1901/frontend-expert
- Path
skills/design-typography/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Design Typography skill do?
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”.
How do I install the Design Typography 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 Typography 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 Vocabulary
9sukirman1901/frontend-expert
Name a design or UI concept from a loose description. Reverse-lookup for design terms — user describes something vaguely ("card floating over blur", "zig-zag layout"), skill returns the proper name + brief definition. Use when the user uses informal language for a UI concept, or when you need the correct term to search references or communicate precisely.
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.
Devtools
9sukirman1901/frontend-expert
Frontend DevTools audit workflow — Lighthouse/CWV, a11y (axe), network/layout, when checks are MUST vs optional. Use for /test-ui deep passes, "audit performance", "cek Lighthouse", "axe", or verifying UI before ship with tooling evidence.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.