@fprad0/skill-master-mcp 0.0.9 → 0.0.11

package/docs/skill-candidates/v0.0.10/webapp-testing/examples/static_html_automation.py

@@ -0,0 +1,33 @@
+from playwright.sync_api import sync_playwright
+import os
+
+# Example: Automating interaction with static HTML files using file:// URLs
+
+html_file_path = os.path.abspath('path/to/your/file.html')
+file_url = f'file://{html_file_path}'
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True)
+    page = browser.new_page(viewport={'width': 1920, 'height': 1080})
+
+    # Navigate to local HTML file
+    page.goto(file_url)
+
+    # Take screenshot
+    page.screenshot(path='/mnt/user-data/outputs/static_page.png', full_page=True)
+
+    # Interact with elements
+    page.click('text=Click Me')
+    page.fill('#name', 'John Doe')
+    page.fill('#email', 'john@example.com')
+
+    # Submit form
+    page.click('button[type="submit"]')
+    page.wait_for_timeout(500)
+
+    # Take final screenshot
+    page.screenshot(path='/mnt/user-data/outputs/after_submit.png', full_page=True)
+
+    browser.close()
+
+print("Static HTML automation completed!")

package/docs/skill-candidates/v0.0.10/webapp-testing/scripts/with_server.py

@@ -0,0 +1,106 @@
+#!/usr/bin/env python3
+"""
+Start one or more servers, wait for them to be ready, run a command, then clean up.
+
+Usage:
+    # Single server
+    python scripts/with_server.py --server "npm run dev" --port 5173 -- python automation.py
+    python scripts/with_server.py --server "npm start" --port 3000 -- python test.py
+
+    # Multiple servers
+    python scripts/with_server.py \
+      --server "cd backend && python server.py" --port 3000 \
+      --server "cd frontend && npm run dev" --port 5173 \
+      -- python test.py
+"""
+
+import subprocess
+import socket
+import time
+import sys
+import argparse
+
+def is_server_ready(port, timeout=30):
+    """Wait for server to be ready by polling the port."""
+    start_time = time.time()
+    while time.time() - start_time < timeout:
+        try:
+            with socket.create_connection(('localhost', port), timeout=1):
+                return True
+        except (socket.error, ConnectionRefusedError):
+            time.sleep(0.5)
+    return False
+
+
+def main():
+    parser = argparse.ArgumentParser(description='Run command with one or more servers')
+    parser.add_argument('--server', action='append', dest='servers', required=True, help='Server command (can be repeated)')
+    parser.add_argument('--port', action='append', dest='ports', type=int, required=True, help='Port for each server (must match --server count)')
+    parser.add_argument('--timeout', type=int, default=30, help='Timeout in seconds per server (default: 30)')
+    parser.add_argument('command', nargs=argparse.REMAINDER, help='Command to run after server(s) ready')
+
+    args = parser.parse_args()
+
+    # Remove the '--' separator if present
+    if args.command and args.command[0] == '--':
+        args.command = args.command[1:]
+
+    if not args.command:
+        print("Error: No command specified to run")
+        sys.exit(1)
+
+    # Parse server configurations
+    if len(args.servers) != len(args.ports):
+        print("Error: Number of --server and --port arguments must match")
+        sys.exit(1)
+
+    servers = []
+    for cmd, port in zip(args.servers, args.ports):
+        servers.append({'cmd': cmd, 'port': port})
+
+    server_processes = []
+
+    try:
+        # Start all servers
+        for i, server in enumerate(servers):
+            print(f"Starting server {i+1}/{len(servers)}: {server['cmd']}")
+
+            # Use shell=True to support commands with cd and &&
+            process = subprocess.Popen(
+                server['cmd'],
+                shell=True,
+                stdout=subprocess.PIPE,
+                stderr=subprocess.PIPE
+            )
+            server_processes.append(process)
+
+            # Wait for this server to be ready
+            print(f"Waiting for server on port {server['port']}...")
+            if not is_server_ready(server['port'], timeout=args.timeout):
+                raise RuntimeError(f"Server failed to start on port {server['port']} within {args.timeout}s")
+
+            print(f"Server ready on port {server['port']}")
+
+        print(f"\nAll {len(servers)} server(s) ready")
+
+        # Run the command
+        print(f"Running: {' '.join(args.command)}\n")
+        result = subprocess.run(args.command)
+        sys.exit(result.returncode)
+
+    finally:
+        # Clean up all servers
+        print(f"\nStopping {len(server_processes)} server(s)...")
+        for i, process in enumerate(server_processes):
+            try:
+                process.terminate()
+                process.wait(timeout=5)
+            except subprocess.TimeoutExpired:
+                process.kill()
+                process.wait()
+            print(f"Server {i+1} stopped")
+        print("All servers stopped")
+
+
+if __name__ == '__main__':
+    main()

