Build a dashboard redesign critique framework component with inline annotations and severity tags
Views
2.1K
Copies
628
Likes
314
Comments
0
Copy rate
30.0%
Prompt
Create a single-file React component named CritiqueFramework that presents a structured redesign critique for a [dashboard_type]. Use Tailwind only.
The component must include:
- A header with project name, date, and the reviewer's name
- A critique scorecard (5 criteria: clarity, hierarchy, consistency, density, accessibility) with 1-5 dots each
- A severity legend (low, medium, high, blocking) with consistent dot colors
- A list of numbered issues, each with title, description, severity tag, affected area, and a suggested fix
- An "open questions" section at the bottom with at least 3 items
- A sticky footer action bar with "Approve with changes" and "Request rework" buttons
- All state interactive: severity tags filter the issue list, clicking an issue highlights it
Tone of the content: constructive, specific, framed around user outcomes — not taste. Use [product_focus] as the subject of the critique. The output must be a ready-to-run component.Customise this prompt
Fill in 2 variables to personalise this prompt
Preview
Create a single-file React component named CritiqueFramework that presents a structured redesign critique for a [dashboard_type]. Use Tailwind only.
The component must include:
- A header with project name, date, and the reviewer's name
- A critique scorecard (5 criteria: clarity, hierarchy, consistency, density, accessibility) with 1-5 dots each
- A severity legend (low, medium, high, blocking) with consistent dot colors
- A list of numbered issues, each with title, description, severity tag, affected area, and a suggested fix
- An "open questions" section at the bottom with at least 3 items
- A sticky footer action bar with "Approve with changes" and "Request rework" buttons
- All state interactive: severity tags filter the issue list, clicking an issue highlights it
Tone of the content: constructive, specific, framed around user outcomes — not taste. Use [product_focus] as the subject of the critique. The output must be a ready-to-run component.