agentleFS
rundopsrundops/dops/.claude/skills/wizard-forms/SKILL.md

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

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
  1. Very specific:

    Add ParamXxx constant to internal/domain/runbook.go

    line 63
  2. Very specific:

    Add case to fieldMode() in wizard model

    line 64
  3. Very specific:

    Add rendering in renderCurrentField()

    line 65
  4. Very specific:

    Add key handling in Update() switch

    line 66
  5. Very specific:

    Add schema generation in internal/mcp/schema.go

    line 67

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

TypeRenderingInput
string> text inputType text, Enter to submit
integer> text inputMust be numeric
boolean[Yes] [No] toggle←→ toggle, Enter confirm
select> option cursor list↑↓ nav, Enter select
multi_select[x]/[ ] checkboxesSpace toggle, ↑↓ nav, Enter confirm
file_path> text inputType path
resource_id> text inputType ID
secret> •••••••••• or > ****Enter to keep saved, type to override

Persistence Flow

  1. Wizard shows ALL params with pre-filled saved values
  2. Sensitive fields show •••••••••• (enter to keep, type to override)
  3. Enter on pre-fill → accept, advance (no save prompt)
  4. New/changed value → "Save for future runs? [Yes/No]" (default No)
  5. Yes → saves to config.json at field's scope (global/catalog/runbook)
  6. No → ephemeral, advances without saving

Overlay Style

  • Left accent bar: ThickBorder() left only, primary color
  • Panel background: backgroundPanel color
  • Header: green $ + bold command text (only shows --param for overrides)
  • Centered: lipgloss.Place(), width 2/3 terminal
  • Context-sensitive footer hints per field type and phase

Adding a New Field Type

  1. Add ParamXxx constant to internal/domain/runbook.go
  2. Add case to fieldMode() in wizard model
  3. Add rendering in renderCurrentField()
  4. Add key handling in Update() switch
  5. Add schema generation in internal/mcp/schema.go

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.