package/docs/skill-candidates/v0.0.10/winui-app/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/docs/skill-candidates/v0.0.10/winui-app/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: winui-app
+description: Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.
+---
+
+# WinUI App
+
+Use this skill for WinUI 3 and Windows App SDK work that needs grounded setup guidance, app bootstrap, modern Windows UX decisions, or concrete implementation patterns.
+
+## Required Flow
+
+1. Classify the task as environment/setup, new-app bootstrap, design, implementation, review, or troubleshooting.
+2. If the task is about preparing a machine for WinUI, auditing readiness, or creating a brand new app, start with the bundled setup-and-scaffold flow in this skill before broader design, implementation, or troubleshooting work:
+   - Pick the app name when the request is for a new app.
+   - Use the exact name the user gave when it is already a safe folder name.
+   - If the user did not give a name, derive a short PascalCase name from the request and state what you chose.
+   - Create the project in the user's current workspace unless they asked for another location.
+   - Do not use `--force` unless the user explicitly asked to overwrite existing files.
+   - Run the bundled WinGet configuration from the skill directory so the relative path stays exactly `config.yaml`:
+
+```powershell
+winget configure -f config.yaml --accept-configuration-agreements --disable-interactivity
+```
+
+   - Treat the configuration as intended to enable Developer Mode, install or update Visual Studio Community 2026, and install the Managed Desktop, Universal, and Windows App SDK C# components needed for WinUI development.
+   - Assess the configuration result before continuing. Continue on success. If it fails, inspect the output instead of guessing. If the `winui` template is already available and the toolchain is usable, note the partial failure and continue. If prerequisites are still missing, stop and report the blocker clearly.
+   - Verify the template is available before scaffolding:
+
+```powershell
+dotnet new list winui
+```
+
+   - For diagnostics-only environment requests, explain that the bundled bootstrap may change the machine and get confirmation before running it. If the user declines changes, use the manual verification guidance in `references/foundation-environment-audit-and-remediation.md` and summarize readiness under `present`, `missing`, `uncertain`, and `recommended optional tools`.
+   - For a brand new app, scaffold with `dotnet new winui -o <name>`. Add template options only when the user asked for them. Supported options: `-f|--framework net10.0|net9.0|net8.0`, `-slnx|--use-slnx`, `-cpm|--central-pkg-mgmt`, `-mvvm|--use-mvvm`, `-imt|--include-mvvm-toolkit`, `-un|--unpackaged`, `-nsf|--no-solution-file`, `--force`. Do not invent unsupported flags. If the user asks for packaged behavior, pass `--unpackaged false`. Otherwise keep the template default.
+   - Verify a new scaffold by confirming the expected project file exists and running `dotnet build` against the generated `.csproj`.
+   - Launch a newly scaffolded app through the correct path for its actual packaging model and confirm there is a real top-level window instead of relying only on the launcher process exit code.
+3. Read `references/_sections.md`, then load only the reference files that match the task.
+4. Make the packaging model explicit before creating or refactoring the app. Default to packaged for Store-like product workflows and Visual Studio deploy/F5 flows. Default to unpackaged when the user expects repeatable CLI build-and-run loops or direct `.exe` launches after each change.
+5. When the task is an opaque XAML compiler failure such as `MSB3073` or `XamlCompiler.exe`, read `references/foundation-template-first-recovery.md` and simplify back toward the current `dotnet new winui` scaffold for the chosen packaging model before inventing custom recovery structure.
+6. For any work that creates or changes a WinUI app, make a complete but minimal edit set, then build the app and run it before responding to the user. Do this by default even when the user did not explicitly ask for verification. If a running app instance locks the output while more work remains, stop it, rebuild, relaunch, and continue verification. When the work is complete and launch verification succeeds, leave the final verified app instance running for the user unless they explicitly asked you not to.
+7. Treat launch verification as incomplete until the app shows objective success signals such as a responsive top-level window, expected window title, or other clear startup behavior. A spawned process by itself is not enough.
+8. Prefer Microsoft Learn for requirements, API expectations, and platform guidance.
+9. Prefer WinUI Gallery for concrete control usage, shell composition, and design details.
+10. Prefer WindowsAppSDK-Samples for scenario-level APIs such as windowing, lifecycle, notifications, deployment, and custom controls.
+11. Build toward WinUI and Fluent guidance first. Treat native WinUI shells, controls, interactions, and control chrome as the default implementation path.
+12. For grouped command surfaces such as document actions, editor formatting, view toggles, or page-level toolbars, favor a native `CommandBar` or other stock WinUI command surface before building a custom row with `Grid`, `StackPanel`, `Border`, or ad hoc button groupings.
+13. Do not invent app-specific controls, bespoke component libraries, or custom chrome to replace stock WinUI behavior unless the user explicitly asks for that customization, the existing product design system already requires it, or a verified platform gap leaves no clean native option.
+14. When customization is needed, first compose, template, or restyle built-in WinUI controls and system resources before adding CommunityToolkit dependencies or authoring a new custom control.
+15. Use CommunityToolkit only when built-in WinUI controls or helpers do not cover the need cleanly.
+16. Support both light and dark mode by default. Treat single-theme output as an exception that requires an explicit user request or an existing product constraint.
+17. Use theme-aware resources, system brushes, and WinUI styling hooks instead of hard-coded light-only or dark-only colors when building or revising UI.
+18. Make scroll ownership explicit for collection layouts. When a page already scrolls vertically, do not assume a nested `GridView` or other scroll-owning collection will still render a horizontal poster rail correctly.
+19. Do not add extra `Border` wrappers around sections, lists, or cards unless the border is doing distinct work that the contained control or parent surface does not already provide. Avoid "double-card" compositions where a section `Border` wraps child items that already render as cards.
+20. Treat responsiveness as a shell-plus-page problem, not only a control-resize problem. Plan explicit wide, medium, and phone-width behavior for navigation, padding, content density, and footer/tool regions, and simplify or hide nonessential UI as width shrinks.
+
+## Common Routes
+
+| Request | Read first |
+| --- | --- |
+| Check whether this PC can build WinUI apps | `references/foundation-environment-audit-and-remediation.md` |
+| Install missing WinUI prerequisites | `references/foundation-environment-audit-and-remediation.md` |
+| Start a new packaged or unpackaged app | `references/foundation-setup-and-project-selection.md` |
+| Recover from opaque XAML compiler or startup failures while staying anchored to the template scaffold | `references/foundation-template-first-recovery.md` |
+| Build, run, or verify that a WinUI app actually launched | `references/build-run-and-launch-verification.md` |
+| Review app structure, pages, resources, and bindings | `references/foundation-winui-app-structure.md` |
+| Choose shell, navigation, title bar, or multi-window patterns | `references/shell-navigation-and-windowing.md` |
+| Choose controls or responsive layout patterns | `references/controls-layout-and-adaptive-ui.md` |
+| Apply Mica, theming, typography, icons, or Fluent styling | `references/styling-theming-materials-and-icons.md` |
+| Improve accessibility, keyboarding, or localization | `references/accessibility-input-and-localization.md` |
+| Diagnose responsiveness or UI-thread performance | `references/performance-diagnostics-and-responsiveness.md` |
+| Decide whether to use CommunityToolkit | `references/community-toolkit-controls-and-helpers.md` |
+| Handle lifecycle, notifications, or deployment | `references/windows-app-sdk-lifecycle-notifications-and-deployment.md` |
+| Run a review checklist | `references/testing-debugging-and-review-checklists.md` |
+
+## Environment Rules
+
+- Do not guess whether the machine is ready for WinUI development. Verify it.
+- Use the bundled setup-and-scaffold flow in this skill for fresh setup, remediation, and first-project scaffolding instead of delegating to another skill.
+- Treat `config.yaml` in this skill directory as the bundled bootstrap source of truth.
+- Treat uncertain environment signals as uncertain, not as success.
+- If the task is audit-only and the user declines machine changes, use the manual verification guidance in `references/foundation-environment-audit-and-remediation.md` and keep uncertain signals explicit instead of implying success.
+- If `config.yaml` is missing, say so clearly and fall back to the official Microsoft workflow instead of pretending the bundled path exists.
+- Keep environment readiness, packaging choice, and application startup verification as separate checks. Passing one does not prove the others.
+- Fail closed on ambiguous launch results. If the app did not clearly open, keep debugging.
+- After creating or editing a WinUI app, do not stop at a successful build. Launch the app, confirm objective startup behavior, and leave the final verified app instance running before returning control to the user unless they explicitly say not to run it.
+
+## Reference Rules
+
+- Keep C# as the primary path. Mention C++ or C++/WinRT only when the difference is material.
+- Preserve the conventions of an existing codebase instead of forcing a generic sample structure onto it.
+- Treat WinUI design guidance and native controls as the baseline. Do not drift into bespoke component systems or app-specific replacements for standard controls unless the user explicitly requests them or the existing codebase already depends on them.
+- Support light and dark mode by default for app UI work unless the user explicitly asks for a single-theme result or the product already enforces one.
+- Favor built-in WinUI controls and system styling hooks before adding CommunityToolkit dependencies, custom controls, or app-specific surface systems.
+- Put detailed control, theming, shell, scrolling, responsiveness, packaging, and recovery guidance in the matching reference files instead of duplicating those rules here.

