Describe your app
A useful brief names the job before the layout. Include who the app serves, what information it receives, and what should happen next.
A brief you can adapt
Section titled “A brief you can adapt”Create a customer workspace. Customers sign in to see their own project documents and submit requests. Staff see a queue of requests and can update their status. Save each request with its customer, project, message, and status. Send an acknowledgment only after the request is saved. Keep the layout quiet and readable on a phone.
This describes a result you can test: a customer submits a request, staff handle it, and the customer sees the change.
Add models with a purpose
Section titled “Add models with a purpose”If you want an agent to suggest a response, name its approved source documents and ask for a draft for staff review. Specify what it should do when an answer is missing. If the app generates media, describe the input, output format, where files are saved, and how users choose a result.
Use reference material carefully
Section titled “Use reference material carefully”Attach a sample file or design reference when it clarifies the brief. Remove private information you do not need for the build. Explain whether a file supplies data, text, visual direction, or all three. A screenshot supplies appearance; live behavior still needs to be described.