1.Design BriefEnter a UI screenshot with your app type and brand details, and get a detailed design brief written for developers, covering light and dark mode and default responsive breakpoints.Design › Design collaboration · #Analyzing #Reformatting #Developer2.Work out what a change request actually costsCounts in what must be redone rather than hours, and names what breaks silently.Design › Design collaboration · #Analyzing #Reviewing #Question generation3.Read the decisions behind a competitor's screenLooks for what they gave up, and states what cannot be known from outside.Design › Design collaboration · #Analyzing #Reviewing #Ideation4.Decode vague design feedbackThe reaction is usually right and the proposed fix usually is not — this works back to the observation.Design › Design collaboration · #Analyzing #Question generation #Reviewing5.Design Handoff Notes - AI First, Human ReadableEnter your project, framework, styling approach, component library, and design source to get a spec document an AI implementer can follow without guessing.Design › Design collaboration · #Drafting #Reformatting #Developer6.Write a developer handoff specWhat gets built wrong is the behaviour nobody wrote down, not the layout.Design › Design collaboration · #Drafting #Checklist #Reformatting7.Run a design review that ends in decisionsNarrows to one question and states up front what is not up for discussion.Design › Design collaboration · #Drafting #Question generation #Checklist8.Document a component so it is used correctly"What it is not for" prevents more misuse than "what it is for".Design › Design collaboration · #Drafting #Reformatting #Template
TukttakAI prompt library