Look beyond a component generator
v0 documents application projects with GitHub, database integrations and Vercel deployment. Its project workflow goes beyond generating isolated interface components. Compare the tools on the application you need to deliver.
MaShop combines application work in Code with research and connected-service tasks in Agents. Describe the users, data and actions needed for your dashboard, public website or internal application.
Make the design requirements testable
Describe the people using the screen, the main action and the information they need to make a decision. Include a reference, colours, typography and the placement of important blocks when those details matter.
For an internal dashboard, ask for the overview, the detail view and the empty or error states that belong to your workflow. Inspect mobile behaviour and the actual interaction. Refine a specific screen instead of accepting the first arrangement as the finished product.
- Name the information the screen should display.
- Explain what should happen after its main action.
- Identify the layout and existing behaviour that must remain unchanged.
Review code and data as separate responsibilities
Use Ask for a diagnosis or Plan for an approach before switching to Build or Agent for code changes. The connected GitHub project, files and preview help you review the implementation.
When the application needs stored data, review the Supabase connection and required changes. Source control, application data and hosting have different roles. Verify each step rather than treating a generated screen as proof that all services are configured.
Use agents for the next operational task
After reviewing a dashboard, open Agents to research a tool or prepare a report from a connected service. Specify the source and expected output, then review any action that needs approval.
Instructions, selected tools, skills and memory help define repeatable work. Execution history records what happened. Compare this workflow alongside the development experience, and consult current pricing and usage limits before choosing a plan.
Common questions
Can I specify the design instead of accepting a preset layout?
Yes. Include your colours, typography, references, page structure and interaction requirements in the brief. Review the output and request precise corrections; a prompt is not a guarantee of a perfect first result.
What is the difference between Agent and Agents?
Agent is a Code mode for carrying coding steps forward. Agents is the area for operational agents, connected-service tasks and recurring work. They use different conversations and still respect available tools and permissions.
Are a database and hosting automatically connected?
No. Review the services the application needs and authorize the relevant connections. A preview does not confirm that a database or production host has been configured.