dotnet-uno-targets

Provide per-target deployment, debugging, and packaging guidance for Uno Platform applications.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-uno-targets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-uno-targets
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-uno-targets
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-uno-targets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance for deploying Uno Platform applications across a wide array of target platforms, addressing platform-specific challenges and configurations.

Core Features & Use Cases

  • Per-Target Deployment Guidance: Detailed instructions for Web/WASM, iOS, Android, macOS, Windows, Linux, and Embedded targets.
  • Debugging & Packaging: Covers setup, debugging workflows, and packaging/distribution strategies for each platform.
  • Platform-Specific Gotchas: Highlights unique constraints, AOT/trimming implications, and behavioral differences across targets.
  • Use Case: A developer needs to understand how to package and debug their Uno Platform app for both iOS and WebAssembly, including specific considerations for each.

Quick Start

Consult the Web/WASM section for instructions on publishing your Uno Platform application for web deployment.

Frequently Asked Questions about dotnet-uno-targets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish and debug an Uno Platform app for WebAssembly?

To publish and debug an Uno Platform app for WebAssembly (WASM), you follow specific project setup and debugging workflows. This includes configuring the project for web deployment and applying appropriate packaging strategies for the WASM target.

What are the common platform-specific gotchas when deploying Uno Platform apps to iOS and Android?

Common Uno Platform deployment gotchas for iOS and Android include unique platform constraints and behavioral differences. You must address platform-specific configurations, debugging workflows, and packaging strategies tailored to each mobile environment to ensure proper functionality.

Does deploying Uno Platform applications to Linux and macOS require special packaging strategies?

Deploying Uno Platform applications to Linux and macOS requires specific packaging strategies and platform-specific guidance. You must configure your project setup to accommodate the distinct behavioral differences and constraints of these desktop targets.

How do AOT and trimming implications affect cross-platform Uno Platform deployment?

AOT and trimming implications affect Uno Platform deployment by altering application behavior and size across targets. You must understand these constraints to properly configure debugging workflows and packaging strategies for Web/WASM, iOS, Android, and other platforms.

What is the best way to set up an Uno Platform project for multiple cross-platform targets?

The best way to set up an Uno Platform project for multiple cross-platform targets is to follow per-target deployment guidance. This approach addresses specific project setup, debugging workflows, and packaging strategies for Web/WASM, iOS, Android, macOS, Windows, Linux, and embedded targets.