Create wireframe layout

I need a basic wireframe layout for the onboarding flow—two screens: welcome and create-account—ready by Wednesday. Create a 360×800 mobile frame for each screen. On the welcome screen place a centered illustration, a headline, a one-line benefit statement, and two buttons: Create account and Log in. On the create-account screen include labeled fields for name, email, password, a show-password toggle, and a Continue button disabled until fields are valid. Keep everything in low-fidelity — gray boxes and placeholder text.

Before I hand these wireframes to the PM and engineers, make them easy to evaluate: surface the primary conversion path, label which fields are required, show the disabled state and an error example for the email field, and add a short note listing assumptions about validation and third-party auth. Highlight any places where flow detail is missing that would make engineers block on APIs.

I sketched the onboarding wireframes and the PM says she needs field validation and edge cases before scoping. I don’t know the business rule for password strength or whether to allow social sign-on. I’m afraid engineers will build a lax flow or we’ll postpone a critical check. What’s the likely minimum validation to ask for now and how should I phrase the questions to the PM so we can move to estimate without stalling design?

Across projects we hand over low-fi wireframes that omit validation, error states and empty states. That leads to weeks of rework when engineers implement and QA finds edge cases. What practical habits should I adopt in my wireframe process to catch the common missing items and cut handoff back-and-forth by half? Give three checks to include on every wireframe before review.