Menu

Individual skill

ux-login-signup

0upvotes

Design or critique a login / sign-up screen. Applies the always-true core (separate pages, minimal fields, inline validation, full password-reset flow) and gates context-dependent choices (social login, 2FA, "stay logged in", username vs. email) with trade-offs. Trigger when designing auth screens, sign-up forms, registration flows, or password recovery.

ux/screens/login-signup/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Login & Sign-up Screen Skill


## How this skill behaves (read first)

This is a **generative** skill, so it does **not** blindly apply every best practice — login/sign-up has a set of context-dependent levers (social login, "stay logged in", username vs. email, 2FA) where applying everything is wrong for some products and right for others. Auto-applying all of them produces a bloated, insecure, or privacy-hostile screen.

So the skill works in three moves:

1. **Establish context** (one quick question if it's not already known).
2. **Apply the always-true core** — the patterns that are correct for essentially every auth screen.
3. **Surface the context-dependent decisions** with their trade-offs and a recommendation, and let the user choose — don't silently pick.

Then it **hands the result to the audit skills** for validation: call the **heuristics audit** (`ux-heuristics-audit`) and the **accessibility audit** (`ux-accessibility-audit`) on the generated screen. This skill deliberately does *not* re-derive contrast/keyboard/screen-reader rules — that's the accessibility skill's job.
Back to top