Define the auth flow and metrics schema

Establish exactly what the login system must do and what metrics need to be captured before implementation starts.

If your stack already has auth or analytics packages, tell the builder to use them instead of inventing new ones.

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

Prompt Capsule

Review this project and produce an implementation plan for a real login page with authentication and metrics tracking. Identify the current stack, existing auth provider if any, routing structure, protected pages, and available analytics or database options. Define the auth flow from page load to login success or failure, and list the exact events to track: login_page_view, login_attempt, login_success, login_failure, logout, and unauthorized_redirect. For each event, specify required fields such as timestamp, email or masked identifier when appropriate, failure reason, route, and session or user id if available.

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 concrete implementation plan listing auth flow steps, route protections, and the exact analytics events and data fields to record.

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.

Your notes for this step

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

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Auth provider or backend path is identifiedProtected destination after login is namedMetrics event names are explicitly listedFailure reasons to capture are definedNo part of the plan relies on fake UI-only auth

Do not continue if…

! Building a login form that looks complete but does not authenticate against a real backend or auth service
! Tracking metrics only in console logs without storing or sending them anywhere testable
! Redirecting after login without actually persisting the authenticated session
! Showing generic success states even when auth requests fail

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Your previous response was too generic. Re-inspect the actual project structure and give me a specific implementation plan based on the current stack, files, routes, auth method, and where metrics events will be stored or sent. Do not describe a mock example.