devskill 2.0.6 → 2.0.8

package/skills/webapp-testing/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: webapp-testing
+description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+---
+
+# Web Application Testing
+
+This skill enables comprehensive testing and debugging of local web applications using Playwright automation.
+
+You should use the Playwright MCP Server to undertake the work if possible. If the MCP Server is unavailable, you can run the code in a local Node.js environment with Playwright installed.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+
+- Test frontend functionality in a real browser
+- Verify UI behavior and interactions
+- Debug web application issues
+- Capture screenshots for documentation or debugging
+- Inspect browser console logs
+- Validate form submissions and user flows
+- Check responsive design across viewports
+
+## Prerequisites
+
+- Node.js installed on the system
+- A locally running web application (or accessible URL)
+- Playwright will be installed automatically if not present
+
+## Core Capabilities
+
+### 1. Browser Automation
+
+- Navigate to URLs
+- Click buttons and links
+- Fill form fields
+- Select dropdowns
+- Handle dialogs and alerts
+
+### 2. Verification
+
+- Assert element presence
+- Verify text content
+- Check element visibility
+- Validate URLs
+- Test responsive behavior
+
+### 3. Debugging
+
+- Capture screenshots
+- View console logs
+- Inspect network requests
+- Debug failed tests
+
+## Usage Examples
+
+### Example 1: Basic Navigation Test
+
+```javascript
+// Navigate to a page and verify title
+await page.goto("http://localhost:3000");
+const title = await page.title();
+console.log("Page title:", title);
+```
+
+### Example 2: Form Interaction
+
+```javascript
+// Fill out and submit a form
+await page.fill("#username", "testuser");
+await page.fill("#password", "password123");
+await page.click('button[type="submit"]');
+await page.waitForURL("**/dashboard");
+```
+
+### Example 3: Screenshot Capture
+
+```javascript
+// Capture a screenshot for debugging
+await page.screenshot({ path: "debug.png", fullPage: true });
+```
+
+## Guidelines
+
+1. **Always verify the app is running** - Check that the local server is accessible before running tests
+2. **Use explicit waits** - Wait for elements or navigation to complete before interacting
+3. **Capture screenshots on failure** - Take screenshots to help debug issues
+4. **Clean up resources** - Always close the browser when done
+5. **Handle timeouts gracefully** - Set reasonable timeouts for slow operations
+6. **Test incrementally** - Start with simple interactions before complex flows
+7. **Use selectors wisely** - Prefer data-testid or role-based selectors over CSS classes
+
+## Common Patterns
+
+### Pattern: Wait for Element
+
+```javascript
+await page.waitForSelector("#element-id", { state: "visible" });
+```
+
+### Pattern: Check if Element Exists
+
+```javascript
+const exists = (await page.locator("#element-id").count()) > 0;
+```
+
+### Pattern: Get Console Logs
+
+```javascript
+page.on("console", (msg) => console.log("Browser log:", msg.text()));
+```
+
+### Pattern: Handle Errors
+
+```javascript
+try {
+  await page.click("#button");
+} catch (error) {
+  await page.screenshot({ path: "error.png" });
+  throw error;
+}
+```
+
+## Limitations
+
+- Requires Node.js environment
+- Cannot test native mobile apps (use React Native Testing Library instead)
+- May have issues with complex authentication flows
+- Some modern frameworks may require specific configuration
+
+## Helper Functions
+
+Some helper functions are available in [`test-helper.js`](./assets/test-helper.js) to simplify common tasks like waiting for elements, capturing screenshots, and handling errors. You can import and use these functions in your tests to improve readability and maintainability.

