Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
thedaviddias avatar

Selection Input

  • 1 installs
  • 228 repo stars
  • Updated June 30, 2026
  • thedaviddias/ux-patterns-for-developers

Guides building a select/dropdown control where users choose one option from a short predefined list.

About

Covers designing an accessible single-select dropdown for short predefined option lists. A developer uses it when a form needs one choice from roughly 10-15 known options in limited space.

  • Use when options are short and space is limited
  • Prefer multi-select or autocomplete for multiple choices or long lists

Selection Input by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #1,609 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/thedaviddias/ux-patterns-for-developers --skill selection-input

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars228
Last updatedJune 30, 2026
Repositorythedaviddias/ux-patterns-for-developers

What it does

Guides building a select/dropdown control where users choose one option from a short predefined list.

Files

SKILL.mdMarkdownGitHub ↗

Selection Input

Choose from predefined options

What it solves

A selection input is a form control that allows users to choose one option from a predefined list of options. The selected option is typically displayed in a single-line text field, with the list of options hidden until the user interacts with the control.

When to use

  • When users need to select a single option from a list of predefined choices
  • When the list of options is relatively short (less than 10-15 items)
  • When screen space is limited, and displaying all options at once is not feasible
  • When the selected option doesn't need to be visible at all times

When to avoid

  • When users need to select multiple options (use checkboxes or a multi-select instead)
  • When the list of options is very long (consider using an autocomplete or a typeahead)
  • When users need to input free-form text (use a regular text input instead)
  • When the options are complex or require additional information or visual aids

Implementation workflow

1. Confirm the pattern matches the problem and constraints before copying the example. 2. Start from the anatomy and examples in references/pattern.md, then choose the smallest viable variation. 3. Apply accessibility, performance, and interaction guardrails before layering visual polish. 4. Use the testing guidance to verify behavior across keyboard, screen reader, responsive, and failure scenarios.

Accessibility guardrails

  • Use a visible label connected to the control via for/id.
  • Prefer native <select> for simple cases to inherit built-in accessibility.
  • Provide group labels for long lists (<optgroup>) and descriptive helper text when needed.
  • Keep focus indicators highly visible and maintain sufficient text/background contrast.
  • Announce validation and error states using aria-invalid and aria-describedby.

Related patterns

  • https://uxpatterns.dev/patterns/forms/autocomplete
  • https://uxpatterns.dev/patterns/forms/multi-select-input

---

For full implementation detail, examples, and testing notes, see references/pattern.md.

Pattern page: https://uxpatterns.dev/patterns/forms/selection-input

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.