Before we wrap up, let's cover a few best practices that will make your time in the builder smoother and more productive:
Build your front end first. Start with the interface and layout, then connect data and workflows afterward. This order tends to give you the best results.
Keep your changes small and focused. Rather than trying to make many big changes in one long conversation, scope each conversation to the change you're working on. When you finish one change and want to start something significantly different, begin a new conversation. This keeps the builder accurate and helps it stay focused on the task at hand.
Use @ mentions to give the builder context. You can reference stories, record types, plans, and resources by @-mentioning them in the conversation panel, which helps Workbench understand exactly what you're working with.
Refine through follow-up prompts. You don't have to get everything right on the first try. After your first version is generated, keep the conversation going with small, specific follow-ups: "make the header blue," "add a dropdown for department," "move the submit button to the bottom." Build it up piece by piece.
Think of building an App as a back-and-forth conversation rather than a single big request. Describe, review in the Preview tab, refine, and repeat. That rhythm is the heart of working in the App builder.