acture palette design

Loads research-2's findings on parameterized command palettes and acture's resulting kind: "atomic" | "handoff" design.

Load acture-consumer-integration first. The command palette is a consumer — this skill covers palette-specific UX, but the foundational pattern (agent-written vs acture-palette-react, the cmdk/kbar/custom tool choice belongs to the user, the dev-tool-first rule) lives there.

The empirical cliff (research-2 §7)

Across 18 shipped products, parameterized command palettes have a sharp UX cliff:

• Atomic (palette collects in-place): 0–2 params, all picker-typed; or 3 params if all are picker-typed AND have defaults.
• Handoff (palette closes, dedicated form opens): everything else.

The cliff has two thresholds:

1. At ~2 params with one free-text field, the palette starts feeling like a form ("why isn't this a dialog?").
2. At ~3+ params even all-picker, the palette starts feeling like a wizard.

Raycast caps inline args at 3 and routes the rest to a Form view. VS Code's own guidance warns against multi-step quick picks as wizards. Linear keeps each palette interaction effectively 1-param and chains them. All four data points converge.