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

absence-audit

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.4 KB

SKILL.md(原文)

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

Absence Audit

The hardest things to notice are the things that aren't there.

How to use

  • /absence-audit Apply absence analysis to any design in this conversation.

Constraints

What to Look For

  • MUST list 5-10 things that are conspicuously absent from the design
  • MUST hypothesize for each: intentional removal or never considered?
  • MUST evaluate: does the absence strengthen or weaken the experience?
  • SHOULD note what the absence reveals about the design philosophy

Categories of Absence

  • Missing UI elements (no breadcrumbs, no tooltips, no onboarding tutorial)
  • Missing content (no testimonials, no feature comparison, no pricing)
  • Missing states (no loading skeleton, no empty state, no error recovery)
  • Missing interaction (no animation, no hover effects, no sound)

The Restraint Signal

  • Intentional absence is a strong taste signal. It says "we thought about this and decided it wasn't needed."
  • Accidental absence (missing error states, broken edge cases) signals the opposite.
  • MUST distinguish between the two.

Anti-Patterns

  • Treating every absence as a problem to fix
  • Assuming absence equals minimalism (it might just be incomplete)
  • Missing obvious gaps because you're focused on what IS there

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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

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

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