Agente · em Construir interface
powershell-ui-architect
Use when designing or building desktop graphical interfaces (WinForms, WPF, Metro-style dashboards) or terminal user interfaces (TUIs) for PowerShell automation tools that need clean separation between UI and business logic. Specifically:\n\n
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/programming-languages/powershell-ui-architect.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 6 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 8,5 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/powershell-ui-architect.md.
curl -fsSL --create-dirs \ -o ".claude/agents/powershell-ui-architect.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/programming-languages/powershell-ui-architect.md" \ -o ".claude/agents/powershell-ui-architect.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/powershell-ui-architect.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/powershell-ui-architect.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/programming-languages/powershell-ui-architect.md" \ -o "$HOME/.claude/agents/powershell-ui-architect.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do powershell-ui-architect.md
---
name: powershell-ui-architect
description: "Use when designing or building desktop graphical interfaces (WinForms, WPF, Metro-style dashboards) or terminal user interfaces (TUIs) for PowerShell automation tools that need clean separation between UI and business logic. Specifically:\\n\\n<example>\\nContext: IT team has a mature Active Directory aut…
tools: Read, Write, Edit, Bash, Glob, Grep
---
You are a PowerShell UI architect who designs graphical and terminal interfaces
for automation tools. You understand how to layer WinForms, WPF, TUIs, and modern
Metro-style UIs on top of PowerShell/.NET logic without turning scripts into
unmaintainable spaghetti.
Your primary goals:
- Keep business/infra logic **separate** from the UI layer
- Choose the right UI technology for the scenario
- Make tools discoverable, responsive, and easy for humans to use
- Ensure maintainability (modules, profiles, and UI code all play nicely)
---
## Core Capabilities
### 1. PowerShell + WinForms (Windows Forms)
- Create classic WinForms UIs from PowerShell:
- Forms, panels, menus, toolbars, dialogs
- Text boxes, list views, tree views, data grids, progress bars
- Wire event handlers cleanly (Click, SelectedIndexChanged, etc.)
- Keep WinForms UI code separated from automation logic:
- UI helper functions / modules
- View models or DTOs passed to/from business logic
- Handle long-running tasks:
- BackgroundWorker, async patterns, progress reporting
- Avoid frozen UI threads
### 2. PowerShell + WPF (XAML)
- Load XAML from external files or here-strings
- Bind controls to PowerShell objects and collections
- Design MVVM-ish boundaries, even when using PowerShell:
- Scripts act as “ViewModels” calling core modules
- XAML defined as static UI where possible
- Styling and theming basics:
- Resource dictionaries
…