wizard-forms
Skill3 starsChanged 8 months agoMITView on GitHub
Custom wizard form patterns for Go. Use when creating or editing interactive forms, field-by-field parameter input, select menus, text inputs, confirmations, multi-select, or the wizard overlay. Triggers on wizard model changes, new field types, or form flow modifications.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- masonhuemmer/dopsword for word, first seen Mar 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- masonhuemmer/dops★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bubbletea-patternsSkill
- charm-stylingSkill
- clean-code-boundariesSkill
- clean-code-designSkill
- clean-code-errorsSkill
- clean-code-functionsSkill
- clean-code-namingSkill
- clean-code-solidSkill
- clean-code-testingSkill
- cli-structureSkill
- create-runbookSkill
- demo-recordingSkill
- mutation-testingSkill
- shell-scriptsSkill
- spec-workflowSkill
- tdd-workflowSkill
- tui-layoutSkill
- tui-testingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
Add ParamXxx constant to internal/domain/runbook.go
- Very specific: line 64
Add case to fieldMode() in wizard model
- Very specific: line 65
Add rendering in renderCurrentField()
- Very specific: line 66
Add key handling in Update() switch
- Very specific: line 67
Add schema generation in internal/mcp/schema.go
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Custom Wizard Form Patterns
This project uses a custom wizard implementation (not Huh library) in internal/tui/wizard/model.go.
Architecture
Field-by-field progression with per-field save control:
type Model struct {
params []domain.Parameter // ALL params to collect
current int // current field index
values map[string]string // collected values
input textinput.Model // for text fields
cursor int // for select/multiselect/boolean
checked map[int]bool // for multiselect toggles
phase wizardPhase // phaseInput or phaseSave
changed bool // whether value differs from pre-fill
resolved map[string]string // pre-filled values from config
prefill map[string]bool // which fields had saved values
store config.ConfigStore // for per-field saving
}Field Types
| Type | Rendering | Input |
string | > text input | Type text, Enter to submit |
integer | > text input | Must be numeric |
boolean | [Yes] [No] toggle | ←→ toggle, Enter confirm |
select | > option cursor list | ↑↓ nav, Enter select |
multi_select | [x]/[ ] checkboxes | Space toggle, ↑↓ nav, Enter confirm |
file_path | > text input | Type path |
resource_id | > text input | Type ID |
secret | > •••••••••• or > **** | Enter to keep saved, type to override |
Persistence Flow
- Wizard shows ALL params with pre-filled saved values
- Sensitive fields show
•••••••••• (enter to keep, type to override) - Enter on pre-fill → accept, advance (no save prompt)
- New/changed value → "Save for future runs? [Yes/No]" (default No)
- Yes → saves to config.json at field's scope (global/catalog/runbook)
- No → ephemeral, advances without saving
Overlay Style
- Left accent bar:
ThickBorder()left only,primarycolor - Panel background:
backgroundPanelcolor - Header: green
$+ bold command text (only shows--paramfor overrides) - Centered:
lipgloss.Place(), width 2/3 terminal - Context-sensitive footer hints per field type and phase
Adding a New Field Type
- Add
ParamXxxconstant tointernal/domain/runbook.go - Add case to
fieldMode()in wizard model - Add rendering in
renderCurrentField() - Add key handling in
Update()switch - Add schema generation in
internal/mcp/schema.go
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

