educlopez/ui-craft

typeset

Typography pass covering font choice, modular scale, tracking, leading, weight hierarchy, and micro-typography details.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/educlopez/ui-craft --skill typeset

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Typeset the UI at $ARGUMENTS. Load the ui-craft skill and read references/typography.md.

Note: typeset is knob-agnostic — typography rules (no ALL CAPS on headings, tracking-tight ≥24px, one body font, etc.) are not tunable.

Apply, in order:

  1. Font inventory — what's loaded? If Inter is the default choice with no reason, ask before accepting it (Inter is the #1 AI-tell). Good alternatives: Geist, DM Sans, Plus Jakarta Sans, system stack. One body font, optionally one display font. Never three.
  1. Scale — is there a scale or are sizes ad hoc? Anchor to a modular scale (1.125 / 1.2 / 1.25). Sizes: 12 / 14 / 16 / 20 / 24 / 32 / 48 / 64 / 72. No 13px / 15px / 17px one-offs unless optical.
  1. Tracking (letter-spacing):
  • ≥ 24px → tracking-tight (-0.02em) or tighter for 40px+
  • 14-20px body → default
  • 11-13px category labels → tracking-wide (+0.06em) + uppercase IS allowed here (the one exception)
  • Never ALL CAPS on headings, nav, buttons, tables
  1. Leading (line-height):
  • Headings: 1.05-1.15
  • Body: 1.5-1.65
  • UI (buttons, labels): 1.2-1.3
  1. Weight hierarchy — pick 2-3 weights max. Common: 400 body, 500 UI/labels, 600-700 headings. Never load 9 weights "just in case".
  1. Micro-typography (the compound details):
  • tabular-nums on every number you align (tables, stats, timestamps, prices)
  • text-wrap: balance on headlines, text-wrap: pretty on body
  • Curly quotes (' / "), em dashes (—), en dashes (–), no double hyphens
  • &nbsp; in brand names, between number + unit, and before final short words in headlines
  • Real apostrophes in contractions
  • font-feature-settings or font-variant-* for opt-in features (ligatures, ss01, fractions)
  • Straight prime marks (′, ″) for units, not quotes
  1. Hierarchy check — can you tell primary / secondary / tertiary at a glance? If every line has the same weight or size, collapse or amplify.

Amplifying hierarchy

If the UI is technically correct but forgettable, use typography as the weapon. Pick ONE element to carry signature (never two); boldness is typography, not color or decoration:

  1. Hero headline — push size to 80-120px, weight to 700-800, tracking to -0.04em. Tight leading (0.95-1.0).
  2. Hierarchy jump — widen the gap between H1 and body. If H1 is 32px and body is 16px, the UI is whispering; if H1 is 48px+, the ratio reads. Compress or expand the range deliberately.
  3. Micro-motif — one custom detail that repeats: a hand-drawn underline, numeric counters (01, 02), an asymmetric supporting element, a distinctive list marker.

Knob gating for amplification (CRAFT_LEVEL):

  • ≤ 4 — skip. Boldness is a craft layer, not a baseline.
  • 5-7 — apply the type amplification only. No signature motif unless asked.
  • 8+ — type amplification + one signature detail (chosen at /craft first pass per references/craft-intent.md; /polish and /bolder strengthen it — never stack a second).

Pre-check: if an accent is already overused or hierarchy is already loud, you don't have a tameness problem — you have a noise problem. Route to /distill (cut) or /colorize (reduce accents) instead.

Output: edit code directly. Print the Review Format table. Call out the single highest-impact change (usually: "font choice" or "tracking-tight on hero").

Next step: /polish — micro-details land best right after the type system is set (rung 1).

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
educlopez
コミュニティ

ui-craft

Use for UI design and implementation work to avoid generic AI-looking interfaces. Provides anti-slop rules, a required discovery phase before coding, and guidance for layout, typography, color, motion, accessibility, dashboards, tables, landing pages, theming, and polish. Trigger when editing UI code or reviewing and refining components, pages, screens, layouts, animations, responsive behavior, or design systems.

1時間の導入数
2
GitHub Stars
450
更新日
11月6日
educlopez
コミュニティ

ui-craft-dense-dashboard

Dense dashboard / admin / Bloomberg / Retool / data-heavy internal tools. Locked knobs: CRAFT=7, MOTION=3, DENSITY=9. IBM Plex + mono numbers, semantic palette, 4/8px grid, sparklines, tabular-nums. Trigger on: dashboard, admin panel, data-dense, analytics, Bloomberg-like, Retool-like.

1時間の導入数
2
GitHub Stars
450
更新日
11月6日
educlopez
コミュニティ

adapt

Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says \"make it responsive\" / \"fix mobile layout\". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work.

1時間の導入数
1
GitHub Stars
394
更新日
10月19日
educlopez
コミュニティ

animate

Motion design pass — adds purposeful animations or removes excessive ones, respecting MOTIONINTENSITY and the project's animation stack. Use when the user asks to add animation, \"make it feel smoother\", fix janky transitions, or trim motion that's distracting. Invoke when the user asks for animate on their UI, or mentions 'animate' alongside design / UI / frontend work.

1時間の導入数
1
GitHub Stars
394
更新日
10月19日