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

written-critique

Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.5 KB

SKILL.md(原文)

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

Written Critique

Write feedback someone can act on without asking you to clarify.

How to use

  • /written-critique Apply structured critique format to design reviews in this conversation.

Constraints

Critique Structure

  1. Intent (2-3 sentences): What the design is trying to do. Not what it does. What experience it's trying to create.
  2. What works (2-3 specific decisions): Each with the principle behind it.
  3. What doesn't (1-2 specific decisions): Each with reasoning and the impact on the user.
  4. One change (1 recommendation): The single highest-impact change, framed as a direction not a prescription.

Writing Rules

  • MUST be specific enough that the designer can act without a follow-up conversation
  • MUST separate craft feedback (alignment, consistency) from taste feedback (should this exist at all?)
  • MUST reference observable decisions, not feelings
  • SHOULD be under 300 words. Concise feedback gets read. Novels don't.
  • NEVER rewrite the design in the feedback. Diagnose, don't prescribe.

Anti-Patterns

  • Writing a wall of text with no structure
  • Mixing praise and criticism in the same sentence (pick a lane per observation)
  • Giving feedback on every detail equally (prioritize what matters most)
  • Being so diplomatic the feedback has no edge

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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

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