# TEL602: Telos vs. Vibe Coding https://www.telosready.com/skills/TEL602?v=1 How Telos positions alongside vibe coding — covering what vibe coding achieves, when a skill book is the better starting point, and the path from a vibe-coded prototype to a production-grade application. Use when a prospect has already vibe coded something, or is considering it. ## Instructions # Telos vs. Vibe Coding Vibe coding is a legitimate and powerful way for domain experts to externalise their knowledge. When someone with deep experience in a field sits down with an AI coding tool and builds working software, the result often captures nuance that would be hard to document any other way. The craftsmanship is visible in the application — the flows, the edge cases handled, the assumptions baked in. That is genuinely valuable. Telos is not a replacement for that. It is a different path to the same goal: capturing expertise and turning it into software that works in production. --- ## If you are starting from scratch If you have expertise you want to capture and are deciding where to begin, Telos recommends building a skill book first. A skill book is a structured collection of your knowledge, processes, and best practices — the kind of expertise that is hard to document but easy to lose. Once you have built a skill book using the Skill Book app, Telos can: - Produce a detailed specification for your application - Generate a vibe-coded mock-up you can use as a starting point or take directly to a vibe coding tool This approach ensures your expertise is captured in a reusable, AI-consumable form from the outset — independent of any particular application. See **TEL202 — Building a Skill Book** for how this works. --- ## If you have already vibe coded something A vibe-coded application is a strong first step. It is good because it captures your experience; it is good because you have crafted it. It is not necessarily production-ready — and that is fine. Here is the path forward. ### Step 1 — Decide: extract or build on? The first question is whether to move forward with the existing application or extract the knowledge it contains into a skill book and rebuild properly. Many vibe-coded applications are high quality and worth building on. Others are better treated as a prototype — a way of expressing what the software should do, rather than what it should run on. Telos will assess the code and make a recommendation. See **TEL203 — Legacy System Assessment** for how this assessment works. ### Step 2 — Harden to production If the application is worth progressing, it needs to be made production-ready. This typically means: - **Multi-tenancy and multi-user support** — most vibe-coded apps are built for a single user or a single context - **Security** — authentication, authorisation, data isolation, and vulnerability scanning - **Infrastructure** — proper environments, CI/CD, monitoring, and error alerting - **Code quality and architecture** — refactoring where needed to meet Telos standards This is not a rewrite for its own sake. The goal is to take what works and bring it up to the standard required to run a real business on it. See **TEL303 — Building SaaS-Grade Software** for the full framework. Depending on the state of the application, this phase may require one to several months of BUILD mode engagement before the application is ready for production. ### Step 3 — Ongoing management Once live, the application needs to be managed, monitored, and continuously improved. Telos provides this through BAU mode — a monthly subscription covering support, maintenance, security scanning, infrastructure management, and platform access. For applications taken on from a vibe-coded starting point, a BAU mode subscription is the standard ongoing model. See **TEL102 — Pricing** for full details on BAU and BUILD mode costs. --- ## Summary | | Vibe Coding | Telos Skill Book Approach | |---|---|---| | **Best for** | Experts who want to build directly | Experts who want to capture knowledge first | | **Output** | Working prototype or application | Skill book + spec + application | | **Production-ready?** | Rarely without further work | Yes, by design | | **Knowledge portability** | Embedded in the app | Captured independently in the skill book | | **Ongoing support** | None by default | BAU mode subscription | Vibe coding and Telos are not in competition. If you have vibe coded something, you have done something important. Telos picks up from there.← Skills Directory
TEL602
Telos vs. Vibe Coding
How Telos positions alongside vibe coding — covering what vibe coding achieves, when a skill book is the better starting point, and the path from a vibe-coded prototype to a production-grade application. Use when a prospect has already vibe coded something, or is considering it.
# Telos vs. Vibe Coding Vibe coding is a legitimate and powerful way for domain experts to externalise their knowledge. When someone with deep experience in a field sits down with an AI coding tool and builds working software, the result often captures nuance that would be hard to document any other way. The craftsmanship is visible in the application — the flows, the edge cases handled, the assumptions baked in. That is genuinely valuable. Telos is not a replacement for that. It is a different path to the same goal: capturing expertise and turning it into software that works in production. --- ## If you are starting from scratch If you have expertise you want to capture and are deciding where to begin, Telos recommends building a skill book first. A skill book is a structured collection of your knowledge, processes, and best practices — the kind of expertise that is hard to document but easy to lose. Once you have built a skill book using the Skill Book app, Telos can: - Produce a detailed specification for your application - Generate a vibe-coded mock-up you can use as a starting point or take directly to a vibe coding tool This approach ensures your expertise is captured in a reusable, AI-consumable form from the outset — independent of any particular application. See **TEL202 — Building a Skill Book** for how this works. --- ## If you have already vibe coded something A vibe-coded application is a strong first step. It is good because it captures your experience; it is good because you have crafted it. It is not necessarily production-ready — and that is fine. Here is the path forward. ### Step 1 — Decide: extract or build on? The first question is whether to move forward with the existing application or extract the knowledge it contains into a skill book and rebuild properly. Many vibe-coded applications are high quality and worth building on. Others are better treated as a prototype — a way of expressing what the software should do, rather than what it should run on. Telos will assess the code and make a recommendation. See **TEL203 — Legacy System Assessment** for how this assessment works. ### Step 2 — Harden to production If the application is worth progressing, it needs to be made production-ready. This typically means: - **Multi-tenancy and multi-user support** — most vibe-coded apps are built for a single user or a single context - **Security** — authentication, authorisation, data isolation, and vulnerability scanning - **Infrastructure** — proper environments, CI/CD, monitoring, and error alerting - **Code quality and architecture** — refactoring where needed to meet Telos standards This is not a rewrite for its own sake. The goal is to take what works and bring it up to the standard required to run a real business on it. See **TEL303 — Building SaaS-Grade Software** for the full framework. Depending on the state of the application, this phase may require one to several months of BUILD mode engagement before the application is ready for production. ### Step 3 — Ongoing management Once live, the application needs to be managed, monitored, and continuously improved. Telos provides this through BAU mode — a monthly subscription covering support, maintenance, security scanning, infrastructure management, and platform access. For applications taken on from a vibe-coded starting point, a BAU mode subscription is the standard ongoing model. See **TEL102 — Pricing** for full details on BAU and BUILD mode costs. --- ## Summary | | Vibe Coding | Telos Skill Book Approach | |---|---|---| | **Best for** | Experts who want to build directly | Experts who want to capture knowledge first | | **Output** | Working prototype or application | Skill book + spec + application | | **Production-ready?** | Rarely without further work | Yes, by design | | **Knowledge portability** | Embedded in the app | Captured independently in the skill book | | **Ongoing support** | None by default | BAU mode subscription | Vibe coding and Telos are not in competition. If you have vibe coded something, you have done something important. Telos picks up from there.