rapid-prototyping

To prototype multiple UI design options in separate git worktrees, this skill proposes 2-4 concrete directions and isolates each in its own worktree under .worktrees with a descriptive name, allowing parallel design validation.

The best way to validate different dashboard prototype directions is generating multiple concrete options, writing a prototype-spec.md for each detailing goals and mocked data, and implementing one happy path per option before landing the chosen slice.

Yes, you need a Git repository with worktree support to use git worktrees for prototyping. The skill creates separate worktrees for each design option and requires the ability to land the chosen prototype back into the main branch.

A prototype-spec.md helps with rapid prototyping by detailing the goal, happy path, assumptions, mocked data, and explicit shortcuts for each design option, speeding decision-making and reducing polish-time during design validation.

Yes, you can land a selected prototype slice from a worktree back into the main worktree. After implementing one happy path per chosen option, the skill lands the selected slice and removes temporary worktrees upon completion.

You should not use git worktrees for design exploration if your project lacks a Git repository with worktree support or if you cannot merge the chosen prototype back into the main branch, as these are required dependencies.