u/Lanky-Lie-6795

I started building SaaS apps around November last year. My first app actually made money for 6 days straight, which felt unreal at the time.

Then in December, I built another SaaS and ended up selling it for a decent amount. But this year... completely different story.

I launched 4 more apps since then and combined they have made barely 20usd. It's not like I stopped working, I learned a lot, built more, improved my skills. Learned how to implement Stripe subscriptions, optimizations, and others. But looking at the results, it feels like I went backwards...

When I started, I was posting consistently and no AI slop posts at all. Recently I've been posting less and probably in the wrong places too.

Now I'm kind of resetting mentally back to "day 0", because I want to focus more on distribution, writing my own posts again. I'm still very motivated, I am writing down my little ideas every single day.

It's hard to stay motivated while being stuck. Although I will not give up my dreams, I want to achieve again these goals what I achieved in the first two months.

Have a great day and thanks for reading this post.

The problem with current AI coding agents for UI work: they don't know your context.

When you ask Claude Code, Cursor, or any other agent to "build a dashboard sidebar," you get something that compiles but is completely off — wrong component hierarchy, no awareness of your existing design system, generic placeholder copy. Then you spend 5 rounds correcting it.

The root cause is that agents are flying blind. They don't know:

• Which components already exist in your codebase
• Your tech stack constraints (Tailwind only, no inline styles, specific component library, etc.)
• What each piece of UI is supposed to do
• How sections relate to each other visually

My approach: plan the UI first in a visual canvas, then generate structured XML context from that plan. The XML goes into the agent as a system prompt with sections for frames, frameworks, mandatory constraints, and visual profile.

Instead of "build me a hero section," the agent gets a precise machine-readable spec of what you want. The quality difference is significant — first-pass outputs actually match the intended structure.

Also ships with an MCP server so Claude Code users can pull the project context directly in the terminal without copy-pasting anything.

Link in comments per sub rules.

Been thinking about this a lot lately. Every time I start a new AI coding session, the agent has no idea what colors, spacing, or component rules my project uses. It guesses - and it guesses wrong.

I ended up building a tool called UIPrompt that exports your design tokens, stack, and UI frame structure into a single structured context block. You paste it at the start of a session and the agent immediately understands your visual system.

It produces output like this:

<design_tokens>
  colors: #111111 primary, #6f6f6f muted, #ffffff background
  spacing: 4/8/12/16/24/32px
  typography: 400/500/600/700
</design_tokens>
<mandatory_constraints>
  x No placeholder copy
  x No hallucinated icons or emoji
  x Responsive by default
</mandatory_constraints>

The difference in output consistency is real. The agent stops inventing hex values and starts respecting your actual system.

uiprompt.app

Curious how others here handle this - do you have a system for keeping AI output on-brand?

Every new AI coding session starts cold. No memory of your colors, fonts, component rules, or constraints. You either paste the same context block manually every time, or you accept inconsistent output.

I got tired of this and built UIPrompt. You define your project once - design tokens, tech stack, UI frame structure, mandatory rules - and it exports a structured context block you paste at the start of any AI agent session.

The agent immediately knows: your color palette, your spacing scale, your frameworks, what it must never do (placeholder copy, hallucinated icons, etc.).

Output quality went up noticeably. Fewer corrections per session.

Launched it at uiprompt.app. Still early but people are using it.

Curious if others here have hit the same problem or solved it a different way.