app-auth — Claude Code skill: what it does, how to install
The app-auth skill for Claude Code structures and implements application authentication flows. It activates when handling social login, password recovery, account switching, or sign-in components.
Apache-2.0 ★ 1,216 updated 2026-11-16
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install reusable-app-components@claude-settingsWhat app-auth does
The skill sets up full-page sign-in, account creation, and password reset flows with remembered profiles. Social login runs in the same browser tab by default rather than popups. Ready-made React 19.2+ files include GoogleSignIn, EmailAuth, AuthPanel, and RememberedLogin, while core routing and session hints stay framework-neutral inside login.ts.
The host application controls script loading, backend token verification, session persistence, and post-auth navigation. PocketBase projects use pocketbase.ts to map auth providers, but the host still handles MFA, OTP tokens, and session lifecycles. The bundled Vite demo runs via npm run dev and only simulates authentication providers.
What it helps with
- implement social sign-in for Google, GitHub, Apple, or PocketBase
- remember the last authenticated profile across browser sessions
- build email authentication forms with password recovery support
- separate UI credential handling from host session storage
Example prompts for the agent
- Build a login component supporting Google and email with remembered profiles
- Add authentication flow for PocketBase with account switching
- Set up a password recovery screen and link it to session logic
How to install app-auth
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install reusable-app-components@claude-settingsThis installs the whole reusable-app-components plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill app-auth -a claude-code3Manually: put the files in place
~/.claude/skills/app-auth/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/app-auth/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill app-auth -a codex2Manually: put the files in place
.agents/skills/app-auth/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill app-auth -a cursor2Manually: put the files in place
.cursor/skills/app-auth/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/reusable-app-components/skills/app-auth2Manually: put the files in place
.github/skills/app-auth/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill app-auth -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/reusable-app-components/skills/app-authManually: put the files in place
.devin/skills/app-auth/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about app-auth
How to install app-auth in Claude Code?
Run /plugin marketplace add fcakyon/claude-codex-settings followed by /plugin install reusable-app-components@claude-settings. Alternatively, install it directly using npx skills add fcakyon/claude-codex-settings --skill app-auth -a claude-code.
What does app-auth do?
It provides architecture rules, TypeScript contracts, and React templates for same-tab social login, profile persistence, and email credentials.
What is required for app-auth to work?
React implementations require React 19.2+, while identity verification, email delivery, and session storage must be provided by the host backend.
Source text
SKILL.md · Apache-2.0
--- name: app-auth description: This skill should be used when the user asks to build, design, add, refactor or fix "login", "auth", "authentication", "social login", "sign in", "signup", "password recovery", "remember last login", "switch accounts", or a "reusable login component", including Google, GitHub, Apple, Hugging Face and PocketBase auth. Use the shared login design, bundled SVG logos, same-tab social sign-in, remembered profiles and email forms, with framework-neutral TypeScript contracts, React components and a Vite demo. Native and TV flows remain integration contracts. --- # App authentication Use full-page, same-tab social login by default and offer the last successfully used profile, saved after every verified login unless the product needs an opt-in checkbox. Google and the browser decide whether account selection or reauthentication is required. Do not promise silent login or call a flow fastest without measurements. 1. Inspect login, signup, email verification, recovery, session, logout, account linking and authorization. Identify the selected action, locales, design system and registered Google callback. 2. Read [integration](references/integration.md). For React 19.2+, adapt [GoogleSignIn.tsx](assets/GoogleSignIn.tsx) and its [styles](assets/google-sign-in.css). Use the optional [AuthPanel](assets/AuthPanel.tsx) with [panel styles](assets/auth-panel.css) for a minimal auth shell. Other frameworks should implement the same contract using their own lifecycle primitives. 3. Use [login.ts](assets/login.ts) for framework-independent navigation and last-login profile storage. React hosts can wrap their existing forms in [RememberedLogin](assets/RememberedLogin.tsx). Run `npm run dev` in the plugin directory for the Vite demo. Its provider and email flows are simulations. 4. For PocketBase apps, map enabled auth methods with [pocketbase.ts](assets/pocketbase.ts) and read the optional PocketBase section in the integration contract. Native token-link recovery, OTP, MFA and app session ownership remain explicit host responsibilities. 5. For email/password flows, adapt [EmailAuth.tsx](assets/EmailAuth.tsx) and [email styles](assets/email-auth.css). Read the email adapter section in the integration contract. Use [email-design](../email-design/SKILL.md) for messages sent by those flows. 6. Use GoogleSignIn with `label`, `redirectEndpoint` and `returnTo` for full-page login without GIS. The old credential adapter remains available for existing popup integrations. A saved email may be a provider hint only. The provider still verifies identity. “Sign in with another profile” opens all configured methods and uses `prompt=select_account` without a hint. 7. Resolve return navigation in the auth owner. Both paths must use the same account/session policy, then resume the action once. Only the backend verifies identity and authorizes access. 8. Run the applicable [journeys](references/journeys.md) through the project's existing QA harness. Keep fixture results, real Google evidence and deployed behavior distinct. 9. Record the app commit, runtime versions and actual evidence in its existing tracked guidance. Change the shared recipe only when new evidence changes a shared rule. The app owns script loading, public client configuration, sessions, error reporting and navigation. The component owns rendering, pending/error UI and cancelling its credential operation when the auth surface closes. For architecture standardization, read [backend standard](references/backend-standard.md). It is a proposed target, not an implemented Go dependency or completed migration. For web/native/TV clients or another social provider, read [platforms and providers](references/platforms.md). Use one identity store and revocation model per product across its clients. Keep browser cookies and native secure-storage transport distinct. ## Curation Read [provenance](references/provenance.md) before claiming production coverage. Distinguish a shipped reference, a tested extraction and a pending app integration. Add future components as focused skills with code, integration contracts and behavior tests when an actual app supplies the evidence. Do not add empty catalogs or treat a component PR as permission to deploy another app.
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings