setup-auth

> **Plugin check**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding. # Set Up Authentication & Authorization Configure authentication (login/logout via Microsoft Entra ID) and role-based authorization for a Power Pages code site. This skill creates an auth service, type declarations, authorization utilities, auth UI components, and role-based access control patterns appropriate to the site's framework. ## Core Principles - **Client-side auth is UX only** — Power Pages authentication is server-side (session cookies). Client-side role checks control what users see, not what they can access. Server-side table permissions enforce actual security. - **Framework-appropriate patterns** — Every auth artifact (hooks, composables, services, directives, guards) must match the detected framework's idioms and conventions. - **Development parity** — Include mock data for local development so developers can test auth flows and role-based UI without deploying to Power Pages. **Initial request:** $ARGUMENTS > **Prerequisites:** > > - An existing Power Pages code site created via `/create-site` > - The site must be deployed at least once (`.powerpages-site` folder must exist) > - Web roles must be created via `/create-webroles` ## Workflow 1. **Phase 1: Check Prerequisites** — Verify site exists, detect framework, check web roles 2. **Phase 2: Plan** — Gather auth requirements and present plan for approval 3. ...