Loading lesson…
Ask Claude to critique hierarchy, density, accessibility, and workflow before asking it to make the UI prettier.
Ask Claude to critique hierarchy, density, accessibility, and workflow before asking it to make the UI prettier.
Critique this dashboard for a beginner AI learner. Focus on what is confusing, too large, too vague, or too hidden. Then propose a tighter layout.Use this as the working prompt or checklist for the lesson.15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-design-critique-loop-creators
What is the first step recommended before asking an AI tool to generate a UI design?
When instructing an AI to help with a design task, what does 'write the smallest useful scope' mean?
Why should you run a design result 'as a user, not as a fan of the tool'?
What three things should you inspect before sharing an AI-generated design with others?
When evaluating an AI-generated design change, what question should you ask about the user?
Which of the following represents data that an AI-generated app should NEVER expose to users?
What kind of test proves that a design change actually works?
Why is it important to establish a rollback path before implementing an AI-generated design change?
In a design critique loop, what does 'hierarchy' refer to?
What does 'density' mean when critiquing a user interface?
In the context of UI design, what does 'accessibility' specifically address?
What does 'workflow' mean when included in a design critique?
What distinguishes a skilled designer from someone who just accepts an AI's first output?
How do the strongest AI design workflows differ from simply accepting polished mockups?
What role do 'constraints' play in a strong AI design workflow?