skilly. Buy ad slot
All skills
Frontend · Testing · Dotnet / AGENT SKILL

tree

jonathanpeppers/vibe-wpf
0 installs 9 GitHub stars
0

Inspect the visual tree of a running WPF application to understand and debug its UI.
Get the visual tree structure of the running WPF application. Use this skill when asked to inspect, debug, or understand the element hierarchy, control structure, or layout of the WPF UI.

BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Not yet assessed

Review the original instructions and requested permissions before installing.

No security review is available for this catalog entry yet.

SKILL QUALITY

Not yet assessed

How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.

No quality assessment is available for this catalog entry yet.

The full skill.

Original instructions from the publisher’s SKILL.md

# Vibe Visual Tree Skill

This skill retrieves the complete WPF visual tree as JSON, showing all UI elements, their types, names, and hierarchy.

## When to Use

Use this skill when:
- Inspecting the structure of the WPF UI
- Finding element names for automation or testing
- Debugging layout or control hierarchy issues
- Understanding how controls are nested
- Verifying that elements exist in the visual tree

## Prerequisites

The WPF application must be running with the VibeServer extension. Start it with:
```powershell
cd MyWpfApp
dotnet watch run
```

## Usage

Run the script from the repository root:
```powershell
.\.github\skills\vibe-tree\get-tree.ps1
```

## Output

Returns a JSON representation of the visual tree with:
- Element type (e.g., `Button`, `TextBlock`, `Grid`)
- Element name (x:Name attribute)
- Child elements (nested hierarchy)

Example output:
```json
{
  "Type": "MainWindow",
  "Name": "mainWindow",
  "Children": [
    {
      "Type": "Grid",
      "Name": "rootGrid",
      "Children": [...]
    }
  ]
}
```

## Workflow Integration

Use this skill alongside vibe-screenshot to:
1. Capture a screenshot to see the visual appearance
2. Get the tree to understand the element structure
3. Make targeted XAML changes based on element names

Skill folder

Files included alongside SKILL.md in the publisher’s repository.