Skip to main content

6 posts tagged with "全栈"

全栈开发

View All Tags

Open Plugins: The Plugin Standard for AI Coding Tools

· 18 min read
Booker Zhao
Booker Zhao
AI Full-Stack Engineer / CloudBase AI ToolKit Author

One plugin standard, shared across seven tools.

Fig: Open Plugins — install once, works across seven tools

AI coding tools are multiplying: Cursor, Claude Code, Codex, Grok Build — each with its own plugin format. Then came Open Plugins.

It's an open standard maintained by Vercel Labs. Install one plugin, it runs across seven tools.

Codex grew 7x in 6 months and non-programmers are using it — here's how to go from zero to deployed multiplayer game

· 6 min read
Booker Zhao
Booker Zhao
AI Full-Stack Engineer / CloudBase AI ToolKit Author

This article covers four things: ① What Codex is and what it can do → ② Five-minute hands-on: build a playable game → ③ Core usage and features → ④ Connect low-cost Chinese open-source models and deploy your app so others can access it.

Short on time? Codex now supports DeepSeek, GLM, and other affordable models. Want to save money + one-click deploy? Jump to Step 4 and copy one config. Want the full picture? Read on.

Codex at a glance: from what it is, to configuring models, installing plugins, and deploying

Vibe Coding isn't a myth: non-developers can build real apps with AI too

· 6 min read
Booker Zhao
Booker Zhao
AI Full-Stack Engineer / CloudBase AI ToolKit Author

Ever run into this: AI generates your app, then it breaks and you don't even know what question to ask? AI gives you N solutions but you have no idea which one is right?

This is the pain point for many non-technical people using AI to code:

  • Debug hell: page shows something wrong, but no idea which layer is the issue (frontend? backend? deployment?)
  • Can't ask the right question: don't know how to describe the problem so AI understands and gives accurate answers
  • Unclear learning path: know you need some basics, but don't know where to start or what's enough

Today I'll share a systematic approach — from foundational concepts to debugging techniques to backend solutions — to take you from "able to generate apps" to "able to build real, usable apps."

Why does your AI code always need rework? SBE methodology has the answer

· 6 min read
Booker Zhao
Booker Zhao
AI Full-Stack Engineer / CloudBase AI ToolKit Author

My Kiro Spec Workflow guide blew up recently, and many people DM'd me: "Why is the Spec approach so effective? What's the theory behind it?"

Honestly, I'd been thinking about this too. Then I read Gojko Adzic's Specification by Example: How Successful Teams Deliver the Right Software, and it all clicked.

It turns out Kiro's Spec workflow is a perfect implementation of SBE (Specification by Example) methodology. Let me unpack this framework and fix your AI coding rework problem once and for all.