← スキル一覧に戻る

tree
by jonathanpeppers
This is a sample for the "vibe code inner loop" seeing how we might leverage dotnet-watch & screenshots together to vibe.
⭐ 5🍴 0📅 2026年1月17日
SKILL.md
name: tree description: 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.
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:
cd MyWpfApp
dotnet watch run
Usage
Run the script from the repository root:
.\.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:
{
"Type": "MainWindow",
"Name": "mainWindow",
"Children": [
{
"Type": "Grid",
"Name": "rootGrid",
"Children": [...]
}
]
}
Workflow Integration
Use this skill alongside vibe-screenshot to:
- Capture a screenshot to see the visual appearance
- Get the tree to understand the element structure
- Make targeted XAML changes based on element names
スコア
総合スコア
70/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です