Skip to content
Skillpedia
Interfaces (UI/UX)101k · #738

login-flow

Creates login and authentication screens for mobile apps. It ensures a secure and easy sign-in flow for users.

What it does

This tool creates login screens for mobile apps. It can generate options like SMS verification, password login, or social logins (Google, Facebook, etc.).

When to use it

  • ✓When you need an entry screen for a new mobile app.
  • ✓If your app needs to verify the user's phone number via SMS.
  • ✓To add quick login options using existing accounts (Google, Facebook).

Example of what to ask your AI

“Create a login screen for my app that accepts phone and SMS login, with a button for Google login.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/skills/login-flow/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/skills/login-flow/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool first checks basic requirements. Then, it asks which login method you prefer (SMS, password, or social). Finally, it builds the HTML code for this screen, including error and loading states.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill login-flow

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/skills/login-flow/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Login Flow Skill

A skill for generating mobile-first login and authentication screens. Use this when the user wants a sign-in experience for a mobile app, including phone + SMS verification, password-based login, and social SSO options.

Workflow

  1. Read reference files first (see below)
  2. Clarify auth method: phone/SMS, password, or social SSO
  3. Checklist gate — verify P0 items before emitting <artifact>
  4. Build the HTML prototype with proper states (default, loading, error)
  5. Wrap in <artifact> tag referencing the output file

Side Files

  • references/checklist.md — P0/P1 acceptance criteria

Output

A single standalone HTML file implementing the login screen with:

  • Labels above inputs (never placeholder-only)
  • Password field with show/hide toggle
  • Social SSO buttons with SVG icons
  • Error states below fields
  • Loading spinner in primary CTA
  • Touch targets minimum 44px

Mobile-First Constraints

  • Viewport: 375px wide (iPhone standard)
  • No horizontal scroll
  • Safe area insets for notched devices
  • Input keyboards: tel for phone, password for password fields
FAQ

What are 'states' on the login screen?

These are the different appearances the screen can have, such as the normal state, the loading state while the password is being verified, or the error state if something goes wrong.

What does 'mobile-first' mean?

It means the screen is designed primarily to work well on mobile phones, with a standard screen width of 375 pixels, ensuring nothing is cut off or requires horizontal scrolling.

What are 'touch targets'?

These are the clickable areas on the screen (buttons, text fields). 'Touch targets' of 44px ensure they are easy to tap with a finger on mobile screens.

Details

Original description by the author

Mobile login and authentication flow screens

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#738
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills