MAUI Base Template — Agent hub (`ConnectSoft.MauiBaseTemplate`)¶

Factory scope: Rules, symbols, and pitfalls for connectsoft-maui-base.
Canonical spec: ConnectSoft.Documentation — MAUI Base overview

Do / do not (summary)¶

Do	Do not
Require `--service-name` for any scaffold; it drives `MauiBase` → product renames	Assume `-n` alone renames projects — it only affects output folder when `preferNameDirectory` applies
Keep business logic in *`.Core`** with no `Microsoft.Maui.*` references	Move MAUI-dependent code into Core “for convenience”
Use `ILogger<T>`, `IStringLocalizer<T>`, `IOptions<T>` as in repo	Add parallel “ConnectSoft wrappers” for SecureStorage, Preferences, Connectivity unless a test seam is required
Respect *`Use` symbols: they exclude files (observability, RESX, offline/sync paths, docs**)	Assume flags strip all runtime code — some guidance docs are optional; core packages may still be present

dotnet new install <path-or-package>
dotnet new connectsoft-maui-base -h

Short name: connectsoft-maui-base (confirm in repo template.json if pinning an older package).

Page	Use when
Overview	Agent checklist, layering vs backend Base
Getting Started	Workload restore, first build
Parameters	Symbols / CLI flags
Solution structure	Where projects live
Architecture	Boundaries, DI
Features	Optional stacks
Configuration	appsettings
Authentication	MSAL / OIDC hints
Resiliency	HTTP resilience
Testing	Three test projects, coverage
Development	CPM, analyzers
Use cases	When to pick MAUI base
Runbook	Pipelines