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

hierarchy-principles

Visual weight, attention order, and the decisions that guide the eye. Use when building layouts, evaluating information architecture, or diagnosing why a design feels confusing.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.8 KB

SKILL.md(原文)

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

Hierarchy Principles

The single most important thing in any visual design.

How to use

  • /hierarchy-principles Apply hierarchy constraints to any design work in this conversation.

Constraints

Hierarchy Rules

  • MUST establish a clear primary element on every screen. If everything is important, nothing is.
  • MUST create hierarchy through at least two of: scale, weight, contrast, color, space, position
  • MUST ensure visual weight matches content priority (the most important thing is the most prominent)
  • NEVER allow two elements to compete at the same hierarchy level unless intentional tension is the goal
  • SHOULD test by covering half the screen. Can you still tell what's most important?

Hierarchy Tools

  • Scale: Bigger things get seen first. The ratio between largest and smallest defines your range.
  • Weight: Bolder things demand attention. Use sparingly or nothing stands out.
  • Contrast: High-contrast elements pull focus. Low-contrast recedes.
  • Color: Saturated colors advance. Desaturated retreat. One accent in a neutral system creates instant hierarchy.
  • Space: More breathing room signals more importance. Crowded elements feel like metadata.
  • Position: Top-left gets seen first (LTR). Center gets attention. Bottom-right gets ignored unless hierarchy pulls the eye there.

Anti-Patterns

  • Using size as the only hierarchy tool (creates monotonous layouts)
  • Making everything bold (negates the purpose of bold)
  • Competing calls-to-action on the same screen
  • Navigation that's visually louder than the content it serves

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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