{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Lenny’s AI Builders","title":"Kimi K3.1 Pro just dropped - i made it race Opus 5.5 to build one game | LAB 0029","html":"","width":"100%","height":180,"duration":844,"description":"Kimi K3.1 Pro just dropped, so i gave it and Opus 5.5 the exact same prompt: build me a 3D game where you're a Perth plumber racing to call-outs. one game cost $1.08, the other $3.21 (API-equivalent, one shot each), and only one of them got Perth. i play both blind before i tell you which model built which.\n\nalso this week: OpenAI paused its best models for 11 days after a settings mistake gave one a little bit of internet during training, Cursor's agents can now drive your whole computer, Block's Dessa is the most human AI voice i've heard (waitlist only), and Grok Bot's new Vault can sign in and check out for you.\n\nthe practical - one prompt that makes your site work on the iPhone Duo's big inner screen. paste it into Claude Code inside your project. it screenshots every page at the Duo sizes before it changes anything, writes a check that fails first, fixes it until it passes, and leaves your normal phone and desktop layouts alone. on my site, 9 checks failed before the fix and all 18 passed after. the catch: those Duo sizes come from a simulator, not Apple, so measure your own Duo first and put your numbers in the prompt.\n\nthe prompt:\nmake this site work well on the iphone duo's big inner screen. work on a new git branch, draft only: never push, merge or deploy.\n\n1. find every width breakpoint in the code and list them.\n2. run the app locally. with playwright, screenshot every main page at 382x580, 669x825, 870x669, 951x543, plus a normal phone (390x844) and desktop (1440x900), before changing anything. save them in a before folder.\n3. add a fold layout for screens roughly 600 to 1000px wide. where the app has a list plus detail, or a sidebar, show two panes side by side. make every tap target at least 44px, make sure nothing hides under fixed buttons, and respect safe-area insets (left and right).\n4. write a playwright check for those rules (no sideways scroll, tap targets, two panes). run it first and show it failing. then make the fix and show it passing....","thumbnail_url":"https://img.transistorcdn.com/P0B9fKUWl01KOkVXqQcDv5YBEKR1sflq-Hk71z-fa_U/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS84MzAx/ZGNmYzY1MmEwNjBk/NzUzN2NmODM3ZWUx/YzMzZi5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}