La versione breve
- Un prompt UI è più utile se descrive il compito dell'utente, lo stato della schermata e i vincoli di accessibilità. Gli esempi indicano direzioni di layout, non aumenti di conversione misurati.
- Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Un prompt UI è più utile se descrive il compito dell'utente, lo stato della schermata e i vincoli di accessibilità. Gli esempi indicano direzioni di layout, non aumenti di conversione misurati.
Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Come usare questa raccolta
Scegli l'attività più vicina al tuo lavoro. Copia il prompt, sostituisci la scena generica o il contesto del codice con i tuoi dati e mantieni i vincoli utili a valutare il risultato. Modifica una variabile alla volta per capire cosa migliora.
Il metodo segue la guida a First Draft di Figma: fornisci un contesto preciso e controlla il risultato, senza dare per corretta una prima bozza ben presentata.
Prompt per descrivere l'attività
Per descrivere l'attività, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
1. Un percorso di iscrizione a un'app didattica
Design a signup flow for a learning app for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
2. Una schermata di risultati per cercare lavoro
Design a search results screen for jobs for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
3. Un pannello delle impostazioni delle notifiche
Design a settings panel for notifications for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
4. Una pagina di riepilogo del pagamento
Design a checkout review page for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
5. Uno stato vuoto per gli elementi salvati
Design an empty state for saved items for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
6. Una dashboard per un redattore
Design a dashboard for an editor for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
7. Un calendario delle prenotazioni
Design a booking calendar for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
8. Un menu di navigazione mobile
Design a mobile navigation menu for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
9. Uno stato di errore nel pagamento
Design an error state for payment for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
10. Una schermata per completare il profilo
Design a profile completion screen for a person who needs to finish one task quickly. State the audience and task you are assuming. Then show the user goal, entry point, essential action and success state in a low-fidelity flow. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Un nuovo utente capisce quale azione compiere senza leggere un suggerimento?
Prompt per progettare la schermata principale
Per progettare la schermata principale, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
11. Un percorso di iscrizione a un'app didattica
Design a signup flow for a learning app for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
12. Una schermata di risultati per cercare lavoro
Design a search results screen for jobs for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
13. Un pannello delle impostazioni delle notifiche
Design a settings panel for notifications for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
14. Una pagina di riepilogo del pagamento
Design a checkout review page for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
15. Uno stato vuoto per gli elementi salvati
Design an empty state for saved items for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
16. Una dashboard per un redattore
Design a dashboard for an editor for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
17. Un calendario delle prenotazioni
Design a booking calendar for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
18. Un menu di navigazione mobile
Design a mobile navigation menu for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
19. Uno stato di errore nel pagamento
Design an error state for payment for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
20. Una schermata per completare il profilo
Design a profile completion screen for a person who needs to finish one task quickly. State the audience and task you are assuming. Then use a clear hierarchy, realistic content lengths and one prominent primary action. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Controlla il layout su desktop e su uno schermo mobile largo 360 pixel.
Prompt per gestire i dati mancanti
Per gestire i dati mancanti, indica l'utente e la decisione che la schermata deve aiutarlo a prendere.
21. Un percorso di iscrizione a un'app didattica
Design a signup flow for a learning app for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
22. Una schermata di risultati per cercare lavoro
Design a search results screen for jobs for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
23. Un pannello delle impostazioni delle notifiche
Design a settings panel for notifications for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
24. Una pagina di riepilogo del pagamento
Design a checkout review page for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
25. Uno stato vuoto per gli elementi salvati
Design an empty state for saved items for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
26. Una dashboard per un redattore
Design a dashboard for an editor for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
27. Un calendario delle prenotazioni
Design a booking calendar for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
28. Un menu di navigazione mobile
Design a mobile navigation menu for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
29. Uno stato di errore nel pagamento
Design an error state for payment for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
30. Una schermata per completare il profilo
Design a profile completion screen for a person who needs to finish one task quickly. State the audience and task you are assuming. Then include empty, loading and error states with recovery actions. Use realistic labels and content lengths, with no invented metrics or testimonials. Describe the information hierarchy, mobile adaptation and next action. Explain one tradeoff and how you would check it with users.Verifica: Verifica che l'utente possa riprendere l'attività senza perdere i dati inseriti.
Cosa verificare prima di usare il risultato
Le schermate generate sono un punto di partenza. Testale con contenuti reali, tastiera, schermi piccoli e persone che dovranno usarle. Una buona resa visiva non dimostra l'usabilità.
Se il risultato non risponde al compito, accorcia il prompt e precisa il fatto o il vincolo mancante. Conserva la versione usata per poter riprodurre il contenuto finale o la modifica al codice.
Approfondimenti
Hai una domanda o una correzione?
Contatta Thrive
