maui-quarterback

To coordinate multi-surface MAUI work, a primary skill is assigned ownership while up to three secondary skills handle adjacent domains like navigation, auth, or API, preventing cross-skill conflicts. This orchestration ensures complex requests are managed with proper guardrails and sequencing.

Preventing MVVM and platform code conflicts requires enforcing app-model adherence and selecting a primary skill to own the task. This approach attaches secondary skills for support, ensuring wave-based sequencing and clear handoffs across MAUI domains without conflict.

Yes, this orchestration supports Shell, plain MAUI, Blazor Hybrid, MauiReactor, and migration app models. It enforces app-model adherence by loading current APIs, framing concerns, and delivering a wave-based handoff contract to prevent cross-skill conflicts during complex requests.

Sequencing setup, infrastructure, and UI work is handled through a wave-based approach that plans execution phases. It assigns a primary skill for the request, attaches secondary skills, and delivers a clear handoff contract to downstream skills for each wave.

No, loading current APIs is handled automatically to satisfy governance rules during orchestration. The workflow frames concerns, selects primary and secondary skills, and sequences the work, ensuring app-model adherence without manual API loading.

Multi-domain requests fail due to cross-skill conflicts when ownership is unclear. Assigning one primary skill and up to three secondary skills enforces guardrails and sequencing, delivering a wave-based handoff contract that prevents overlapping task management.