Is there a realistic workflow for good UI, or is learning Figma/front-end basics basically unavoidable?

I'm pretty new to vibe coding. I can get the basic app working but the visual side, getting it to actually look good? That's where I got stuck.

I have a rough sense of what I want it to look like. Sometimes I'll grab screenshots of sites or apps I like and ask AI to turn those into a prompt or design direction. And it sort of helps, the colors get closer, but everything else, like the way components feel against each other, it all goes back toward that same generic SaaS template.

And then every tiny visual change becomes another round of prompting. It makes me feel frustrated. I don't know front-end well enough to just open the code and fix it myself. Learning Figma and design systems plus everything looks like a big project.

Do you have an actual workflow for getting decent UI without going full code dev? Or is the answer that eventually you just have to learn enough Figma+coding knowledge(see this in the discussion) to control the visuals yourself?

reddit.com
u/Appropriate-Being151 — 3 days ago

After 7 days of vibe coding, I learned to write better prompt and what actually good prompt looks like.

My early vibe coding prompts were dead simple. I'd type "build me an AI study planner" and wait. And the AI would give me something that looked okay, but obviously AI-made. Lately I've been trying to improve the first output by writing better prompts.

So I ran a small comparison to see whether prompts actually make a big difference in AI app builders(like Lovable, V0, Happyseeds etc).

Simple prompt: Build me an AI study planner. that automatically generates a daily schedule based on my exam dates and weak subjects.

Polished prompt: Build a clean AI study planning app for college students.The app should help students create a personalized study schedule from today until their exam dates. The student should enter their course names, exam dates, course difficulty, assignments, assignment deadlines, and available study hours.

The app should prioritize assignments first because they have deadlines. After assignment time is allocated, the app should distribute remaining study time across courses based on course difficulty and exam date. Harder courses and closer exams should receive more time, but the workload should stay balanced and realistic.

The generated plan should be shown as a daily checklist.

The difference was obvious. The one-line version(screenshots in the comments) looked like a generic demo. The second version felt closer to something I'd actually use. It had a clearer flow. The output also felt more useful because it separated today’s plan, weekly view, progress, upcoming assignments, and exams.

So this is what I've learned: Stop prompting like an app user, and start writing specs like a Product Manager briefing a senior engineer. Don't just describe what to build, try to think three layers:

  • Who & why: Anchor the AI. Who is this for and what is the exact goal? Remember to be specific (e.g. "College students" too general, try "MTI students who have 10 final exams and only a week left").
  • The logic: Define the rules. Describe the underlying data flow and prioritization (e.g. In my planer, "Deadlines first, then course difficulty"), not just how it looks.
  • The constraints : Explicitly state what not to do so the AI doesn't overcomplicate it.

How are other people handling this? If anyone has suggestions, or a better workflow for turning rough ideas into specific prompts, love to hear them.

u/Appropriate-Being151 — 5 days ago

What part of your affiliate workflow did you automate first without hurting conversions?

I started doing affiliate marketing recently and didn’t realize how much time the content side would take.

For one product, I might write a blog post, cut it into a few social posts, make a short video, then post across different platforms. After that, there are comments, DMs, and sometimes email follow-ups if someone seems interested.

None of this is hard by itself. It just gets repetitive fast when you’re doing it for every product.

I’ve tried using AI for rough drafts and basic replies, but I still have to edit most of it or it sounds off.

What did you automate or clean up first? I’m mostly thinking about video, replies, email follow-ups, and posting.

reddit.com
u/Appropriate-Being151 — 7 days ago

My AI affiliate workflow for testing one product before I scale it

I mostly promote home office products and try not to spend time on a full article or a batch of videos until I have tested one buyer-intent angle first.

A recent example was an ergonomic desk chair offer. I skipped broad keywords like “best office chairs” because that SERP is brutal. Instead, I looked for narrower angles, like small apartment desk chairs, mesh vs cushioned chairs, and chairs for long desk sessions.

Before making content, I check more than keyword difficulty. I look at the actual SERP, whether the current results really answer the buyer’s question, and whether the offer is even worth pushing: commission, cookie window, reviews, return policy, and any affiliate restrictions.

I use AI mostly for content structure, not the final copy. I give it the product specs, affiliate terms, keyword angle, and notes from competitor pages. Then I ask for an outline, objections to answer, comparison points, short video hooks, and a claims checklist. That last part matters with ergonomic products because I do not want to imply pain relief or posture benefits the product page does not prove.

For creative testing, I use PixVerse when I only have product photos and need a few quick video variations. Usually it is just a slow push-in, a product-in-room shot, or a simple desk setup visual. If the chair starts looking warped or different from the original image, I throw that version out.

I usually test 3 to 5 variations around the same angle, then adapt them for Pinterest, TikTok, Shorts, and sometimes LinkedIn. Each link gets UTMs so I can compare hooks and traffic sources.

Views do not mean much by themselves. I look at outbound clicks, time on page, affiliate link clicks, and whatever signal I can get from the merchant dashboard. If an angle gets attention but no qualified clicks, I either rewrite the hook or drop it. AI helps me test faster, but the actual affiliate work is still picking a decent offer, staying honest with claims, and not lying to myself about the data.

reddit.com
u/Appropriate-Being151 — 12 days ago

I'm going to stop mixing the same tools for work and side projects

I’ve been wondering if there’s a good way to physically separate work coding from side projects.

Currently I use the same setup for everything. But as soon as I open my usual dev environment to experiment with even the smallest hobby idea, its like my brain switches into work mode. It kills my mood pretty fast.

Feels like I need some kind of different, lighter environment setup for side projects, similar to how people use work laptops vs personal gaming devices.

Not sure if anyone else has solved this.

reddit.com
u/Appropriate-Being151 — 13 days ago
🔥 Hot ▲ 9.8k r/accidentalart+1 crossposts

How did eggs like this?

I had some beaten egg left in a bowl, and after sitting overnight it somehow formed strange crystal-like structures. The texture feels like spaghetti.

What on earth is this???

u/Appropriate-Being151 — 16 days ago
▲ 4 r/Music

Who have used both MobileSheets and forScore, how big is the gap really?

Here's the thing... everyone says forScore is the goat for gigging, but mobileSheets users seem happy with their setup. if i just need this for rehearsal, live performance, and basic annotations, how much am i actually giving up if i stay on android?

reddit.com
u/Appropriate-Being151 — 29 days ago