Загрузка видео...

Не удалось загрузить видео

На главную

Introducing GGEZ: The Nextjs for ThreeJS Games It's an open source framework which adds all the missing pieces to vibe code better ThreeJS games It has full codex integration, so a $20 ChatGPT sub is enough to build games! Literally "bun run start" and you have the full development...

44,009 просмотров • 7 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 просмотров • 4 месяцев назад

What if you could npm install 3D models? Introducing Vibe3D - the shadcn for threejs Starting with the scifi asset kit, over 180+ models, all free and oss (MIT licensed) and two reference terrain meshes. All models are installed directly into your codebase instead of pre-packaged as code imports or worse yet, FBX files 🤮 Docs: This means, a simple "bunx vibe3d add Artificial Intelligence Papers-kit/pressure-gauge" will install the fully procedural code Want to change something? just tell your ai to do it It uses some shared helper code to produce the topology and at least per kit all items reuse and share the same materials, so technically performance should be better than letting your ai run wild on its own. Also releasing with it two skills: - Vibe model skill to produce your own models and kits, just "bunx vibe-model --global" and tell your ai to vibe model some 3d assets with a reference photo, you'll see it works - Vibe terrain "bunx vibe-terrain" installs the terrain mesh modeler, yea just try it out, best results with opus 5 ngl Everything is MIT licensed, i was just joking, no hate for unreal or unity Threejs still the best tho 🖕🏻 If you just want to see all 3D models up close: Yea, you can also just vampire it and download all modes as .glb files, good luck fixing some of them then though Big thanks to ThreeJS Assets for contributing 50 assets to the scifi kit! Everyone who spends some tokens on it will be added to the contributor list Oh and before i forget fuck you kenney, we roll our own kits now

robot 2.0

59,393 просмотров • 2 месяцев назад

EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on The Startup Ideas Podcast (SIP) 🧃 where you get your pods watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?

GREG ISENBERG

69,596 просмотров • 5 месяцев назад

How I get shit done, Episode 001 I've set up a playbook called ‘land’, which is triggered automatically when I drag an issue into the merging column in Linear. That reliably runs CI and merges any green PRs. This has allowed me to ship way faster than before. I think the key takeaway here is you can try to build your own code factory and your own agent orchestration layer, but it is a huge amount of work. The truth is there are entire companies with massive funding that are already tackling this and it's just easier to use their platform. I think this is a lot like if you were a carpenter: you could build your own generator, fuel it, wire it up, and then build a plug and then you could plug your saw into it. Or you could just plug your saw into the wall. Because the electricity company has already done all the work in the infrastructure and investment to make that plug work. I think more of us who are building companies should just be plugging into the wall instead of trying to build all this tooling ourselves. As a dev it's so tempting to build your own dev tools but I think a lot of times, even though you can build fast with agents now, it's a complete waste of time. It probably sounds like I'm being paid by Devin or something but I have zero financial interest here. They don't give me credits. I'm not an investor. I'm not being paid. I just think the tooling is really damn good. If you used Devin a long time ago and wrote it off, you really should have another look - for $500/month it's pretty obscene what you can get done.

Ryan Carson

14,059 просмотров • 7 месяцев назад