korrents

korrents · Dive Club

Meng To - Codex superpowers for designers

Meng To · 35m · youtube.com ↗

18 korrents from this recording

Meng To did not write this page.

Every claim below is a statement made in this recording, quoted word for word and linked to the second it was said, so you can hear it rather than take our word for it. The wording comes from the transcript published alongside the recording; the sentence above each quote is our reading of the claim, not their wording.

  1. 7:08 · watch on youtube.com↗

    I think designers have to build their own tools because the tools that we have are never good enough.
  2. 3 min later
  3. 10:22 · watch on youtube.com↗

    because Codex works really well locally and agents can do it far more powerful than any private walled garden that exists out there in the cloud
  4. 10:43 · watch on youtube.com↗

    I don't plan things. I don't like have a giant blueprint where I just plan all the ideas in advance uh because when when you work solo, this is your superpower like this is how you move away faster than anyone else.
  5. 2 min later
  6. 12:46 · watch on youtube.com↗

    A skill is is basically a prompt, sometimes a large prompt. You can think about what is the best like what is the best practice. It's more like a style guide. What is the best practice for taste, which font to use, you know, how do you guide AI to not create AI slop. So, the skill would be great for that.
  7. 13:03 · watch on youtube.com↗

    The thing is that if you always chase the trends, you will become AI slop very soon. So, my suggestion to you is always be a step ahead. It's like playing chess. You have to be always a step ahead of what is the baseline.
  8. 1 min later
  9. 13:47 · watch on youtube.com↗

    So you have to always be ahead. And the only way you can be ahead is just to to to spend that last 10%.
  10. 1 min later
  11. 14:30 · watch on youtube.com↗

    when you have a starting point, your AI will stop making AI slop because your starting point is you
  12. 1 min later
  13. 15:05 · watch on youtube.com↗

    The reason why is very simple, it's because the screenshot is the fastest, easiest way to build without having to voice it, without having to type it.
  14. 1 min later
  15. 15:47 · watch on youtube.com↗

    how knowledgeable are you of your product? Because if you're not knowledgeable about your product, forget it. You're not going to do anything meaningful, and someone else in 3 months' time will do exactly what you're doing in one prompt.
  16. 1 min later
  17. 17:08 · watch on youtube.com↗

    you will never find something like this in an existing library. Why? Because it's not part of that personality or that experience that you you yourself have by watching Apple work or by watching your best friend designer work
  18. 1 min later
  19. 18:23 · watch on youtube.com↗

    So part of the skills nowadays is to be able to talk to AI in the most efficient way possible. And one of the ways is just yeah, take screenshot, use your voice because when you use your voice you can explain things much clearer instead of saying go here and because you're lazy to to type all of that stuff, you don't add all of those details that you can speak uh like three or five times faster.
  20. 6 min later
  21. 24:07 · watch on youtube.com↗

    This used to have you needing to learn all about these libraries, these animation terms. Now, you know what our team use? They use a video. They give the AI a video, and they ask the AI, "How should I prompt this animation?"
  22. 1 min later
  23. 25:09 · watch on youtube.com↗

    There is zero difference between that landing page and one created by Opus 4.8 or Sonnet 4.6 or 4.5. The reason why is because it's like you're using someone far too powerful for a simple task. The only way you can utilize these super intelligent model is by giving a giant piece of prompt, literally.
  24. 1 min later
  25. 26:21 · watch on youtube.com↗

    all the designers, they have a style guide. It's kind of like their guiding principle of their mastery of a designer. Right? You go to school, you you work on 10,000 designs, you have embedded in your blood that design language, that style guide. The design.md is basically all of that sweat, tears, and blood into one markdown file that the AI can read.
  26. 26:50 · watch on youtube.com↗

    if you're using a model like Mythos fable five, then you give something like design MD, it will understand it and it will be able to take it to the next level. If you use a base model, it won't understand it.
  27. 3 min later
  28. 29:36 · watch on youtube.com↗

    design.md is powerful at the beginning, but when you're doing a lot of iterations really quickly, you don't want to always reference that. You can totally save that into your agents.md.
  29. 1 min later
  30. 30:57 · watch on youtube.com↗

    You have a main agent.md for all of the things. So, you can totally go to settings and go to your configuration and then put that into you. That it's a bit dangerous because it's red for every single problem or every single new project.
  31. 2 min later
  32. 33:06 · watch on youtube.com↗

    But most importantly, have a an endless amount of of curiosity about what's going on and how you can perfect your own workflow because it keeps evolving. And because it keeps evolving, it always requires your attention.