Working Signup/Auth System
0/13 steps0%

Step 1 of 13

Define auth requirements

Clarify exactly what the authentication system must do before building it.

This step prevents the AI from creating only a visual signup form. Paste the Context Pack first.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Create a complete authentication requirements spec for this app. Include user signup, login, logout, session persistence, protected dashboard routes, validation rules, error states, loading states, duplicate email handling, and mobile behavior. Make clear that the implementation must be functional, not only visual.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A clear auth spec that can guide implementation.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent