Auth UI Specification

Define Zod-validated specifications for authentication UI forms and flows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/stellarone/evaluate --skill auth-ui-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Auth UI Specification
Source: https://github.com/stellarone/evaluate/tree/main/.agents/skills/auth-ui-specification
Command: npx skills add https://github.com/stellarone/evaluate --skill auth-ui-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates ambiguity and rework when implementing authentication UIs by providing consistent, field-by-field specifications and Zod-ready validation rules for every auth-related screen.

Core Features & Use Cases

  • Login form spec: email/password fields with clear validation and API submit behavior to /api/v1/auth/login.
  • Signup form spec: enforces strong password requirements, full name rules, and mandatory terms acceptance, including the required redirect to OTP verification.
  • OTP, reset, and password update specs: defines verification inputs (including OTP type), reset behavior that avoids leaking sensitive info, and secure change-password flows that route mutations through platform-auth.

Quick Start

Use this skill to generate Zod schemas and form field specs for login, signup, OTP verification, reset password, and invite forms, then wire them to the corresponding auth endpoints in your app.

Frequently Asked Questions about Auth UI Specification

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

FAQPage Schema
How do I define Zod validation schemas for a login form?

To define Zod validation schemas for a login form, you specify explicit email and password field validation rules with deterministic API submit behavior routing to the `/api/v1/auth/login` endpoint.

What password policy and terms acceptance rules are needed for a signup form spec?

A complete signup form spec enforces strong password requirements, full name validation rules, and mandatory terms acceptance, including a required redirect to OTP verification.

How does OTP verification UI specification handle input validation?

OTP verification UI specification defines specific verification inputs, including the OTP type, and establishes deterministic submit, redirect, and error behavior matching platform-auth endpoints.

Can I use this auth UI specification with any frontend framework?

Yes, the auth UI specification applies to login, signup, OTP verification, password reset, and invite user scenarios across any frontend framework by providing field-by-field specifications and Zod-ready validation rules.

How to design a password reset form that avoids leaking sensitive info?

Designing a password reset form that avoids leaking sensitive info requires defining reset behavior with explicit field validation rules and deterministic error messaging that matches platform-auth endpoint flows.