Vibe Coding não funciona (Novo Workflow no Claude Code)

Vibe Coding não funciona (Novo Workflow no Claude Code)

Workflow for Creating Professional Applications with Cloud Code

Introduction to the Workflow

  • The speaker introduces a complete workflow used for creating professional applications using cloud code, contrasting it with Vibe Coding.
  • Highlights the success of a product called Epic New, which gained 300 users in one day and was developed entirely with AI.

Steps in the Workflow

  • The first step involves writing a specification (spec), detailing all pages, components, and user behaviors to clarify what will be built.
  • The spec is then broken down into smaller tasks to prevent overwhelming the cloud code during implementation.
  • Each task requires planning that includes reusing existing code and consulting external documentation for proven implementation patterns.

Importance of Task Management

  • The speaker acknowledges that this structured process may seem bureaucratic compared to Vibe Coding but emphasizes its effectiveness based on testing various approaches.
  • Discusses common pitfalls in Vibe Coding, such as assigning overly large tasks that can lead to failures due to context overload.

Common Issues Encountered

  • A frequent issue is generating messy code; AI tends to complicate simple tasks or create unnecessary implementations instead of following documented patterns.
  • Another problem is repetitive code generation where AI fails to recognize previously written components, leading to maintenance challenges.

Miscommunication with AI

  • Users often express frustration when AI does not follow instructions correctly; this stems from unclear communication about what files need modification or creation.
  • Emphasizes the importance of specifying exact files for modification rather than vague requests like "create a signup," which can lead AI astray.

Understanding Common Issues in Coding Projects

Challenges in Small vs. Large Projects

  • In small projects with limited files (e.g., 20), it's statistically easier for AI to find the necessary code. However, as project size increases, locating specific files becomes more challenging.