package/docs/skill-candidates/v0.0.10/winui-app/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "WinUI App"
+  short_description: "[Windows only] Build native WinUI 3 apps"
+  icon_large: "./assets/winui.png"
+  default_prompt: "Create a new $winui-app desktop app for me."

package/docs/skill-candidates/v0.0.10/winui-app/config.yaml

@@ -0,0 +1,50 @@
+# yaml-language-server: $schema=https://aka.ms/configuration-dsc-schema/0.2
+
+##################################################################################################################################
+# This configuration installs the tools needed to get started building Windows apps with WinUI.                                  #
+#                                                                                                                                #
+# This will:                                                                                                                     #
+#   * Enable Developer Mode                                                                                                      #
+#   * Install Visual Studio Community 2026                                                                                       #
+#   * Install the WinUI / Windows App SDK workloads                                                                              #
+##################################################################################################################################
+properties:
+  assertions:
+    - resource: Microsoft.Windows.Developer/OsVersion
+      directives:
+        description: Verify min OS version requirement
+        allowPrerelease: true
+      settings:
+        MinVersion: '10.0.17763'
+  resources:
+    - resource: Microsoft.Windows.Settings/WindowsSettings
+      directives:
+        description: Enable Developer Mode
+        securityContext: elevated
+        allowPrerelease: true
+      settings:
+        DeveloperMode: true
+    - resource: Microsoft.WinGet.DSC/WinGetPackage
+      id: Visual Studio
+      directives:
+        description: Install Visual Studio Community 2026
+        securityContext: elevated
+      settings:
+        id: Microsoft.VisualStudio.Community
+        source: winget
+    - resource: Microsoft.VisualStudio.DSC/VSComponents
+      id: Workloads ManagedDesktop
+      dependsOn:
+        - Visual Studio
+      directives:
+        description: Install required VS workloads (ManagedDesktop, Windows App SDK)
+        allowPrerelease: true
+        securityContext: elevated
+      settings:
+        productId: Microsoft.VisualStudio.Product.Community
+        channelId: VisualStudio.18.Release
+        components:
+          - Microsoft.VisualStudio.Workload.ManagedDesktop
+          - Microsoft.VisualStudio.Workload.Universal
+          - Microsoft.VisualStudio.ComponentGroup.WindowsAppSDK.Cs
+  configurationVersion: 0.2.0

