A portfolio website should make it easy for a potential client to answer three questions: What do you do, who do you work with, and can you actuall...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
The biggest takeaway for me is that AI works better as a design accelerator than a replacement. Getting multiple directions quickly is useful, but the decisions around hierarchy, copy, positioning, and usability are what actually make a portfolio feel credible.
Exactly! That was my experience too. AI saved a lot of time getting from a blank canvas to workable concepts, but the final quality came from deciding what to keep, what to remove, and how to make the portfolio communicate clearly to a real client.
Absolutely! That balance between AI efficiency and human judgment is what makes the final work stand out. Glad you had a similar experience, and thanks for sharing your perspective!
This is so true, one thing i noticed from the v0 generation is that it has a particular way of designing portfolios for example i also generated a portfolio site but it was only after heavy editing, I was able to bring out the desgn i wanted.
The "brief instead of a master prompt" approach is the most transferable takeaway here; keeping a single input across Figma Make, Stitch, v0, and Banani turns the comparison into an actual test of the tools rather than a test of your prompting skill on any single tool. It also mirrors real client work, where you rarely get to hand-tune the brief per deliverable; you write it once, and it has to hold up.
The line that stuck with me was "you don't necessarily need AI to give you the final answer, you need it to give you more good options quickly." That's a much healthier framing than treating any of these tools as a design-decision engine. The manual pass rewriting the hero, adding problem/role/outcome context to projects, and checking mobile separately is normal design work that AI sped the runway to, not replaced.
Absolutely agree. Using the same brief across every tool makes the comparison much more realistic because you are evaluating the tools themselves, not how well you can optimize prompts for each one. And that point about AI generating more good options quickly is exactly the right mindset. AI can speed up exploration, but the final design decisions still need a human eye.
Really useful breakdown of using multiple AI design tools against the same brief instead of hopping between them ad hoc. The framing of "AI gives you a direction, not a finished decision" matches what I've seen too. The repetitive layout and component work is where these tools genuinely save time, but things like hero copy, project framing, and information hierarchy are where a real understanding of the client's problem still has to show up. The mobile-check point is underrated as well; a lot of AI-generated first passes look great on desktop and fall apart on smaller viewports.
Absolutely agree. AI is great at accelerating the repetitive execution, but the real value still comes from understanding why something should be designed a certain way. The mobile check is especially important, what looks polished on desktop can quickly expose weak hierarchy or spacing on smaller screens. AI can speed up the process, but the designer still has to make the right decisions.
I really liked the point about not publishing the first AI-generated version. The “first output is a draft, the second pass is where the real design work begins” mindset feels especially important when using AI for client-facing work.
Absolutely. The first generation gives you something to react to, not something you should automatically ship. The manual refinement is what helped turn the AI output into something that actually represented my work and made the projects easier for clients to understand.
The part that landed for me was keeping one brief across tools instead of rewriting the prompt for each generator. On client files I force a four-line sticky before any AI pass: (1) one-sentence goal for this visitor, (2) constraints the model must not invent, (3) the one acceptance check (“a stranger can answer what I do in one breath”), (4) what is explicitly out of scope this round.
If I skip that, every tool happily invents a different hero and a different service list at high confidence. If I keep it, the first output is already a draft I can edit instead of a new personality. Curious whether your worst first-pass was a “bad tool” or just a brief that left positioning and out-of-scope blank.
That’s a really solid approach. I’ve noticed the same thing, AI often isn’t the problem; the lack of a clear brief is. The four-line sticky is a great way to keep the tools focused on the actual positioning instead of letting each one invent its own direction. The “out of scope” part especially feels underrated.
What stood out to me is the workflow, not the tools themselves. Using one consistent brief across four different generators instead of tailoring the prompt for each is the part most people skip, and it's exactly why the comparison actually meant something here. You could see how each tool interprets the same input rather than just picking whichever one happened to sound good with a custom-written prompt.
The mobile-check habit is one I've learned the hard way too. A layout can look completely polished on a 1440px screen and then fall apart the moment text wraps differently or a card grid stacks awkwardly on a phone. Treating the first generation as a draft rather than a deliverable seems like the actual skill here, way more than knowing which AI tool to open first.
Absolutely agree. The biggest value comes from keeping the input consistent and judging how each tool handles the same constraints. And yes, treating AI output as a first draft is becoming a core skill. The real work starts when you test, refine, and adapt it across screen sizes.
The four-line sticky idea from another commenter is close to what I do too, but I'd add one more failure mode worth naming: even with a locked brief, the tools disagree on what "professional" means visually, and that disagreement is where a lot of first-pass ugliness comes from. One tool's idea of restrained is another tool's idea of empty.
What stood out most in your breakdown was treating v0 as an implementation tool rather than a design tool. That's the split people miss, they run everything through one generator and get frustrated when the thing that's great at layout exploration is mediocre at component structure, or vice versa. Matching tool to stage instead of expecting one tool to do all of it is probably the actual unlock here, more than any specific prompt.
Absolutely. That difference in what each tool considers “professional” is something I noticed too. A locked brief helps, but it does not guarantee consistent visual output across tools.
And I completely agree on v0. Treating it as an implementation tool rather than forcing it into the design exploration stage makes much more sense. The real unlock is understanding which tool is best for each stage of the workflow instead of expecting one AI tool to handle everything.
This is a great example of where AI-assisted design actually makes sense. I especially like the distinction between generating the first version and making the final product feel intentional. The biggest win isn’t replacing the designer, it’s reducing the time spent getting from a blank canvas to something worth critiquing. The human judgment around positioning, hierarchy, copy, and usability is still what makes the portfolio convincing.
Absolutely agree. AI is most valuable when it helps designers move past the blank canvas faster, while the human still owns the decisions that make the final product feel thoughtful and usable. That balance is where AI-assisted design really shines.
Really solid breakdown, especially the part about treating each tool's output as a starting point rather than a finished product. The distinction between Figma Make for exploration, Stitch for quickly comparing directions, v0 for turning sections into working components, and Banani for generating concepts to pull ideas from is a much more realistic way to use these tools than expecting one platform to do everything.
The mobile check point stood out to me too. It is easy for a layout to look great on a large screen and then fall apart once text wraps differently or spacing gets cramped on a phone, and a lot of first drafts from AI tools do not account for that well.
The biggest thing I am taking from this is the reminder that clients do not care which tool built the site. They care whether the site makes it obvious what you do and whether they can trust you to solve their problem. AI can speed up the layout and component work, but positioning, project framing, and copy still need a human who understands the actual client.