UX Coaching
Review "$ARGUMENTS" through the lens of a senior UX/UI designer. Provide mentorship feedback on usability, visual hierarchy, readability, and adherence to UX principles.
Arguments. $ARGUMENTS may contain the project name and optional flags. Derive <project> from the argument by taking its basename without extension and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"coaching-ux","workflow":"coaching","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill that can run anytime.
Process
Read the target:
- Read the file, component, or design artifact specified in "$ARGUMENTS"
- If it's a design artifact (from
.singularskills/design/), read the full context
- If it's code, focus on the UI/UX aspects (layout, interaction, feedback)
Read reference material:
- Read
references/ux-laws.md for UX principles
- Read
references/feedback-format.md for output structure
Evaluate against UX principles:
- Fitts's Law: Are important targets appropriately sized and positioned?
- Hick's Law: Are choices minimized? Is progressive disclosure used?
- Jakob's Law: Does it follow established conventions?
- Miller's Law: Is information chunked appropriately?
- Gestalt principles: Are grouping, proximity, and similarity used effectively?
- Visual hierarchy: Is importance conveyed through size, color, position, whitespace?
- Readability/legibility: Line length, contrast, typography, scannability
- Cognitive load: Is extraneous complexity minimized?
- Information architecture: Is navigation logical and labeling clear?
Write the coaching report to .singularskills/coaching/<project>/ux-review.md following the feedback format.
Output
The UX coaching report written to .singularskills/coaching/<project>/ux-review.md. Present the score and top 3 suggestions to the user.
1---2name: coaching-ux3description: Review a screen, component or design as a senior UX/UI designer — UX laws, Gestalt grouping, visual hierarchy, readability, cognitive load and navigation — in a scored coaching report. Use when the user wants feedback on how usable and clear their interface or design artifact is.4metadata:5 source: https://skillmd.com/skills/bromso/coaching-ux6 argument-hint: "<file-or-topic> [--skip-checks]"7---89# UX Coaching1011Review "$ARGUMENTS" through the lens of a senior UX/UI designer. Provide mentorship feedback on usability, visual hierarchy, readability, and adherence to UX principles.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Derive `<project>` from the argument by taking its basename without extension and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"coaching-ux","workflow":"coaching","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Prerequisites1617None — this is a utility skill that can run anytime.1819## Process20211. **Read the target:**22 - Read the file, component, or design artifact specified in "$ARGUMENTS"23 - If it's a design artifact (from `.singularskills/design/`), read the full context24 - If it's code, focus on the UI/UX aspects (layout, interaction, feedback)25262. **Read reference material:**27 - Read `references/ux-laws.md` for UX principles28 - Read `references/feedback-format.md` for output structure29303. **Evaluate against UX principles:**31 - **Fitts's Law:** Are important targets appropriately sized and positioned?32 - **Hick's Law:** Are choices minimized? Is progressive disclosure used?33 - **Jakob's Law:** Does it follow established conventions?34 - **Miller's Law:** Is information chunked appropriately?35 - **Gestalt principles:** Are grouping, proximity, and similarity used effectively?36 - **Visual hierarchy:** Is importance conveyed through size, color, position, whitespace?37 - **Readability/legibility:** Line length, contrast, typography, scannability38 - **Cognitive load:** Is extraneous complexity minimized?39 - **Information architecture:** Is navigation logical and labeling clear?40414. **Write the coaching report** to `.singularskills/coaching/<project>/ux-review.md` following the feedback format.4243## Output4445The UX coaching report written to `.singularskills/coaching/<project>/ux-review.md`. Present the score and top 3 suggestions to the user.