What problem does it solve? Adding user input to a clawker CLI command requires choosing between two distinct prompting layers (line-based prompter vs. BubbleTea wizard) with different APIs, import boundaries, and non-interactive fallback behaviors. This Skill provides the decision tree, API contracts, and a reference implementation so you wire prompts correctly the first time. ## Core Features & Use Cases - Decision tree for prompt selection: Maps each input need (confirm, text, select, multi-step form) to the correct package — internal/prompter for single prompts, internal/tui RunWizard for multi-step forms. - Full API reference: Documents Prompter methods (String, Confirm, Select), wizard field models (SelectField, TextField, ConfirmField), StepperBar rendering, and WizardModel internals including SkipIf conditional steps and navigation. - Reference implementation: Walks through clawker project init as the canonical hybrid wizard + progress + static output pattern, including non-interactive bypass and test strategies. - Use Case: When adding a new clawker container create flow that asks for image, packages, and confirmation, use this Skill to build a WizardField list with SkipIf predicates and wire it through f.TUI.RunWizard. ## Quick Start Ask the AI to add a multi-step wizard to a clawker command using RunWizard with SelectField, TextField, and ConfirmField definitions following the project init pattern.
