Design app screens

I need polished app screens for the core user flow by next Tuesday for the beta build. Design five mobile screens: Home feed, Item detail, Create post, Notifications, and Profile. Use the Product Design System tokens for color and text, include real copy for headlines and at least one microcopy example (empty state on Notifications), and create interaction states for primary buttons and a modal confirmation for deleting a post. Prepare these screens in a single file where layers are tidy and components are used rather than flattened frames.

Before I hand final screens to engineering, make them easy to implement: ensure all components are instances from the system, expose layout constraints for responsive behavior, annotate padding and type sizes, include image assets in the assets page, and add a short spec sheet listing API endpoints needed for feed, create, and notifications. Flag any screens that use custom behavior not covered by the system.

I delivered five final screens and engineers report missing image sizes and unclear spacing rules; they can’t map components to endpoints. I’m worried the release will slip if I don’t fix it now. Which two fixes will most reduce their blockers this afternoon, and how should I communicate the changes so they can continue work while I update the files?

Every sprint I end up adding specs, annotating screens, and answering the same implementation questions one-off. That slows releases and frustrates engineers. What three small practices could I make routine so handoffs are consistent, reduce follow-up questions, and cut the number of clarification messages the engineering lead sends me each sprint? Be concrete about what to include in the file and what to say in the handoff message.