🎨 Palette: Improve Welcome screen command visibility#239
🎨 Palette: Improve Welcome screen command visibility#239AhmmedSamier merged 2 commits intomasterfrom
Conversation
In accordance with UX findings (Palette journal), Welcome items in the QuickPick UI now display the primary interaction trigger (the command itself, like `/all`) in the `description` field rather than in parentheses within the `label`. This makes the command more visible and scanable, while retaining the explanation and shortcut in the `detail` field. Co-authored-by: AhmmedSamier <17784876+AhmmedSamier@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
In accordance with UX findings (Palette journal), Welcome items in the QuickPick UI now display the primary interaction trigger (the command itself, like `/all`) in the `description` field rather than in parentheses within the `label`. This makes the command more visible and scanable, while retaining the explanation and shortcut in the `detail` field. Co-authored-by: AhmmedSamier <17784876+AhmmedSamier@users.noreply.github.com>
💡 What: Moved the slash command trigger (e.g.,
/all) from thelabelto thedescriptionfield for Welcome items in the QuickPick UI. The explanation and keyboard shortcut remain in thedetailfield.🎯 Why: To improve the visibility and scanability of the primary interaction trigger. Putting it in the
descriptionfield uses VS Code's native visual hierarchy (right-aligned, muted color) to separate the friendly name from the technical command, reducing cognitive load.📸 Before/After: N/A
♿ Accessibility: Improves clarity for screen reader users by separating the name and the command.
PR created automatically by Jules for task 1950424283835398538 started by @AhmmedSamier