Audit Existing Team, User, and Auth Models

Map the current app structure so the invite system integrates with real existing models and permission rules.

Ask the builder to inspect the current schema and auth flow before changing anything.

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

Prompt Capsule

Review the existing codebase and identify the real models, routes, and UI related to users, teams, memberships, and authentication. Show me the current schema for users, teams, and team memberships, identify who currently has admin or owner privileges, and propose the minimal integration plan for adding team invitations. Do not implement anything yet; first give a concrete implementation plan tied to the actual files and models already in the app.

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 implementation plan showing current models, permissions, routes, and the exact insertion points for invites.

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.

Existing user model is identifiedExisting team and membership models are identifiedCurrent role or permission logic is documentedFiles/routes/components to modify are named explicitly

Do not continue if…

! Building only an invite modal UI without any database table, token validation, or acceptance logic
! Letting the frontend decide who can invite users without server-side authorization checks
! Creating invite links that look real but do not actually map to stored invite records
! Accepting the invite visually without creating a real membership row in the database

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.

You gave a generic plan instead of inspecting my actual app. Re-scan the current codebase and list the real files, models, routes, and components for users, teams, memberships, and auth. Base the invite implementation plan only on what already exists in this project.