app-auth
/app-auth
Buduje lub poprawia logowanie i rejestrację: logowanie społecznościowe, odzyskiwanie hasła, zapamiętane profile i wspólny projekt logowania.
- Autor
- fcakyon ↗
- Repozytorium
- claude-codex-settings ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 26
- Skrypty
- 10
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 10 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: assets/AuthPanel.tsx, assets/EmailAuth.tsx, assets/GoogleSignIn.tsx, assets/ProviderLogo.tsx, assets/RememberedLogin.tsx, assets/SocialSignIn.tsx, assets/auth.ts, assets/login.ts
Co robi i kiedy
Buduje lub poprawia logowanie i rejestrację: logowanie społecznościowe, odzyskiwanie hasła, zapamiętane profile i wspólny projekt logowania.
Wyzwalacze z opisu
Oryginalny opis (EN)
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.
Jak działa
- Curation
Podgląd SKILL.md
--- 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.
Pliki w paczce (26)
- SKILL.md 4 KB
- assets/AuthPanel.tsx 1 KB
- assets/EmailAuth.tsx 9 KB
- assets/GoogleSignIn.tsx 3 KB
- assets/ProviderLogo.tsx 1 KB
- assets/RememberedLogin.tsx 2 KB
- assets/SocialSignIn.tsx 1 KB
- assets/auth-panel.css 3 KB
- assets/auth.ts 1 KB
- assets/email-auth.css 3 KB
- assets/google-sign-in.css 1 KB
- assets/login.ts 1 KB
- assets/logos.d.ts 1 KB
- assets/pocketbase.ts 1 KB
- assets/social-sign-in.css 1 KB
- assets/fonts/InterVariable.woff2 344 KB
- assets/fonts/OFL.txt 4 KB
- assets/logos/apple.svg 1 KB
- assets/logos/github.svg 1 KB
- assets/logos/google.svg 1 KB
- assets/logos/huggingface.svg 5 KB
- references/backend-standard.md 5 KB
- references/integration.md 20 KB
- references/journeys.md 5 KB
- references/platforms.md 7 KB
- references/provenance.md 4 KB
Wersje
W bazie nie ma innych skilli o nazwie app-auth.
Migawka bazy z 13.11.2026 · wersja paczki bc162df0bc5b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100passwordless-authentication
Buduje bezpieczne logowanie bez hasła przez jednorazowy kod e-mail, a opcjonalnie logowanie społecznościowe i biometrię w telefonie. - 100better-auth-authentication
Obsługuje przepływy uwierzytelniania Better Auth w aplikacjach TypeScript: logowanie e-mailem i hasłem, dostawcy społecznościowi, rejestracja, logowanie i weryfikacja. - 100clerk-core-workflow-a
Wdraża rejestrację i logowanie użytkowników w Clerk, w tym interfejs uwierzytelniania i logowanie społecznościowe OAuth. - 100clerk-core-workflow-a
Wdraża przepływy rejestracji i logowania w Clerk: interfejs uwierzytelniania, dostosowanie logowania i logowanie społecznościowe OAuth. - 100better-auth
Dodaje uwierzytelnianie do aplikacji w dowolnym frameworku za pomocą Better Auth: logowanie i rejestrację, dostawców OAuth, sesje oraz wybór między bibliotekami auth dla TypeScript. - 100email-and-password-best-practices
Konfiguruje weryfikację e-mail, reset hasła i politykę haseł w Better Auth, w tym algorytmy haszowania.