Vois Component Selection Skill

You are picking specific components from the workspace manifest. This skill answers "which component for this job" — not what structure (that's vois-patterns) and not how to style it (that's vois-tokens).

Read this skill after vois-patterns has determined the container type. For every component you pick, call record_component_choice before moving to vois-tokens.

The Quick Reference table below resolves most cases on its own. When it doesn't — ambiguous case, need the full decision tree, or need to justify the choice — read the matching reference file.

Before You Pick a Component

1. Identify the job-to-be-done — phrase it as a verb plus object: "confirm a destructive action", "show transient feedback", "group related controls"
2. Find the matching row in Quick Reference, or the matching job in the index below
3. If ambiguous, read the matching reference file and walk its decision tree
4. Call record_component_choice with your selection:

   Tool: record_component_choice
   Arguments:
     job: <the job-to-be-done, one sentence>
     componentName: <exact component name from the manifest>
     alternativesConsidered: <array of component names you ruled out>
     reasoning: <one sentence on why you chose this over the alternatives>

1. If no section matches your job, call report_pattern_gap:

   Tool: report_pattern_gap
   Arguments:
     description: <what the UI needs to do>
     closestPathId: <closest job ID from this skill, e.g. JOB-OVERLAY-INTERACTION>
     gapDescription: <what the rubrics don't cover>

Note on workspace manifests. These rubrics use standard shadcn/ui component names. Your workspace may extend or rename them — e.g. Banner instead of Alert, DataTable instead of Table. Check your workspace manifest for the exact name; use the rubric logic to make the selection, then record the workspace-specific name.

Quick Reference

Job Index

Each reference file has the full decision tree (with thresholds and edge cases) plus "why not X" reasoning for every alternative ruled out.

Relationship to Other Skills

Read `vois-patterns` first. That skill determines the container type — settings page, form, table, dialog. Once you know the structure, come here to pick the specific components that fill it.

Read `vois-tokens` after. Once components are selected, vois-tokens handles tokens, spacing, animation, and accessibility implementation.

Righter for all copy. Component labels, empty state messages, button text, error copy — all of it goes through righter (which calls get_microcopy first). This skill says nothing about words.