Problems with Code Modularity

  • A common issue is fixing one part of the code while inadvertently breaking another, often referred to as "cobertor de pobre" (poor man's blanket). This occurs when multiple responsibilities are combined instead of being modularized.
  • Lack of modularization leads to intertwined functionalities, making it difficult to modify one aspect without affecting others. Developers understand this principle, but non-developers may not recognize its importance.

Security Vulnerabilities

  • Security flaws often arise from poor coding practices, such as placing business logic on the front end or exposing sensitive keys. These vulnerabilities can lead to hacking incidents that are frequently reported online.
  • Anything on the front end can be accessed easily through a browser; thus, sensitive information like database keys should never be exposed there.

Solutions to Common Coding Problems

Breaking Down Tasks for AI

  • To address issues with large implementations where AI struggles, break down projects into smaller tasks. This approach helps maintain context and improves performance.

Avoiding Code Duplication

  • To prevent messy code caused by duplication:
  • Run searches within your project to identify reusable code snippets instead of creating new ones from scratch.
  • Request documented implementation patterns from AI to ensure established solutions are utilized rather than reinventing them.

Directing AI Effectively

  • Clearly specify which files need modification and what changes should be made. Providing precise instructions minimizes the risk of unintended alterations in unrelated areas.

Ensuring Functional Isolation

  • Implement an architecture organized by behavior to isolate functionalities effectively. For example:
  • Separate folders for different behaviors (e.g., login and password recovery).
  • This structure allows focused troubleshooting without impacting other functionalities.

Addressing Security Practices

  • Emphasize client-server architecture principles where business logic resides on the back end rather than the front end. This practice enhances security by preventing unauthorized access to sensitive operations and data.

Understanding Frontend and Backend Interaction

The Role of Frontend and Backend

  • The frontend captures user intentions through clicks and interactions, while the backend processes these requests. The frontend does not control business logic.
  • It is crucial to avoid hardcoding sensitive information like API keys in the frontend to prevent unauthorized access.

Common Problems and Solutions

  • A summary of common issues encountered in Vibe Coding is presented, along with solutions for each problem.
  • The speaker plans to demonstrate practical applications using cloud code, emphasizing a step-by-step approach.

Creating Specifications for Projects

Writing a Specification Document

  • The first step involves writing a specification (spec), which outlines the project details. This includes an overview of the application being developed.
  • For example, a chat application allows users to interact with various AI models. Each page and its components are listed within this spec.

Breaking Down Tasks from Specifications

  • After creating the spec, it is broken down into smaller tasks or "issues" that can be implemented individually.
  • Each behavior described in the spec translates into a task, facilitating organized development.

Implementation Process Overview

Prototyping Phase

  • Initial tasks focus on prototyping; only front-end screens are created without functional implementation to ensure layout correctness before adding functionality.

Planning Tasks Efficiently

  • A command called "plan" is executed to search for reusable code snippets within the project and external documentation, preventing redundancy in coding efforts.

Detailed Task Descriptions

Enhancing Task Clarity

  • Each task description includes scenarios such as happy paths and error cases, detailing expected behaviors under different conditions.
  • Additionally, necessary database tables and their columns are specified alongside any required file modifications or external dependencies.

Planning and Implementation of AI Tasks

Overview of Planning

  • The speaker emphasizes the importance of a clear task list in planning, stating that it summarizes what needs to be done for an ISO (Information Security Officer).
  • A well-defined description of files is crucial; the AI will only act on specified files, preventing unintended modifications.

Ensuring AI Compliance

  • The speaker promotes a new product that consolidates all necessary prompts and skills for building effective AI products, encouraging viewers to create an account.
  • After planning, execution begins with a command that implements the planned tasks.

Utilizing Agents and Skills

  • Each project layer has dedicated agents with specific skills; for instance, database tasks are handled by a model writer agent.
  • Documentation is maintained for each file type's rules and descriptions to guide the implementation process effectively.

Importance of Documentation

  • A "references" folder contains essential documentation like architecture design and workflow specifications to ensure adherence to best practices.
  • Proper documentation helps direct the AI on project organization, minimizing errors during implementation.

Maintaining Code Quality

  • Following architectural guidelines ensures isolation of behaviors and prevents business logic from being placed in the front end.
  • The structured approach addresses common issues faced when using AI in coding projects by breaking down large tasks into manageable parts.

Conclusion on Process Effectiveness

  • The methodical planning reduces code clutter while enhancing quality through documented standards.
  • Clear instructions regarding which files can be modified prevent unwanted changes during task execution.

Addressing Security Concerns

  • Architectural documentation also mitigates security risks by ensuring compliance with established best practices throughout development processes.
  • Specialized agents are employed for testing to uphold security measures without compromising other aspects of the project.

Summary of Key Steps

  • The initial step involves writing a specification that outlines page behavior and component requirements as part of effective project management.

How to Create Professional Projects in Cloud Code

Project Planning and Implementation Process

  • The process begins with writing a specification (spec), which is then broken down into smaller tasks. Before implementing each task, a planning phase occurs that includes research both within the existing codebase and externally.
  • Each task is executed using specialized agents and skills tailored to the software architecture, ensuring that the code remains clean and maintainable.
  • Utilizing supporting documents with clear architectural rules and design principles helps ensure the creation of professional projects that are maintainable over time.
  • Emphasizes the difference between creating simple prototypes versus complex production-ready projects; poor organization can lead to significant issues when problems arise.
  • Following this structured process allows for adaptation to individual project realities, enhancing codebases effectively.

Introduction of Epic New

  • If users prefer not to create their own workflow, they can utilize "Epic New," a new project introduced by the speaker, which offers a ready-made solution for managing workflows.
  • Epic New consists of two main components: Epic Learn (educational sessions with recorded and live classes on project implementation) and Epic Builder (a set of skills, agents, and prompts).
  • Epic Builder provides access to the same workflow demonstrated in the video without needing users to recreate it from scratch.
  • Interested individuals can sign up for a free account through a link provided in the video description to explore the platform further.

Conclusion

  • The speaker encourages viewers who enjoyed the content to like the video and share their thoughts in comments.
Video description

🪽 Acesse o Epic (e use o mesmo workflow desse vídeo): https://epic.new 🤖 Vibe coding parece rápido, até você tentar lançar um produto de verdade. Aqui está o workflow que eu usei pra construir o Epic do zero com IA, sem nenhuma linha de código manual. ⏱️ TIMESTAMPS: 00:00 Intro: O Workflow Anti-Vibe Coding 02:16 Os principais problemas do Vibe Coding 02:54 Código bagunçado 04:12 IA não obedece 05:38 IA arruma uma coisa, mas quebra outra 06:34 Gafes de segurança 11:10 O meu processo na prática 12:25 Quebrando a Spec em Issues 13:42 Pesquisa e planejamento 16:33 Acesse os comandos + Crie sua conta no epic.new 16:53 Executando as Issues 19:04 Como esses problemas são resolvidos 21:03 Conclusão: Como usar o meu workflow 22:36 Tenha acesso ao meu workflow no epic.new! 🎯 O QUE VOCÊ VAI APRENDER: ✅ Por que a IA engasga com tarefas grandes e como evitar isso ✅ Como impedir que o código gerado vire um pesadelo de manutenção ✅ Por que a IA "desobedece" — e o que você deve dizer pra ela realmente te obedecer ✅ Como isolar funcionalidades para não quebrar o que já funciona ✅ Quais são as gafes de segurança mais comuns no vibe coding e como blindar seu app ✅ Como escrever uma Spec e quebrá-la em Issues acionáveis com Claude Code ✅ Como usar agentes e skills especializados para implementar com qualidade profissional 💡 POR QUE ISSO IMPORTA: Qualquer pessoa consegue fazer um protótipo com vibe coding — o problema é quando você quer lançar algo de verdade. Esse workflow nasceu de meses de tentativa, erro e observação dos padrões que destroem projetos feitos com IA. Se você quer construir com IA de forma sustentável, esse processo é o caminho. 🪽 SOBRE O EPIC: O Epic é a plataforma onde você aprende e aplica o workflow que eu uso pra construir aplicações profissionais com IA — com aulas gravadas, aulas ao vivo, agentes prontos, skills e comandos pra você usar no seu coding assistant hoje mesmo. Crie sua conta gratuita! 🔗 https://epic.new 📱 ME SIGA NAS REDES: Instagram: https://www.instagram.com/dfolloni/ LinkedIn: https://www.linkedin.com/in/dfolloni/ Twitter/X: https://x.com/dfolloni 🗞️ ASSINE MINHA NEWSLETTER (DE GRAÇA) Substack: https://dfolloni.substack.com/ 💬 COMENTE AQUI EMBAIXO: Você ainda usa vibe coding nos seus projetos, ou já tá tentando estruturar melhor o seu processo? Me conta nos comentários! Leio todos e respondo sempre que posso 👇 🔔 Inscreva-se no canal e ative o sininho para não perder os próximos vídeos sobre desenvolvimento de software com IA! 🙏 Obrigada por assistir! Se este vídeo te ajudou, deixe seu LIKE 👍 e compartilhe com aquele amigo que vive reclamando que a IA não obedece. Te vejo no próximo vídeo! 🚀