manage-app-shell-authlisted

Enable or disable the PUBLIC auth control of the app shell — the Sign in / account button in the header and the signed-in visitor's account drawer. Use when the owner says "add login", "add auth", "I want a personal cabinet / my account", "let users sign up", or when you are building an app that NEEDS visitor accounts (a store, a social app, a SaaS dashboard) — and when the owner says "remove login". It is a BUILD-TIME toggle (NEXT_PUBLIC_APP_SHELL_AUTH = left | right | off) written through a validated setter; a change applies after a REBUILD. Self-sufficient: the setter is registered in every agent's MCP client — no Hermes required. The admin login always exists separately; this governs only what your visitors see.
Fractera/Agent-Engineering-Infrastructure · ★ 29 · AI & Automation · score 72

Install: claude install-skill Fractera/Agent-Engineering-Infrastructure

# manage-app-shell-auth Turn the deployed app's **public login** on or off. This is the agent-facing side of Admin → **App Settings → App authorization**: the same toggle, settable by you on the owner's behalf. ## What it controls When ON, the header gains a control that reads the visitor's identity: - a guest sees **Sign in** (opens the existing auth flow); - a signed-in visitor sees their **account** button → a full-height **account drawer** (sign out + their email + roles; future account links live there). When OFF (the default), none of this ships — no account button, smaller bundle, faster deploy. A landing page or portfolio needs no login, so it stays off until asked for. **The admin login (how the owner manages the app) is a separate, always-present layer — this toggle never touches it.** You are only ever turning the *public, visitor-facing* login on/off. ## The states `NEXT_PUBLIC_APP_SHELL_AUTH` — one build-time env key, three states: - **off** (absent/empty) → no public auth (default). - **left** → public auth ON, account drawer slides in from the **left**. - **right** → public auth ON, account drawer slides in from the **right**. ## When to enable (and the auto-rule) Enable it when the app genuinely needs **visitor accounts**: a store (checkout, orders), a social app, a SaaS dashboard, anything where people log in. Leave it **off** for static brochure-style sites. **Auto-rule (do not skip):** if the owner asks you to build something that inherently req