Source: qdash /controls "Layer a framework onto your controls" — c64 explorations, 2026-08-11
The current panel spends a 2×3 grid of full-width cards (one row per ~3 frameworks) on what is a set of on/off toggles — and the backend vocabulary is actually 10 packs, not the 6 the panel shows, so the card grid gets worse as the catalog completes. Four compact alternatives, all driving one shared enabled-set — toggle in any variation and the others follow. Baseline included for honest comparison.
Baseline — current card grid
what /controls ships today, at the real 10-pack catalog sizeLayer a framework onto your controls
2 of 10 enabledToggle chips
every option visible, one wrap line, ~6× less vertical spaceFrameworks
2 of 10 enabledA pack maps qdash's live detections to that framework's controls and lights up Compliance coverage.
Popover picker
one line closed — the whole panel collapses to a summary + buttonFrameworks
owasp-llmsoc2Enabled-only + add
managed-list pattern — show only what's on, add from a sentence pillFrameworks
2 enabledthe add pill lists only the 8 not-yet-enabled packs · disabled packs cost zero pixels
Checkbox wrap
the GovernSheet's own Satisfies idiom, promoted to the panelFrameworks
2 of 10 enabledc64 — framework-picker explorations replacing the /controls pack-card grid. All four ideas + the baseline drive one shared enabled-set (toggle anywhere, everywhere follows) over the full 10-pack rules.rs vocabulary — the shipped panel shows only 6, so every alternative here also fixes a completeness gap. Trade-offs: chips (1) keep the full catalog scannable at a glance; popover (2) is the smallest closed state but hides what's NOT enabled behind a click; add-pill (3) optimizes the steady state (packs rarely change after onboarding) and reuses the SentenceSelect + managed-list idiom; checkbox wrap (4) is the same idiom the GovernSheet's Satisfies row already uses — choosing it would make the panel and the sheet read identically.