Y Combinator Startup Podcast
00:22:21 · Aaron Epstein, Stephen Haney
[00:22:21] S1: Mhmm. [00:22:21] S0: For instance, like, see, like, the first shot, it ran the text over the cards. It'll usually catch that and correct it. Or if it doesn't, you can just, you know, tell it, hey. Correct the the text overflow. Mhmm. Let me do this. I'm set to fit, and we'll pop back in Conductor. Please address any text overflow issues. The other thing I noticed too is is the models are always getting better, they have different strengths and weaknesses. Mhmm. And so I I often use fast models for demos like this Mhmm. And they tend to make more mistakes. And so, you know, if you're doing this for real, you're probably using something that's right at the cutting edge, and those prove to deliver, you know, better performance. [00:22:57] S1: Yeah. What are your go to models these days?
00:22:57 · Aaron Epstein, Stephen Haney
[00:22:57] S1: Yeah. What are your go to models these days? [00:22:59] S0: So Fable is a wonderful... You know, I think that's probably the best visual taste right now. Yep. It's very slow. That's why I don't use it for demos. Yeah. I use Cursor as a Composer 2.5 Mhmm. Actually a lot. It's a very good model for the speed. Quality is very good, very precise. 5.5 is still usually a pretty good balance. So I jump around. I think if I need pure taste, it's the Fable and the anthropic models in general. If I'm going for precision or I have like, hey, have 100 artboards and I need a task to go down the entire list, I might reach for the composer. It it just does a really precise job. I find cursor is a really good harness. It... It's not too lazy. It'll often spin up sub agents to get jobs done. Yeah. So I jump around a bit. So here, it gave me kinda like three different ideas. You know? And I think from here, what I would usually do, spend a little more time on exactly what I actually want out of out of it and then give it more direction. But I might start branching. I might be like, oh, I like this. I like... You know, I kind of like the list of this. That's actually very easy to read. I have kind of like... The card layout of this actually, like, featuring one card and having some other cards to the side is nice. So I might just start branching. And think the power of this is you can ask five agents to go generate five more of each, you know, and and kind of find one that really fits
00:24:10 · Aaron Epstein, Stephen Haney
[00:24:10] S1: Yeah. What you're going for. I think one of the things that's interesting is it gives you a lot of, inspiration and ideas, and then you can start branching and going down a path. But it's still the models that's doing the design, and it still has some of the hallmarks of the things that you see Yeah. Models do frequently for better or for worse. And so how do you... When you're designing and you've got this inspiration, you're like, okay. This list is interesting. I hadn't really thought of doing that. Maybe I wanna go with that. How do you then make it more your own and get out of kind of the the standard slop that a lot of them will spit out? [00:24:44] S0: Yeah. Well, I have some, like, very specific rules I can share with you. One is that models love bold. They love bold styles. And and, really, like, try to pull your font weights back. You know? It's so tempting to bold things. Just try to pull them back as light as you can get, and it'll just magically look better designed. Another thing is too many too many sizes. Models love having five, six, seven, eight different font sizes. Yeah. Try to work with three. If you get down to three... So let's let's just try it real quick on this one. If we if we bring this down to, let's see, like, like, a 500. Even that's maybe heavier than it needs to be. Same here. Like, these don't actually need to be bold. This is such a tell of a of a... This one [00:25:23] S1: up here. The care [00:25:23] S0: organized black is so heavy. Let's just pull that back, and suddenly it looks more designed already. Right. Right.
00:25:23 · Stephen Haney, Aaron Epstein
[00:25:23] S0: organized black is so heavy. Let's just pull that back, and suddenly it looks more designed already. Right. Right. [00:25:29] S1: It looks cleaner. [00:25:30] S0: It looks cleaner and more approachable. Black here too. Let's just pull that back. These are really simple tweaks that, like, you can make. The contrast here is pretty good. A lot of times models screw up contrast. Yep. So I would... That's another step. You can just make sure it's like, is the text readable? [00:25:44] S1: Right. [00:25:44] S0: These these little two, three, four, these are a little too contrasty for my taste. I would probably pull these these back. They're supposed to be a [00:25:51] S1: supporting delete them? I mean, those are the kind of things where the models like to add numbers or little icons or things like that there. And, yeah, it's really cool that you can just go through and delete it, and it just snaps everything else up rather than leaving a blank space there.
00:25:51 · Aaron Epstein, Stephen Haney
[00:25:51] S1: supporting delete them? I mean, those are the kind of things where the models like to add numbers or little icons or things like that there. And, yeah, it's really cool that you can just go through and delete it, and it just snaps everything else up rather than leaving a blank space there. [00:26:03] S0: Totally. Totally. Well, that's one of the powers of of of this tool in general is that Paper is a design tool first. It's a human design tool first that happens to be really, really good with agents. Mhmm. And so that means you can customize whatever you need to do. It's... You're not stuck with, like, the track you're on. You don't you don't prompt again. You can start reaching in and and changing things. So, yeah, a 100% agree. Maybe get rid of that one too. The first thing I do is is try to get down to, three font sizes and just pull all that bold way back. Yep. And you'll immediately get something that feels more designed and intentional. [00:26:30] S1: Yeah. Yeah. And then what do you do from here? Great. You've got the new section. You're excited about it. How do you then wrap it back in?
00:26:30 · Aaron Epstein, Stephen Haney
[00:26:30] S1: Yeah. Yeah. And then what do you do from here? Great. You've got the new section. You're excited about it. How do you then wrap it back in? [00:26:36] S0: Well, so there's a couple of ways. You can you can right click and, let me actually grab here. You can copy it as React. Mhmm. So that's kind of the long way, though. So I can get this out as code and paste it into my IDE. You can also just ask the agent to pull this back. So I have the Paper code base open. But you can just say, please build my selection in Paper into a new component in the code base, which we will not actually ship in Paper. It can read everything that we just did. And it knows my code base really well because it's the agent that I use. And so it can actually pull in this design, it'll match the coding styles that we have and the conventions that we have and build it into the code base. And if it already existed, usually you would already have this as a component, and we just update it. And it's really, really fast. So we see a lot of people are just like, this is the whole loop now. There isn't even a handoff anymore. It's just one person making these changes and iterating and shipping, which is really cool. I think really it's cool. [00:27:30] S1: Yeah. That's what's so powerful is, you know, it's easier than ever for designers to actually build and ship things in the way that they see it. [00:27:38] S0: Yes.