windows▌

Critical patterns and pitfalls for Windows PowerShell.

BusyBox is a single binary that implements many common Unix tools.

Keep this workflow focused on existing debug windows and menu entries. Do not add a new utility/debug control window unless the user asks explicitly.

Secure Windows desktop automation with strict process validation, permission tiers, and audit logging. \n \n Provides UI Automation Framework (UIA) and Win32 API integration for discovering and interacting with Windows application elements, including window management, input simulation, and process interaction \n Enforces security-first approach with process validation, blocked application lists (password managers, admin tools, security software), and permission tier model (read-only, standard,

Provides expertise in building modern Windows desktop applications using WinUI 3, WPF, and Windows App SDK. Specializes in XAML-based UI development, MVVM architecture, native Windows integration, and modern packaging with MSIX.

Platform-agnostic patterns for building Windows images with Packer.

BusyBox is a single binary that implements many common Unix tools.

Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements. This skill covers system enumeration, credential harvesting, service exploitation, token impersonation, kernel exploits, and various misconfigurations that enable escalation from standard user to Administrator or SYSTEM privileges.

Automated Windows Flutter development environment setup with platform-specific toolchain configuration. \n \n Configures Flutter SDK paths, Visual Studio C++ toolchain installation, and platform-specific settings via interactive prompts for Windows Desktop, Android, or both targets \n Handles Android Studio setup, device/emulator configuration, and USB driver installation when Android is selected \n Generates self-signed MSIX certificates using OpenSSL for local Windows app packaging and deploym

Essential syntax rules and pitfalls for Windows PowerShell scripting. \n \n Parentheses required around all cmdlet calls when using logical operators ( -or , -and ); missing them causes parsing errors \n Unicode and emoji characters prohibited in scripts; use ASCII-only alternatives like [OK] , [!] , [WARN] for status indicators \n Null checks mandatory before property access; always validate objects exist before calling methods or accessing properties \n JSON operations require explicit -Depth