package/docs/skill-candidates/v0.0.10/winui-app/references/_sections.md

@@ -0,0 +1,96 @@
+# Reference Sections
+
+Use this index to choose the narrowest reference file that fits the current task.
+
+## 1. Foundations
+
+- `foundation-setup-and-project-selection.md`
+  - Priority: CRITICAL
+  - Use for first-project setup, packaged vs unpackaged decisions, and core WinUI prerequisites.
+  - Authority: Microsoft Learn WinUI and Windows App SDK setup docs.
+
+- `foundation-environment-audit-and-remediation.md`
+  - Priority: CRITICAL
+  - Use for machine readiness checks, missing prerequisites, and guided remediation.
+  - Authority: Microsoft Learn setup and system requirements docs, plus the bundled bootstrap workflow.
+
+- `foundation-winui-app-structure.md`
+  - Priority: HIGH
+  - Use for solution layout, shell composition, resources, bindings, and C#-first project structure.
+  - Authority: WinUI Gallery source plus Learn XAML guidance.
+
+- `foundation-template-first-recovery.md`
+  - Priority: CRITICAL
+  - Use for opaque `MSB3073`, `XamlCompiler.exe`, and startup failures that should be recovered by comparing against a fresh `dotnet new winui` scaffold instead of applying alternate baseline files.
+  - Authority: Learn packaged and unpackaged deployment guidance plus recurring template-first recovery patterns.
+
+- `build-run-and-launch-verification.md`
+  - Priority: CRITICAL
+  - Use for build/run workflows, actual launch verification, startup crashes, and packaged-vs-unpackaged local execution choices.
+  - Authority: Learn setup and deployment guidance plus recurring WinUI troubleshooting patterns.
+
+## 2. Shell, Navigation, and Windowing
+
+- `shell-navigation-and-windowing.md`
+  - Priority: HIGH
+  - Use for `NavigationView`, page shells, title bars, `AppWindow`, and multi-window design.
+  - Authority: Learn design guidance, WinUI Gallery samples, Windows App SDK Windowing samples.
+
+## 3. Controls, Layout, and Adaptive UI
+
+- `controls-layout-and-adaptive-ui.md`
+  - Priority: HIGH
+  - Use for control selection, command surfaces, responsive layout, and page composition.
+  - Authority: Learn design guidance and WinUI Gallery control pages.
+
+## 4. Styling, Theming, Materials, and Icons
+
+- `styling-theming-materials-and-icons.md`
+  - Priority: HIGH
+  - Use for Fluent styling, theme resources, Mica, Acrylic, typography, and iconography.
+  - Authority: Learn design/material docs, WinUI Gallery backdrop samples, Windows App SDK Mica samples.
+
+- `motion-animations-and-polish.md`
+  - Priority: MEDIUM
+  - Use for transitions, connected animation, subtle polish, and animation discipline.
+  - Authority: Learn motion guidance, WinUI Gallery transition samples, CommunityToolkit animations.
+
+## 5. Accessibility, Input, and Localization
+
+- `accessibility-input-and-localization.md`
+  - Priority: HIGH
+  - Use for keyboarding, Narrator, high contrast, automation properties, and localization concerns.
+  - Authority: Learn accessibility and globalization guidance, WinUI Gallery automation patterns.
+
+## 6. Performance and Diagnostics
+
+- `performance-diagnostics-and-responsiveness.md`
+  - Priority: HIGH
+  - Use for UI-thread responsiveness, large item collections, rendering cost, and diagnostic tooling.
+  - Authority: Learn WinUI performance docs and XAML frame analysis guidance.
+
+## 7. Windows App SDK Scenarios
+
+- `windows-app-sdk-lifecycle-notifications-and-deployment.md`
+  - Priority: HIGH
+  - Use for lifecycle, activation, notifications, packaged vs unpackaged deployment, and runtime initialization.
+  - Authority: Microsoft Learn Windows App SDK docs and WindowsAppSDK-Samples.
+
+## 8. CommunityToolkit Extensions
+
+- `community-toolkit-controls-and-helpers.md`
+  - Priority: MEDIUM
+  - Use when built-in WinUI controls are not enough and Toolkit packages might close the gap cleanly.
+  - Authority: CommunityToolkit/Windows packages and samples.
+
+## 9. Testing, Debugging, and Review
+
+- `testing-debugging-and-review-checklists.md`
+  - Priority: HIGH
+  - Use for final review passes, debugging workflows, and validation checklists.
+  - Authority: Learn tooling docs plus recurring WinUI review patterns.
+
+- `sample-source-map.md`
+  - Priority: MEDIUM
+  - Use when you need to know which canonical repo or doc to inspect first for a given task.
+  - Authority: Curated map across Learn, WinUI Gallery, WindowsAppSDK-Samples, and CommunityToolkit.

