M Tayyab

When you call customers, the first thing you often hear is a call screener, voicemail, an automated menu, or a "number switched off" message. In our own test of about 2,700 real calls, that was nearly 18%.

An agent who doesn't notice starts talking to a machine, wasting money and sounding silly.

Now it recognises what it is talking to and reacts:

- Call screener: introduces itself, then waits for the person.

It's so easy to fall into the trap of over engineering a quick weekend project just to keep the styling under control. A massive design system feels like total overkill when you're just testing an idea but without some rules the third screen always looks like a completely different app. I've started keeping a basic note with just a few color and spacing constraints to feed the assistant.

What is your go to trick to keep your UI looking clean without slowing down your build speed?

I've noticed this exact same drift when building apps with AI lately.

The landing page looks gorgeous because you spent time prompting it right, but by the time you're deep into page three buttons start changing shapes, fonts look slightly off, and margins get all over the place. I tried dropping a tiny style guide into the project instructions, but the AI still slips up if a prompt gets too long.

For those building fast with AI, do you use a strict component library from the start, or just keep rewriting CSS rules as you go?