Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

See all skills by Dragoon0x

Report a problem with this skill