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

craft-signals

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.8 KB

SKILL.md(原文)

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

Craft Signals

The details that separate 'designed' from 'well-designed.'

How to use

  • /craft-signals Apply craft quality constraints to this conversation.

Constraints

Consistency Checks

  • MUST ensure consistent border radii from the same scale (4, 8, 12, 16, not 4 here and 5 there)
  • MUST ensure alignment is pixel-perfect where intended. Near-alignment looks worse than deliberate offset.
  • MUST ensure the same component looks and behaves the same everywhere it appears
  • SHOULD ensure transitions share the same easing curve and follow a proportional duration scale

State Coverage

  • MUST cover all states: loading, empty, error, success, partial, overflow, truncation
  • MUST design each state intentionally, not rely on browser defaults
  • SHOULD ensure error messages are specific and actionable, not generic
  • SHOULD ensure loading states give spatial hints about what's coming (skeletons over spinners)

Transition Quality

  • Feedback transitions (button press, toggle): 50-150ms, nearly instant
  • Navigation transitions (page change, panel open): 200-400ms, noticeable but fast
  • Emphasis transitions (notification, celebration): 300-600ms, deliberate
  • NEVER let animation block content. If you have to wait for an animation to finish before reading, it's a bug.

Anti-Patterns

  • Inconsistent radii across component types
  • Loading states that last longer than the actual load
  • Error states that say "something went wrong" with no guidance
  • Hover effects on every element (motion should guide attention, not create noise)

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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

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

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