pages-auth-publiques

Documents Toollab's five public authentication screens, login redirect flows, and account activation rules.

Updated May 5, 2025
One-click install
npx skills add https://github.com/sebauvray/toollab-api --skill pages-auth-publiques-sebauvray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pages-auth-publiques
Source: https://github.com/sebauvray/toollab-api/tree/main/.claude/skills/pages-auth-publiques
Command: npx skills add https://github.com/sebauvray/toollab-api --skill pages-auth-publiques-sebauvray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying Toollab's public authentication screens is risky because the auth design is duplicated across four Vue files, the login flow has multiple redirect branches (super-admin, multi-school, zero-school with pending invitations), and several anti-patterns (remember-me, contact links, authenticated calls on public pages) must not be reintroduced. This Skill gives an AI assistant the full context to edit these screens safely. ## Core Features & Use Cases - Auth screen map: Documents the five public routes (login, set-password, reset-password, forgot-password, select-school) with their layouts, middleware, and roles. - Login flow specification: Details the post-login branching logic including super-admin school counting via direct school roles, multi-school selection, and the critical zero-school-with-pending-invitation case. - Account activation flow: Covers the invitation token flow (check-invitation-token, set-password) including the requires_profile case and server-side effects like Sanctum token revocation. - Use Case: You need to change the split-screen auth design. The Skill tells you the change must be replicated in all four files (login, set-password, reset-password, forgot-password) and that animations must respect prefers-reduced-motion. ## Quick Start Ask the assistant to update the login page error handling or modify the auth screen design while following the pages-auth-publiques guidelines.

Frequently Asked Questions about pages-auth-publiques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify the login page design in a Nuxt app with duplicated auth screens?▼

The auth design is duplicated across login.vue, set-password.vue, reset-password.vue, and forgot-password.vue with identical structure and scoped styles. Any design change must be replicated in all four files, or factorized across all four at once to avoid divergence.

How should post-login redirection work for users with multiple schools?▼

After login, fetch the user's school roles. Super-admins count distinct school IDs from their direct school roles. One school sets it directly and redirects; multiple schools route to /select-school preserving the redirect query; zero schools checks for pending invitations before logging out.

Why should a user with zero schools not be logged out after login?▼

A user with zero schools may have pending invitations that grant no access until accepted. They must stay authenticated to accept invitations from the in-app banner or the select-school screen, so logging them out would lock them out permanently.

Can public auth pages make authenticated API calls?▼

No. These pages call the API via direct fetch to the public apiUrl without apiClient, so they have no interceptors or auth context. This is a tolerated anti-pattern, and no authenticated calls should be added to these pages.

What error cases should a login form handle?▼

Handle 401/422 with the server message, 429 with a rate-limit message (the limiter allows 5 attempts per minute), 500, and network errors. Messages should use soft tints like bg-red-50 with ring styling, not solid bg-red-500 blocks.