uno-extensions-services

Configure hosting, DI, authentication, HTTP, configuration, and logging for Uno Platform apps.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill uno-extensions-services
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uno-extensions-services
Source: https://github.com/mtmattei/UnoPlatformSkills/tree/main/uno-extensions-services
Command: npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill uno-extensions-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Patterns and guidance to standardize hosting, dependency injection, authentication, HTTP clients, configuration, logging, and storage in Uno Platform apps, reducing boilerplate and ensuring consistent bootstrapping.

Core Features & Use Cases

  • Hosting and DI patterns for reliable startup, including service registration best practices, TryAdd, and named services.
  • Authentication and HTTP infrastructure using Uno.Extensions for MSAL/OIDC, configuration-driven clients, and unified token handling.
  • HTTP client configuration with Kiota or Refit and appsettings-based endpoints, plus optional native handlers.
  • Centralized configuration and logging patterns with embedded appsettings, IOptions, IWritableOptions, and Serilog support.
  • Shared storage/configuration scaffolding and cross-cutting concerns to simplify feature wiring across projects.

Quick Start

Define and apply Uno.Extensions hosting, DI, authentication, HTTP, configuration, and logging patterns to bootstrap your Uno Platform app.

Frequently Asked Questions about uno-extensions-services

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

FAQPage Schema
How do I configure dependency injection and hosting in a Uno Platform app?

Configure Uno Platform hosting and dependency injection by applying standardized bootstrapping patterns for service registration, environment-aware setup, and reliable startup. This reduces boilerplate and ensures consistent DI wiring across WinUI and .NET projects.

What is the best way to wire up authentication in Uno Platform using MSAL or OIDC?

Wire up authentication in Uno Platform using Uno.Extensions to implement MSAL or OIDC flows with unified token handling. This approach standardizes auth infrastructure and simplifies secure login integration across your cross-platform targets.

How do I set up HTTP clients with Refit or Kiota in a .NET cross-platform app?

Set up HTTP clients in a .NET cross-platform app by using configuration-driven endpoints from appsettings with Refit or Kiota. This pattern standardizes client registration and supports adding optional native handlers for platform-specific network requirements.

Can I use IOptions and Serilog for centralized configuration and logging in Uno Platform?

Yes, you can use IOptions and Serilog for centralized configuration and logging in Uno Platform. The pattern leverages embedded appsettings files and IWritableOptions to provide structured logging integration and typed settings across your application.

Does this Uno.Extensions configuration approach support named services and factories for DI?

Yes, the Uno.Extensions configuration approach supports service registration best practices including TryAdd, named services, and factories. This allows precise dependency injection control and flexible service resolution during app bootstrap.

Why should I standardize app bootstrapping patterns for Uno Platform?

Standardizing app bootstrapping patterns for Uno Platform eliminates inconsistent service wiring and infrastructure setup. It ensures reliable startup by applying unified patterns for hosting, DI, HTTP clients, configuration, and logging across WinUI and .NET projects.