package/skills/webapp-testing/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/webapp-testing`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/webapp-testing/assets/test-helper.js

@@ -0,0 +1,56 @@
+/**
+ * Helper utilities for web application testing with Playwright
+ */
+
+/**
+ * Wait for a condition to be true with timeout
+ * @param {Function} condition - Function that returns boolean
+ * @param {number} timeout - Timeout in milliseconds
+ * @param {number} interval - Check interval in milliseconds
+ */
+async function waitForCondition(condition, timeout = 5000, interval = 100) {
+  const startTime = Date.now();
+  while (Date.now() - startTime < timeout) {
+    if (await condition()) {
+      return true;
+    }
+    await new Promise(resolve => setTimeout(resolve, interval));
+  }
+  throw new Error('Condition not met within timeout');
+}
+
+/**
+ * Capture browser console logs
+ * @param {Page} page - Playwright page object
+ * @returns {Array} Array of console messages
+ */
+function captureConsoleLogs(page) {
+  const logs = [];
+  page.on('console', msg => {
+    logs.push({
+      type: msg.type(),
+      text: msg.text(),
+      timestamp: new Date().toISOString()
+    });
+  });
+  return logs;
+}
+
+/**
+ * Take screenshot with automatic naming
+ * @param {Page} page - Playwright page object
+ * @param {string} name - Base name for screenshot
+ */
+async function captureScreenshot(page, name) {
+  const timestamp = new Date().toISOString().replace(/[:.]/g, '-');
+  const filename = `${name}-${timestamp}.png`;
+  await page.screenshot({ path: filename, fullPage: true });
+  console.log(`Screenshot saved: ${filename}`);
+  return filename;
+}
+
+module.exports = {
+  waitForCondition,
+  captureConsoleLogs,
+  captureScreenshot
+};

package/skills/what-context-needed/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/what-context-needed/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: what-context-needed
+description: 'Ask Copilot what files it needs to see before answering a question'
+---
+
+# What Context Do You Need?
+
+Before answering my question, tell me what files you need to see.
+
+## My Question
+
+{{question}}
+
+## Instructions
+
+1. Based on my question, list the files you would need to examine
+2. Explain why each file is relevant
+3. Note any files you've already seen in this conversation
+4. Identify what you're uncertain about
+
+## Output Format
+
+```markdown
+## Files I Need
+
+### Must See (required for accurate answer)
+- `path/to/file.ts` — [why needed]
+
+### Should See (helpful for complete answer)
+- `path/to/file.ts` — [why helpful]
+
+### Already Have
+- `path/to/file.ts` — [from earlier in conversation]
+
+### Uncertainties
+- [What I'm not sure about without seeing the code]
+```
+
+After I provide these files, I'll ask my question again.

package/skills/what-context-needed/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/what-context-needed`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/winapp-cli/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/winapp-cli/SKILL.md

@@ -0,0 +1,217 @@
+---
+name: winapp-cli
+description: 'Windows App Development CLI (winapp) for building, packaging, and deploying Windows applications. Use when asked to initialize Windows app projects, create MSIX packages, generate AppxManifest.xml, manage development certificates, add package identity for debugging, sign packages, publish to the Microsoft Store, create external catalogs, or access Windows SDK build tools. Supports .NET (csproj), C++, Electron, Rust, Tauri, and cross-platform frameworks targeting Windows.'
+---
+
+# Windows App Development CLI
+
+The Windows App Development CLI (`winapp`) is a command-line interface for managing Windows SDKs, MSIX packaging, generating app identity, manifests, certificates, and using build tools with any app framework. It bridges the gap between cross-platform development and Windows-native capabilities.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+
+- Initialize a Windows app project with SDK setup, manifests, and certificates
+- Create MSIX packages from application directories
+- Generate or manage AppxManifest.xml files
+- Create and install development certificates for signing
+- Add package identity for debugging Windows APIs
+- Sign MSIX packages or executables
+- Access Windows SDK build tools from any framework
+- Build Windows apps using cross-platform frameworks (Electron, Rust, Tauri, Qt)
+- Set up CI/CD pipelines for Windows app deployment
+- Access Windows APIs that require package identity (notifications, Windows AI, shell integration)
+- Publish apps to the Microsoft Store via `winapp store`
+- Create external catalogs for asset management
+- Set up .NET (csproj) projects with Windows App SDK via NuGet
+
+## Prerequisites
+
+- Windows 10 or later
+- winapp CLI installed via one of these methods:
+  - **WinGet**: `winget install Microsoft.WinAppCli --source winget`
+  - **NPM** (for Electron): `npm install @microsoft/winappcli --save-dev`
+  - **GitHub Actions/Azure DevOps**: Use [setup-WinAppCli](https://github.com/microsoft/setup-WinAppCli) action
+  - **Manual**: Download from [GitHub Releases](https://github.com/microsoft/WinAppCli/releases/latest)
+
+## Core Capabilities
+
+### 1. Project Initialization (`winapp init`)
+
+Initialize a directory with required assets (manifest, certificates, libraries) for building a modern Windows app. Supports SDK installation modes: `stable`, `preview`, `experimental`, or `none`.
+
+### 2. MSIX Packaging (`winapp pack`)
+
+Create MSIX packages from prepared directories with optional signing, certificate generation, and self-contained deployment bundling.
+
+### 3. Package Identity for Debugging (`winapp create-debug-identity`)
+
+Add temporary package identity to executables for debugging Windows APIs that require identity (notifications, Windows AI, shell integration) without full packaging.
+
+### 4. Manifest Management (`winapp manifest`)
+
+Generate AppxManifest.xml files and update image assets from source images, automatically creating all required sizes and aspect ratios. Supports manifest placeholders for dynamic content and qualified names in AppxManifest for flexible app identity definitions.
+
+### 5. Certificate Management (`winapp cert`)
+
+Generate development certificates and install them to the local machine store for signing packages.
+
+### 6. Package Signing (`winapp sign`)
+
+Sign MSIX packages and executables with PFX certificates, with optional timestamp server support.
+
+### 7. SDK Build Tools Access (`winapp tool`)
+
+Run Windows SDK build tools with properly configured paths from any framework or build system.
+
+### 8. Microsoft Store Integration (`winapp store`)
+
+Run Microsoft Store Developer CLI commands directly from winapp, enabling store submission, package validation, and publishing workflows without leaving the CLI.
+
+### 9. External Catalog Creation (`winapp create-external-catalog`)
+
+Create external catalogs to streamline asset management for developers, separating catalog data from the main package.
+
+## Usage Examples
+
+### Example 1: Initialize and Package a Windows App
+
+```bash
+# Initialize workspace with defaults
+winapp init
+# Note: init no longer auto-generates a certificate (v0.2.0+). Generate one explicitly:
+winapp cert generate
+
+# Build your application (framework-specific)
+# ...
+
+# Create signed MSIX package
+winapp pack ./build-output --generate-cert --output MyApp.msix
+```
+
+### Example 2: Debug with Package Identity
+
+```bash
+# Add debug identity to executable for testing Windows APIs
+winapp create-debug-identity ./bin/MyApp.exe
+
+# Run your app - it now has package identity
+./bin/MyApp.exe
+```
+
+### Example 3: CI/CD Pipeline Setup
+
+```yaml
+# GitHub Actions example
+- name: Setup winapp CLI
+  uses: microsoft/setup-WinAppCli@v1
+
+- name: Initialize and Package
+  run: |
+    winapp init --no-prompt
+    winapp pack ./build-output --output MyApp.msix
+```
+
+### Example 4: Electron App Integration
+
+```bash
+# Install via npm
+npm install @microsoft/winappcli --save-dev
+
+# Initialize and add debug identity for Electron
+npx winapp init
+npx winapp node add-electron-debug-identity
+
+# Package for distribution
+npx winapp pack ./out --output MyElectronApp.msix
+```
+
+## Guidelines
+
+1. **Run `winapp init` first** - Always initialize your project before using other commands to ensure SDK setup and manifest are configured. Note: as of v0.2.0, `winapp init` no longer generates a development certificate automatically. Run `winapp cert generate` explicitly when you need to sign with a dev certificate.
+2. **Re-run `create-debug-identity` after manifest changes** - Package identity must be recreated whenever AppxManifest.xml is modified.
+3. **Use `--no-prompt` for CI/CD** - Prevents interactive prompts in automated pipelines by using default values.
+4. **Use `winapp restore` for shared projects** - Recreates the exact environment state defined in `winapp.yaml` across machines.
+5. **Generate assets from a single image** - Use `winapp manifest update-assets` with one logo to generate all required icon sizes.
+
+## Common Patterns
+
+### Pattern: Initialize New Project
+
+```bash
+cd my-project
+winapp init
+# Creates: AppxManifest.xml, SDK configuration, winapp.yaml
+# Note: .NET (csproj) projects skip winapp.yaml and configure NuGet packages in the .csproj directly
+
+# Generate a dev signing certificate explicitly (no longer done by init)
+winapp cert generate
+```
+
+### Pattern: Package with Existing Certificate
+
+```bash
+winapp pack ./build-output --cert ./mycert.pfx --cert-password secret --output MyApp.msix
+```
+
+### Pattern: Self-Contained Deployment
+
+```bash
+# Bundle Windows App SDK runtime with the package
+winapp pack ./my-app --self-contained --generate-cert
+```
+
+### Pattern: Update Package Versions
+
+```bash
+# Update to latest stable SDKs
+winapp update
+
+# Or update to preview SDKs
+winapp update --setup-sdks preview
+```
+
+## Limitations
+
+- Windows 10 or later required (Windows-only CLI)
+- Package identity debugging requires re-running `create-debug-identity` after any manifest changes
+- Self-contained deployment increases package size by bundling the Windows App SDK runtime
+- Development certificates are for testing only; production requires trusted certificates
+- Some Windows APIs require specific capability declarations in the manifest
+- `winapp init` no longer auto-generates a certificate (v0.2.0+); run `winapp cert generate` explicitly
+- .NET (csproj) projects skip `winapp.yaml`; SDK packages are configured in the project file directly
+- winapp CLI uses the NuGet global cache for packages (not `%userprofile%/.winapp/packages`)
+- winapp CLI is in public preview and subject to change
+
+## Windows APIs Enabled by Package Identity
+
+Package identity unlocks access to powerful Windows APIs:
+
+| API Category | Examples |
+| ------------ | -------- |
+| **Notifications** | Interactive native notifications, notification management |
+| **Windows AI** | On-device LLM, text/image AI APIs (Phi Silica, Windows ML) |
+| **Shell Integration** | Explorer, Taskbar, Share sheet integration |
+| **Protocol Handlers** | Custom URI schemes (`yourapp://`) |
+| **Device Access** | Camera, microphone, location (with consent) |
+| **Background Tasks** | Run when app is closed |
+| **File Associations** | Open file types with your app |
+
+## Troubleshooting
+
+| Issue | Solution |
+| ----- | -------- |
+| Certificate not trusted | Run `winapp cert install <cert-path>` to install to local machine store |
+| Package identity not working | Run `winapp create-debug-identity` after any manifest changes |
+| SDK not found | Run `winapp restore` or `winapp update` to ensure SDKs are installed |
+| Signing fails | Verify certificate password and ensure cert is not expired |
+
+## References
+
+- [GitHub Repository](https://github.com/microsoft/WinAppCli)
+- [Full CLI Documentation](https://github.com/microsoft/WinAppCli/blob/main/docs/usage.md)
+- [.NET Project Guide](https://github.com/microsoft/WinAppCli/blob/main/docs/guides/dotnet.md)
+- [Sample Applications](https://github.com/microsoft/WinAppCli/tree/main/samples)
+- [Windows App SDK](https://learn.microsoft.com/windows/apps/windows-app-sdk/)
+- [MSIX Packaging Overview](https://learn.microsoft.com/windows/msix/overview)
+- [Package Identity Overview](https://learn.microsoft.com/windows/apps/desktop/modernize/package-identity-overview)

package/skills/winapp-cli/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/winapp-cli`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/winmd-api-search/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/winmd-api-search/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) Microsoft Corporation. All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.