本文へ移動
cccskills
無料GitHub で公開

type-systems

Scale, weight, line height, and tracking as a coherent system. Use when building type scales, auditing typography consistency, or diagnosing why text feels off.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Type Systems

Typography is a system. Every decision should be intentional and connected.

How to use

  • /type-systems Apply type system constraints to this conversation.

Constraints

Scale

  • MUST use a mathematical ratio for the type scale (1.25, 1.333, 1.5 between sizes)
  • Wide range (12px to 72px): dramatic hierarchy, suits editorial and marketing
  • Narrow range (14px to 24px): subtle hierarchy, suits dense products
  • NEVER use random sizes. If it's not on the scale, it shouldn't exist.
  • MUST limit to 4-6 sizes per screen maximum with clear justification for each

Weight

  • 1-2 weights: discipline. Hierarchy comes from scale and space, not weight.
  • 3 weights: normal range. Regular body, medium emphasis, bold headlines.
  • 4+ weights: either the system demands it or you haven't made a decision.
  • MUST ensure each weight serves a distinct, named purpose

Line Height

  • Body text: 1.5-1.7x font size. Where readability lives.
  • Headlines: 1.1-1.3x. Large text has built-in breathing room.
  • UI labels: 1.2-1.4x. Compact but not crushed.
  • NEVER use the same line height for all text sizes

Letter Spacing

  • Body text: leave it alone. The type designer already optimized it.
  • All-caps labels: add 2-5% tracking. Capitals need air.
  • Large display text (72px+): sometimes benefits from tightening.

Anti-Patterns

  • More than 3 type sizes on a single screen without clear hierarchy justification
  • Centering paragraphs longer than 3 lines
  • Lines over 75 characters wide (hurts readability)
  • Inconsistent weight usage with no system behind it

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.

日本語の概要は準備中です。原文の説明を表示しています。

Dragoon0x/taste-skills62026年2月27日 更新

Dragoon0x のスキルをすべて見る

このスキルの問題を報告する