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

color-systems

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.8 KB

SKILL.md(原文)

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

Color Systems

Fewer colors, more discipline. Every color earns its place.

How to use

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

Constraints

Palette Roles

  • MUST assign every color a clear role: structural (backgrounds, borders), semantic (error, success, warning), accent (primary action, emphasis), or decorative
  • MUST ensure semantic colors are consistent everywhere (red always means the same thing)
  • MUST keep neutrals doing 80-90% of the heavy lifting. Color is the accent, not the foundation.
  • NEVER use the same color for conflicting purposes (red as both "featured" and "error")

Restraint Rules

  • A 2-3 color palette used with intention always outperforms a 7-color palette used without thought
  • MUST evaluate: can any color be removed without losing information?
  • SHOULD start with one accent color and add more only when the single accent can't carry the semantic load
  • NEVER add a color because "it needs more color." Add a color because the information requires it.

Relationships Over Swatches

  • MUST evaluate colors in context, not in isolation (the same blue looks different next to warm gray vs. cool white)
  • MUST check contrast ratios for accessibility (WCAG AA minimum)
  • SHOULD evaluate how the palette works across light and dark modes

Anti-Patterns

  • Picking colors from a trend palette without evaluating fit
  • Using color as the primary hierarchy tool (color should reinforce hierarchy, not create it alone)
  • Decorative gradients that don't serve information or brand
  • Different accent colors on different pages with no system behind the variation

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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日 更新

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日 更新

Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.

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

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

Dragoon0x のスキルをすべて見る

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