正在加载视频...

视频加载失败

AI coding agents are great at building frontends, but they usually fail the moment you ask for a database or auth. You end up with a "cool demo" that doesn't actually work. I just tried InsForge 2.0, and it’s the first time I've seen an AI agent ship a...

82,745 次观看 • 8 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Building an app with AI? Learn these 4 parts first Want to build an app with AI? Learn the four parts first: the front end, the back end, the database, and where AI fits in a modern app. When you ask ChatGPT or Claude to build you an app (vibe coding, no code), these four parts are what you're actually describing. Explained for complete beginners. We follow one customer message through an online coffee store app, start to finish: 1. Front end: everything the customer sees and taps. The screens, the buttons, the text box. It doesn't know prices or stock. It shows things and passes messages along. 2. Back end: runs on a server the customer never sees. This is where the business rules live: login, stock, prices, payments. The front end asks, the back end decides. 3. Database: where everything is saved, like a giant spreadsheet that never closes. Products, prices, customers, orders. Only the back end opens it, and it checks who's asking. 4. AI in the middle: the back end calls the AI model only for jobs that need understanding. Job one, turn a plain sentence ("a gift for my dad, he drinks it black, under $40") into a search. Job two, write the answer using only the real products the database sent back. The rule for building reliable AI apps: AI handles the words, the back end handles the facts and the money. Never let the AI make up prices or stock. Whole app in four lines: the front end shows, the back end decides, the database remembers, the AI understands and writes. If you want to go from understanding the four parts to building your own apps with AI, I teach it step by step, from complete beginner to real systems. Check my profile. #vibecoding#buildwithai#claude#claudecode#aiagents #

Professor Glitch

94,500 次观看 • 3 天前

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 次观看 • 5 个月前