Development
gentleman-installer - Claude MCP Skill
Installation step patterns for Gentleman.Dots TUI installer. Trigger: When editing installer.go, adding installation steps, or modifying the installation flow.
SEO Guide: Enhance your AI agent with the gentleman-installer tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to installation step patterns for gentleman.dots tui installer. trigger: when editing installer.go, add... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md## When to Use
Use this skill when:
- Adding new installation steps
- Modifying existing tool installations
- Working on backup/restore functionality
- Implementing non-interactive mode support
- Adding new OS/platform support
---
## Critical Patterns
### Pattern 1: InstallStep Structure
All steps follow this structure in `model.go`:
```go
type InstallStep struct {
ID string // Unique identifier: "terminal", "shell", etc.
Name string // Display name: "Install Fish"
Description string // Short description
Status StepStatus // Pending, Running, Done, Failed, Skipped
Progress float64 // 0.0 - 1.0
Error error // Error if failed
Interactive bool // Needs terminal control (sudo, chsh)
}
```
### Pattern 2: Step Registration in SetupInstallSteps
Steps MUST be registered in `SetupInstallSteps()` in `model.go`:
```go
func (m *Model) SetupInstallSteps() {
m.Steps = []InstallStep{}
// Conditional step based on user choice
if m.Choices.SomeChoice {
m.Steps = append(m.Steps, InstallStep{
ID: "newstep",
Name: "Install Something",
Description: "Description here",
Status: StatusPending,
Interactive: false, // true if needs sudo/password
})
}
}
```
### Pattern 3: Step Execution in executeStep
All step logic goes in `installer.go`:
```go
func executeStep(stepID string, m *Model) error {
switch stepID {
case "newstep":
return stepNewStep(m)
// ... other cases
default:
return fmt.Errorf("unknown step: %s", stepID)
}
}
func stepNewStep(m *Model) error {
stepID := "newstep"
SendLog(stepID, "Starting installation...")
// Check if already installed
if system.CommandExists("newtool") {
SendLog(stepID, "Already installed, skipping...")
return nil
}
// Install based on OS
var result *system.ExecResult
if m.SystemInfo.IsTermux {
result = system.RunPkgInstall("newtool", nil, func(line string) {
SendLog(stepID, line)
})
} else {
result = system.RunBrewWithLogs("install newtool", nil, func(line string) {
SendLog(stepID, line)
})
}
if result.Error != nil {
return wrapStepError("newstep", "Install NewTool",
"Failed to install NewTool",
result.Error)
}
SendLog(stepID, "ā NewTool installed")
return nil
}
```
### Pattern 4: Interactive Steps (sudo/password required)
Mark step as Interactive and use `runInteractiveStep`:
```go
// In SetupInstallSteps:
m.Steps = append(m.Steps, InstallStep{
ID: "interactive_step",
Name: "Configure System",
Description: "Requires password",
Status: StatusPending,
Interactive: true, // KEY: marks as interactive
})
// In runNextStep (update.go):
if step.Interactive {
return runInteractiveStep(step.ID, &m)
}
```
---
## Decision Tree
```
Adding new tool installation?
āāā Add step to SetupInstallSteps() with conditions
āāā Add case in executeStep() switch
āāā Create step{Name}() function in installer.go
āāā Handle all OS variants (Mac, Linux, Arch, Debian, Termux)
āāā Use SendLog() for progress updates
āāā Return wrapStepError() on failure
Step needs password/sudo?
āāā Set Interactive: true in InstallStep
āāā Use system.RunSudo() or system.RunSudoWithLogs()
āāā Use tea.ExecProcess for full terminal control
Step should be conditional?
āāā Check m.Choices.{option} before appending
āāā Check m.SystemInfo for OS-specific logic
āāā Use StatusSkipped if conditions not met
```
---
## Code Examples
### Example 1: OS-Specific Installation
```go
func stepInstallTool(m *Model) error {
stepID := "tool"
if !system.CommandExists("tool") {
SendLog(stepID, "Installing tool...")
var result *system.ExecResult
switch {
case m.SystemInfo.IsTermux:
result = system.RunPkgInstall("tool", nil, logFunc(stepID))
case m.SystemInfo.OS == system.OSArch:
result = system.RunSudoWithLogs("pacman -S --noconfirm tool", nil, logFunc(stepID))
case m.SystemInfo.OS == system.OSMac:
result = system.RunBrewWithLogs("install tool", nil, logFunc(stepID))
default: // Debian/Ubuntu
result = system.RunBrewWithLogs("install tool", nil, logFunc(stepID))
}
if result.Error != nil {
return wrapStepError("tool", "Install Tool",
"Failed to install tool",
result.Error)
}
}
// Copy configuration
SendLog(stepID, "Copying configuration...")
homeDir := os.Getenv("HOME")
if err := system.CopyDir(filepath.Join("Gentleman.Dots", "ToolConfig/*"),
filepath.Join(homeDir, ".config/tool/")); err != nil {
return wrapStepError("tool", "Install Tool",
"Failed to copy configuration",
err)
}
SendLog(stepID, "ā Tool configured")
return nil
}
func logFunc(stepID string) func(string) {
return func(line string) {
SendLog(stepID, line)
}
}
```
### Example 2: Error Wrapping Pattern
```go
func wrapStepError(stepID, stepName, description string, cause error) error {
return &StepError{
StepID: stepID,
StepName: stepName,
Description: description,
Cause: cause,
}
}
// Usage:
if result.Error != nil {
return wrapStepError("terminal", "Install Alacritty",
"Failed to install Alacritty. Check your internet connection.",
result.Error)
}
```
### Example 3: Config Patching
```go
// Patch config based on user choices
func stepInstallShell(m *Model) error {
// ... install shell ...
// Patch config for window manager choice
configPath := filepath.Join(homeDir, ".config/fish/config.fish")
if err := system.PatchFishForWM(configPath, m.Choices.WindowMgr, m.Choices.InstallNvim); err != nil {
return wrapStepError("shell", "Install Fish",
"Failed to configure window manager in shell",
err)
}
return nil
}
```
---
## Logging Pattern
Always use `SendLog` for step progress:
```go
SendLog(stepID, "Starting...") // Start
SendLog(stepID, "Downloading...") // Progress
SendLog(stepID, " ā file.txt") // Sub-item
SendLog(stepID, "ā Step completed") // Success
```
---
## Commands
```bash
cd installer && go build ./cmd/gentleman-installer # Build
./gentleman-installer --help # Show help
./gentleman-installer --non-interactive --shell=fish # Non-interactive
GENTLEMAN_VERBOSE=1 ./gentleman-installer --non-interactive # Verbose logs
```
---
## Resources
- **Steps**: See `installer/internal/tui/installer.go` for step implementations
- **Model**: See `installer/internal/tui/model.go` for SetupInstallSteps
- **System**: See `installer/internal/system/exec.go` for command execution
- **Non-interactive**: See `installer/internal/tui/non_interactive.go` for CLI modeSignals
Information
- Repository
- Gentleman-Programming/Gentleman.Dots
- Author
- Gentleman-Programming
- Last Sync
- 3/12/2026
- Repo Updated
- 3/12/2026
- Created
- 1/13/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
remote-browser
Controls a cloud browser from a sandboxed remote machine. Use when the agent is running in a sandbox (no GUI) and needs to navigate websites, interact with web pages, fill forms, take screenshots, or expose local dev servers via tunnels.
agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
troubleshooting
Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Related Guides
Mastering the Oracle CLI: A Complete Guide to the Claude Skill for Database Professionals
Learn how to use the oracle Claude skill. Complete guide with installation instructions and examples.
Python Django Best Practices: A Comprehensive Guide to the Claude Skill
Learn how to use the python django best practices Claude skill. Complete guide with installation instructions and examples.
Building Full-Stack Applications with Claude: The Node.js MongoDB JWT Express React Skill Guide
Learn how to use the nodejs mongodb jwt express react Claude skill. Complete guide with installation instructions and examples.