ismail9k/vibe-coder-survival-guide

Vibe Coder's Survival Guide is a written guide, not a piece of software, aimed at people who build real projects by describing what they want to an AI assistant and getting working code back. Its target reader can get code to run but does not know which other tools a real project usually needs, or why. The guide exists to close that gap: for example, explaining that instead of asking the AI to make your code neat, there is a whole category of tool called a formatter built for exactly that job. The guide is organized as a set of linked pages rather than one long document. A learning path takes a total beginner from fundamentals to shipping in order. If you already know what kind of thing you are building, you can jump straight to a page for web, mobile, backend, or AI apps. A universal toolbelt page covers the tools every project needs regardless of domain, and a glossary explains any jargon in plain language. The guide is deliberately opinionated: for each job it names one default tool rather than a menu of options, chosen by three rules in order: the tool should be one AI assistants already handle well, it should be easy for a beginner to learn with good documentation and a large community, and it should have a free tier so you can start without a credit card. Underlying all of this is a stronger rule the guide calls buy or glue, don't build: things like authentication, payments, image hosting, and email are treated as solved problems you should use a hosted service for, and you should only build something yourself once you hit a real limitation those services cannot solve. The guide standardizes on TypeScript as the one language used across its web, mobile, backend, and AI app sections, so the same knowledge carries over between domains. Its stated bias is shipping fast and learning, not enterprise scale, and it is upfront about which tools are overkill for a beginner rather than hiding them.