[Lalabadie]

Pet peeve because everyone seems to be doing this:

The video demo shows the operator asking for "same height", and then the agent sets a hardcoded 298px height instead of using any of the many reliable/solid ways to do it with CSS.

I'm sure there are better examples you could prompt to make that video convincing, though I appreciate the honesty showing what to expect.

[joshstrange]

Before I saw this comment I thought that's how it "fixed" it. I recorded my screen so I could slow it down and see what it said and sure enough:

    I've made the following change:
    1. Added a fixed height of `h-[298px]` to match the tallest card (which was 298px)

Screenshot: https://cs.joshstrange.com/d75pC236

This joins the ranks of prominent demos on the landing page that do the wrong or silly thing. It really makes it hard to take some things seriously.

That said, I like the overall idea of this. I think that Claude Code and friends will get way more powerful as we find ways to feed them better (not necessarily more) context.

[cyanydeez]

More context is not going solve this.

CSS requires understanding emerging properties of layout. So context doesn't help. Knowing how a variable expands a a div into a set of constraints isnt context dependent.

What you probably mean is a well designed model context which fits the most flexible and logical code framework.

Reading the last paragraph should make you realize the proposition isnt likely going to happen.

[faangguyindia]

Exactly, but do u think a model can be developed to deal with this?

[cchance]

feels like a case of a system prompt should be enforcing the AI to avoid usage of arbitrary numbers like specific pixel counts and to leverage modern css standard for sizes.

[juliangoetze]

that gave the best results so far - tweaking the system prompt to make sure the agent respects the project's ui system, is aware of dark mode and responsiveness, etc.

[juliangoetze]

Good catch - we could definitely put more effort into creating demos