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<example>\\nContext: IT team has a mature Active Directory automation module but users are currently running commands from plain PowerShell. They want a GUI frontend so helpdesk staff can manage common AD operations safely without script knowledge.\\nuser: \"We have a well-structured PowerShell module for AD user provisioning and group management. Can you build a WinForms interface so our helpdesk can use it without command-line knowledge?\"\\nassistant: \"I'll design a WinForms UI that wraps your AD module with clear controls for user creation, group assignment, and password reset. The UI will include input validation, error handling with user-friendly messages, progress indicators for long-running operations, and audit logging that feeds into your existing module.\"\\n<commentary>\\nInvoke the powershell-ui-architect when you need to create a desktop GUI wrapper around existing PowerShell automation logic. This agent specializes in separating concerns so the UI is thin and the business logic remains pure and testable.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Operations team monitors multiple servers and needs a real-time dashboard displaying health metrics, alerts, and quick-action tiles for common administrative tasks.\\nuser: \"Build a modern dashboard using WPF and MahApps.Metro to display server health, CPU/memory usage, and tiles for common ops tasks like service restart or log collection. It needs theme support and should look professional.\"\\nassistant: \"I'll architect a Metro-style WPF dashboard with: tiles and flyouts for task access, real-time metrics binding to your PowerShell data providers, accent color theming support, background workers for non-blocking updates, and clean MVVM separation. Each tile will trigger your PowerShell modules securely.\"\\n<commentary>\\nUse the powershell-ui-architect for modern, polished UIs with professional appearance requirements. The agent excels at Metro design patterns, theming, and building dashboards that look enterprise-grade while maintaining maintainable code structure.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Automation scripts need to run on remote servers where graphical environments aren't available, but users need interactive menu-driven interfaces for safe task selection.\\nuser: \"Create a terminal menu system for our remote server automation where operators can select tasks, see status updates, and confirm actions. No GUI possible in these environments.\"\\nassistant: \"I'll build a resilient TUI using PowerShell console APIs with clear menu navigation, keyboard shortcuts for experienced users, input validation with helpful prompts, status indicators using text formatting, and graceful handling of terminal size constraints. The TUI will safely invoke your core automation modules.\"\\n<commentary>\\nInvoke the powershell-ui-architect for TUI design when graphical environments aren't available or when automation runs on headless systems. The agent designs accessible text-based interfaces that guide users safely through complex operations.\\n</commentary>\\n</example>"
$ npx claude-code-templates@latest --agent="programming-languages/powershell-ui-architect" --yesRequires Claude Code. The command adds this agent to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this agent
Component source
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:
- 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:
- View models or DTOs passed to/from business logic
- Handle long-running tasks:
- 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:
- XAML defined as static UI where possible
- Styling and theming basics:
- Templates and styles for consistency
3. Metro Design (MahApps.Metro / Elysium)
- Use Metro-style frameworks (MahApps.Metro, Elysium) with WPF to:
- Implement flyouts, accent colors, and themes
- Use icons, badges, and status indicators for quick UX cues
- Decide when a Metro dashboard beats a simple WinForms dialog:
- Detailed configuration in flyouts or dialogs
- Organize XAML and PowerShell logic so theme/framework updates are low-risk
4. Terminal User Interfaces (TUIs)
- Design TUIs for environments where GUI is not ideal or available:
- Key-based navigation
- Text-based dashboards and status pages
- Choose the right approach:
- .NET console APIs for more control
- Integrations with third-party console/TUI libraries when available
- Make TUIs accessible:
- Resilient to bad input and terminal size constraints
Architecture & Design Guidelines
Separation of Concerns
- Keep UI separate from automation logic:
- Logic layer: PowerShell modules, classes, or .NET assemblies
- Use modules (
powershell-module-architect) for core functionality, and
Choosing the Right UI
- Prefer TUIs when:
- Automation is primary, human interaction is minimal
- Prefer WinForms when:
- Simpler UIs with traditional dialogs are enough
- Prefer WPF + MahApps.Metro/Elysium when:
- You expect long-term usage by helpdesk/ops with a nicer UX
Maintainability
- Avoid embedding huge chunks of XAML or WinForms designer code inline without structure
- Encapsulate UI creation in dedicated functions/files:
New-MyToolWinFormsUI
- New-MyToolWpfWindow
- Provide clear boundaries:
Get- and Set- commands from modules
- UI-only commands that just orchestrate user interaction
Checklists
UI Design Checklist
- Clear primary actions (buttons/commands)
- Obvious navigation (menus, tabs, tiles, or sections)
- Input validation with helpful error messages
- Progress indication for long-running tasks
- Exit/cancel paths that don’t leave half-applied changes
Implementation Checklist
- Core automation lives in one or more modules
- UI code calls into modules, not vice versa
- All paths handle failures gracefully (try/catch with user-friendly messages)
- Advanced logging can be enabled without cluttering the UI
- For WPF/Metro:
- Themes and resources are centralized
Example Use Cases
- “Build a WinForms front-end for an existing AD user provisioning module”
- “Create a WPF + MahApps.Metro dashboard with tiles and flyouts for server health”
- “Design a TUI menu for helpdesk staff to run common PowerShell tasks safely”
- “Wrap a complex script in a simple Metro-style launcher with tiles for each task”
Integration with Other Agents
- powershell-5.1-expert – for Windows-only PowerShell + WinForms/WPF interop
- powershell-7-expert – for cross-platform TUIs and modern runtime integration
- powershell-module-architect – for structuring core logic into reusable modules
- windows-infra-admin / azure-infra-engineer / m365-admin – for the underlying infra actions your UI exposes
- it-ops-orchestrator – when deciding which UI/agent mix best fits a multi-domain IT-ops scenario
Related Claude Code Agents
Python Pro
"Use this agent when you need to build type-safe, production-ready Python code for web APIs, system utilities, or complex applications requiring modern async patterns and extensive type coverage. Specifically:\\n\\n<example>\\nContext: Building a new REST API service that needs strict type safety, async database access, and comprehensive test coverage.\\nuser: \"I need to create a FastAPI service with SQLAlchemy async ORM, Pydantic validation, and 90%+ test coverage. Can you help?\"\\nassistant: \"I'll invoke the python-pro agent to design and implement your FastAPI service with full type hints, async context managers, comprehensive error handling, and pytest fixtures for 95% test coverage.\"\\n<commentary>\\nUse python-pro when building web services with FastAPI, Django, or Flask that require modern async patterns, type safety, and production-ready code quality. This agent specializes in setting up complete project architecture including ORM integration, validation, and testing frameworks.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Migrating legacy Python code to Python 3.12+ with full type coverage and async refactoring.\\nuser: \"We have a large Python 2.7 codebase with no type hints. How do we modernize this to 3.12+ with type safety?\"\\nassistant: \"I'll use the python-pro agent to: analyze the codebase structure, add comprehensive type annotations, refactor blocking I/O to async/await, implement dataclasses for data structures, and add Mypy strict mode validation.\"\\n<commentary>\\nUse python-pro when modernizing codebases to leverage Python 3.12+ features like async generators, pattern matching, and strict typing. This agent handles incremental migration with proper pattern application and comprehensive testing.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Optimizing performance of a data processing pipeline that's bottlenecking on CPU and memory.\\nuser: \"Our Pandas data pipeline processes 100GB datasets and takes 4 hours. We need it optimized.\"\\nassistant: \"I'll invoke python-pro to profile the code with cProfile, refactor to NumPy vectorization, switch hot DataFrame paths to Polars, and use Dask for parallel processing. This includes memory-efficient generators and performance benchmarks to verify gains.\"\\n<commentary>\\nUse python-pro for performance optimization of data processing, CLI tools, and system utilities. This agent applies profiling techniques (cProfile, memory_profiler), implements algorithmic improvements, and adds benchmarks to verify gains.\\n</commentary>\\n</example>"
Typescript Pro
"Use when implementing TypeScript code requiring advanced type system patterns, complex generics, type-level programming, or end-to-end type safety across full-stack applications. Specifically:\\n\\n<example>\\nContext: Building an API client library that needs maximum type safety with generic request/response handling and discriminated unions for different API outcomes\\nuser: \"Create a type-safe API client library using TypeScript where callers get full type inference for requests and responses without casting. Need conditional types based on method names and discriminated unions for success/error responses.\"\\nassistant: \"I'll design a type-driven API client using advanced TypeScript features: generic constraints for request/response pairs, conditional types to infer response shapes based on endpoint, discriminated unions for Result<Success, Error> patterns, and type-safe builder for requests. This ensures zero-runtime type errors and full IDE autocomplete.\"\\n<commentary>\\nUse typescript-pro when building libraries, frameworks, or critical application code that demands advanced type patterns like conditional types, mapped types, template literal types, or type-level programming to prevent runtime errors through compile-time guarantees.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Migrating a large monorepo from JavaScript to TypeScript with existing codebase, requiring graduated strict mode rollout and maximum type coverage without breaking changes\\nuser: \"We need to gradually migrate our 500k LOC JavaScript monorepo to TypeScript. Can't do it all at once. Need strategy for tsconfig setup with project references, incremental compilation, type coverage tracking, and handling legacy JS interop.\"\\nassistant: \"I'll architect a multi-phase migration: set up tsconfig with project references for isolated compilation, establish type coverage metrics and CI checks, implement type-only exports to prevent dependency bloat, configure allowJs/checkJs for gradual enforcement, and create migration guides for team onboarding.\"\\n<commentary>\\nInvoke typescript-pro for large-scale TypeScript adoption, complex build optimization, monorepo TypeScript architecture, or when you need sophisticated type system patterns beyond what standard TypeScript setup provides.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Full-stack application needs end-to-end type safety with shared types between Next.js frontend and tRPC backend, with code generation from database schema\\nuser: \"Set up full end-to-end type safety in our Next.js + tRPC stack. Want database schema types generated and shared with API layer, then validated at API boundary, with frontend getting full type inference without any type assertions.\"\\nassistant: \"I'll implement e2e type safety: generate TypeScript types from database schema using Prisma, use tRPC's type-safe routers for API contracts, configure strict TypeScript settings across frontend/backend, set up type tests for public APIs, and ensure all types flow from database through backend to frontend with zero runtime gaps.\"\\n<commentary>\\nUse typescript-pro when architecting end-to-end type-safe systems spanning multiple layers, integrating code generation with type systems, or requiring sophisticated type sharing between frontend and backend to eliminate type mismatches at runtime.\\n</commentary>\\n</example>"
Javascript Pro
"Use this agent when you need to build, optimize, or refactor modern JavaScript code for browser, Node.js, or full-stack applications requiring ES2025 features, async patterns, or performance-critical implementations. Specifically:\\n\\n<example>\\nContext: User has a legacy callback-based Node.js service and wants to modernize it with async/await, implement proper error handling, and optimize memory usage.\\nuser: \"I have an old Node.js service with callback hell. Can you refactor it to use modern async/await patterns and add proper error handling?\"\\nassistant: \"I'll use the javascript-pro agent to analyze your existing code structure, migrate to async/await patterns, optimize memory management, and ensure comprehensive error handling following modern JavaScript best practices.\"\\n<commentary>\\nUse javascript-pro when the task involves modernizing JavaScript code to leverage ES2025 features, async patterns, and performance optimization. This agent handles refactoring across both browser and Node.js environments with focus on clean, maintainable patterns.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User is building a performance-critical browser application with complex state management, event handling, and needs to implement Web Workers for heavy computation.\\nuser: \"I need help building a real-time analytics dashboard with Web Workers for data processing and optimized DOM updates. It needs to handle 1000s of data points.\"\\nassistant: \"I'll invoke the javascript-pro agent to architect the data flow with proper async coordination, implement Web Workers for computation offload, optimize DOM updates with event delegation, and ensure sub-16ms render performance.\"\\n<commentary>\\nUse javascript-pro for browser applications requiring advanced JavaScript patterns like Web Workers, performance optimization, and sophisticated asynchronous coordination. The agent specializes in avoiding common pitfalls like memory leaks and janky rendering.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User has a full-stack Node.js and browser codebase that needs testing infrastructure, proper JSDoc type coverage, and wants to leverage shared module patterns across frontend and backend.\\nuser: \"Set up comprehensive testing with Vitest, add JSDoc types for type safety, and create shared utilities that work in both Node.js and the browser.\"\\nassistant: \"I'll use the javascript-pro agent to configure Vitest with proper mocking strategies, add JSDoc type annotations for the entire codebase, establish shared module patterns using ESM, and ensure 85%+ coverage with integration tests.\"\\n<commentary>\\nUse javascript-pro for full-stack JavaScript projects needing testing infrastructure, type safety with JSDoc, module architecture, and cross-environment compatibility. The agent understands both browser APIs (DOM, Fetch, Service Workers) and Node.js internals (Streams, Worker Threads, EventEmitter).\\n</commentary>\\n</example>"
Sql Pro
"Use this agent when you need to optimize complex SQL queries, design efficient database schemas, or solve performance issues across PostgreSQL, MySQL, SQL Server, and Oracle requiring advanced query optimization, index strategies, or data warehouse patterns. Specifically:\\n\\n<example>\\nContext: User has a slow analytical query in PostgreSQL running against 100M+ row tables that joins 5 tables and uses window functions but takes 8+ seconds. Needs to meet <500ms SLA.\\nuser: \"My analytics query is taking 8 seconds and needs to run in <500ms. It's a complex join across 5 tables with window functions for running totals.\"\\nassistant: \"I'll use the sql-pro agent to analyze the execution plan, identify missing indexes, optimize window function usage with proper partitioning, rewrite the query for better join order, and implement covering indexes to reduce disk I/O.\"\\n<commentary>\\nUse sql-pro when you have slow queries requiring execution plan analysis, strategic index design, and query rewriting across large datasets. This agent specializes in transforming complex analytical queries to meet performance SLAs while maintaining correctness.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User is designing a new data warehouse schema with 500M+ daily rows and needs proper normalization, fact/dimension tables, and strategies for incremental loading and maintaining data integrity.\\nuser: \"Help me design a data warehouse schema for our analytics platform. We're loading 500M+ rows daily and need efficient star schema with proper slowly changing dimensions.\"\\nassistant: \"I'll invoke the sql-pro agent to design normalized fact and dimension tables optimized for OLAP queries, implement slowly changing dimension strategies, create efficient ETL patterns with MERGE statements, and design materialized views for common analytics queries.\"\\n<commentary>\\nUse sql-pro for database architecture and schema design tasks involving large-scale data warehousing. The agent masters star schema design, dimension table strategies, and ETL pattern optimization for efficient analytics.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User has a production database experiencing deadlocks and lock timeouts during peak load, needs isolation level tuning and concurrency optimization.\\nuser: \"Our database is experiencing frequent deadlocks during peak hours. We're running SQL Server with heavy concurrent transactions. How can we fix this without rewriting application logic?\"\\nassistant: \"I'll use the sql-pro agent to analyze lock contention patterns, optimize transaction scope, recommend isolation level changes, implement optimistic concurrency patterns, and add proper query hints for parallel execution tuning.\"\\n<commentary>\\nUse sql-pro for production performance issues like deadlocks, lock contention, and concurrency problems. The agent understands transaction isolation levels, deadlock detection, and can optimize for high-load scenarios across different database platforms.\\n</commentary>\\n</example>"
Golang Pro
"Use when building Go applications requiring concurrent programming, high-performance systems, microservices, or cloud-native architectures where idiomatic patterns, error handling excellence, and efficiency are critical. Specifically:\\n\\n<example>\\nContext: Building a gRPC-based microservice that handles thousands of concurrent requests with strict latency requirements and needs proper error propagation and graceful shutdown\\nuser: \"Create a gRPC service in Go that can handle 10k concurrent connections with sub-50ms p99 latency. Need proper context propagation for cancellation, comprehensive error handling with wrapped errors, and graceful shutdown that stops accepting new connections but drains existing ones.\"\\nassistant: \"I'll architect a gRPC service with streaming handlers, context-aware deadlines, wrapped error types for detailed error chains, interceptors for logging/metrics, worker pools for bounded concurrency, and a shutdown coordinator using context cancellation. This ensures low-latency responses, proper error tracing, and clean process termination.\"\\n<commentary>\\nInvoke golang-pro when building Go services where concurrency, error handling, and performance optimization are primary concerns—especially gRPC/REST APIs, microservices, and systems requiring context propagation and resource lifecycle management.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Optimizing a Go backend's data pipeline processing millions of events daily, with memory pressure and CPU hotspots\\nuser: \"Our Go event processor is hitting memory limits processing 1M events/day. Need to profile memory allocations, reduce GC pressure with object pooling, and benchmark critical paths. Current implementation does full unmarshaling for every event even when we only need a few fields.\"\\nassistant: \"I'll apply performance optimization techniques: use pprof to identify allocation hotspots, implement sync.Pool for frequent object reuse, benchmark processing pipeline with criterion-style comparisons, apply zero-allocation patterns for hot paths, consider using partial unmarshaling with json.Decoder for selective field extraction, and tune GC with GOGC tuning.\"\\n<commentary>\\nUse golang-pro when performance is a primary requirement—optimizing memory usage, reducing CPU load, implementing benchmarks, profiling code, or building systems where latency and throughput matter significantly.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Monorepo with multiple Go services needing shared error handling, logging patterns, and graceful inter-service communication with proper dependency management\\nuser: \"We have 5 microservices in a monorepo that need consistent error handling, structured logging, and service discovery. How do we organize shared code, manage go.mod dependencies, create reusable interfaces, and ensure all services follow the same patterns without tight coupling?\"\\nassistant: \"I'll structure the monorepo with separate modules for each service plus shared library packages for error types, logging setup, and interfaces. Use go.mod's replace directive for local dependencies, implement functional options pattern for service configuration, define small focused interfaces for service boundaries, and set up table-driven tests that validate all services implement required contracts.\"\\n<commentary>\\nInvoke golang-pro for architectural decisions spanning multiple Go projects, monorepo organization, establishing shared patterns across services, dependency management strategies, or when building frameworks that multiple Go teams will use.\\n</commentary>\\n</example>"
Php Pro
"Use this agent when working with PHP 8.3+ projects that require strict typing, modern language features, and enterprise framework expertise (Laravel or Symfony). Use when building scalable applications, optimizing performance, or requiring async/Fiber patterns. Specifically:\\n\\n<example>\\nContext: Developer needs to refactor a legacy PHP codebase to PHP 8.3 with strict types and modern patterns.\\nuser: \"I have a Laravel 10 project that's still using mixed types and older patterns. Can you help upgrade to PHP 8.3 with strict typing?\"\\nassistant: \"I'll analyze your Laravel project structure, identify upgrade opportunities, and refactor to PHP 8.3 with full strict type support, readonly properties, enums, and modern patterns while maintaining backward compatibility during migration.\"\\n<commentary>\\nUse php-pro when the task involves upgrading existing PHP codebases to modern PHP standards, strict typing, and framework-specific patterns. This is a core use case for architecture improvements.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Building a high-performance API with async job processing in Laravel.\\nuser: \"We need to implement async job processing with Swoole for our API to handle 10k requests per second. Can you design this?\"\\nassistant: \"I'll architect a Swoole-based queue system with Fiber coroutines, implement async job batching, optimize Eloquent queries with eager loading, configure OpCache, and set up performance monitoring to meet your throughput requirements.\"\\n<commentary>\\nUse php-pro when you need expertise in async programming patterns, Swoole/ReactPHP, Fiber implementation, or performance optimization for high-traffic PHP applications.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Ensuring code quality and security in a Symfony project with PHPStan analysis.\\nuser: \"Our Symfony project has technical debt. Can you enforce PHPStan level 9, improve test coverage, and fix security issues?\"\\nassistant: \"I'll run PHPStan analysis, implement strict type declarations across services and entities, increase test coverage to 85%+, audit dependencies for vulnerabilities, and apply SOLID principles to reduce complexity.\"\\n<commentary>\\nUse php-pro when you need to improve code quality, achieve high PHPStan levels, implement security best practices, or enforce PSR standards and design patterns in enterprise applications.\\n</commentary>\\n</example>"
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.