package/docs/skill-candidates/v0.0.10/winui-app/references/accessibility-input-and-localization.md

@@ -0,0 +1,51 @@
+---
+title: Accessibility, Input, and Localization
+priority: HIGH
+tags: accessibility, keyboard, narrator, automation, localization, high-contrast
+sources:
+  - https://learn.microsoft.com/windows/apps/design/accessibility/accessibility
+  - https://learn.microsoft.com/windows/apps/design/accessibility/keyboard-accessibility
+  - https://learn.microsoft.com/windows/apps/design/accessibility/high-contrast-themes
+  - https://learn.microsoft.com/windows/apps/design/globalizing/globalizing-portal
+  - https://github.com/microsoft/WinUI-Gallery
+---
+
+## What This Reference Is For
+
+Use this file for keyboard accessibility, Narrator support, automation properties, input parity, high contrast, and localization-ready UI.
+
+## Prefer
+
+- Accessible names, help text, and landmarks for meaningful UI elements.
+- Full keyboard reachability for the main workflow.
+- High-contrast-safe visuals.
+- Localizable strings and layouts that tolerate growth.
+- Equal support for mouse, touch, pen, and keyboard where the platform expects it.
+
+## Avoid
+
+- Icon-only interactions without accessible naming.
+- Focus traps, hidden tab stops, or keyboard-only dead ends.
+- Hard-coded strings in XAML or code-behind that block localization.
+- Text layouts that collapse when strings expand.
+
+## Guidance
+
+- Use automation properties intentionally.
+- Preserve visible focus and logical tab order.
+- Verify context menus, flyouts, and dialogs by keyboard as well as mouse.
+- Respect text scaling, contrast changes, and RTL where relevant.
+- Keep touch targets and spacing usable on both mouse and touch hardware.
+
+## WinUI Gallery Anchors
+
+- Accessibility-related control samples
+- Automation helper patterns in shell code
+- Standard WinUI controls that already expose useful accessibility behavior
+
+## Review Checklist
+
+- Can a keyboard-only user complete the task?
+- Does Narrator have enough information to describe the important UI?
+- Does the experience stay legible in high contrast?
+- Are strings and layout ready for localization and RTL growth?