File size: 42,233 Bytes
8c90f57 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 |
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Complete Guide to Vibe Coding</title>
<script src="https://cdn.tailwindcss.com"></script>
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css">
<style>
.prose {
max-width: 800px;
margin: 0 auto;
}
.prose h2 {
margin-top: 2rem;
margin-bottom: 1rem;
font-weight: 700;
font-size: 1.5rem;
color: #1e40af;
}
.prose h3 {
margin-top: 1.5rem;
margin-bottom: 0.75rem;
font-weight: 600;
font-size: 1.25rem;
color: #1e40af;
}
.prose p {
margin-bottom: 1rem;
line-height: 1.6;
}
.prose ul {
margin-bottom: 1rem;
padding-left: 1.5rem;
list-style-type: disc;
}
.prose li {
margin-bottom: 0.5rem;
}
.prose code {
background-color: #f3f4f6;
padding: 0.2rem 0.4rem;
border-radius: 0.25rem;
font-family: monospace;
}
.prose pre {
background-color: #f3f4f6;
padding: 1rem;
border-radius: 0.5rem;
overflow-x: auto;
margin-bottom: 1.5rem;
}
html {
scroll-behavior: smooth;
}
/* Floating Navigation */
.floating-nav {
position: fixed;
bottom: 2rem;
left: 50%;
transform: translateX(-50%);
background: rgba(255, 255, 255, 0.9);
backdrop-filter: blur(10px);
border-radius: 50px;
padding: 0.5rem;
box-shadow: 0 10px 25px rgba(0, 0, 0, 0.1);
z-index: 100;
display: flex;
align-items: center;
transition: all 0.3s ease;
}
.nav-item {
padding: 0.75rem 1.25rem;
margin: 0 0.25rem;
border-radius: 30px;
font-weight: 500;
color: #4b5563;
cursor: pointer;
transition: all 0.3s ease;
white-space: nowrap;
position: relative;
}
.nav-item:hover {
background: #e5e7eb;
color: #1e40af;
}
.nav-item.active {
background: #3b82f6;
color: white;
}
.nav-item .number {
display: inline-block;
width: 24px;
height: 24px;
background: #e5e7eb;
border-radius: 50%;
text-align: center;
line-height: 24px;
margin-right: 8px;
font-size: 0.8rem;
}
.nav-item.active .number {
background: rgba(255, 255, 255, 0.3);
}
.nav-expand-btn {
width: 40px;
height: 40px;
border-radius: 50%;
background: #3b82f6;
color: white;
display: flex;
align-items: center;
justify-content: center;
cursor: pointer;
margin-left: 0.5rem;
transition: all 0.3s ease;
}
.nav-expand-btn:hover {
transform: rotate(90deg);
}
.progress-container {
position: fixed;
top: 0;
left: 0;
width: 100%;
height: 4px;
background: #e5e7eb;
z-index: 100;
}
.progress-bar {
height: 100%;
background: #3b82f6;
width: 0%;
transition: width 0.1s ease;
}
.quick-nav-btn {
position: fixed;
right: 2rem;
bottom: 2rem;
width: 56px;
height: 56px;
border-radius: 50%;
background: #3b82f6;
color: white;
display: flex;
align-items: center;
justify-content: center;
cursor: pointer;
box-shadow: 0 4px 15px rgba(59, 130, 246, 0.4);
z-index: 90;
transition: all 0.3s ease;
}
.quick-nav-btn:hover {
transform: scale(1.1);
box-shadow: 0 6px 20px rgba(59, 130, 246, 0.6);
}
.quick-nav-menu {
position: fixed;
right: 2rem;
bottom: 8rem;
background: white;
border-radius: 12px;
box-shadow: 0 10px 25px rgba(0, 0, 0, 0.1);
padding: 1rem 0;
width: 250px;
z-index: 95;
opacity: 0;
transform: translateY(20px);
visibility: hidden;
transition: all 0.3s ease;
}
.quick-nav-menu.active {
opacity: 1;
transform: translateY(0);
visibility: visible;
}
.quick-nav-item {
padding: 0.75rem 1.5rem;
cursor: pointer;
transition: all 0.2s ease;
display: flex;
align-items: center;
}
.quick-nav-item:hover {
background: #f3f4f6;
color: #1e40af;
}
.quick-nav-item i {
margin-right: 12px;
width: 20px;
text-align: center;
}
.section-indicator {
position: fixed;
left: 2rem;
top: 50%;
transform: translateY(-50%);
display: flex;
flex-direction: column;
align-items: center;
z-index: 90;
}
.indicator-dot {
width: 12px;
height: 12px;
border-radius: 50%;
background: #e5e7eb;
margin: 0.5rem 0;
cursor: pointer;
transition: all 0.3s ease;
position: relative;
}
.indicator-dot.active {
background: #3b82f6;
transform: scale(1.3);
}
.indicator-dot::after {
content: attr(data-title);
position: absolute;
left: 20px;
top: 50%;
transform: translateY(-50%);
background: white;
padding: 0.25rem 0.75rem;
border-radius: 4px;
box-shadow: 0 2px 8px rgba(0, 0, 0, 0.1);
font-size: 0.8rem;
white-space: nowrap;
opacity: 0;
pointer-events: none;
transition: all 0.3s ease;
}
.indicator-dot:hover::after {
opacity: 1;
left: 25px;
}
@media (max-width: 1024px) {
.floating-nav {
width: 90%;
overflow-x: auto;
padding: 0.5rem;
white-space: nowrap;
-webkit-overflow-scrolling: touch;
}
.floating-nav::-webkit-scrollbar {
display: none;
}
.section-indicator {
display: none;
}
}
@media (max-width: 768px) {
.floating-nav {
bottom: 1rem;
width: calc(100% - 2rem);
}
.nav-item {
padding: 0.5rem 0.75rem;
font-size: 0.9rem;
}
.nav-item .number {
display: none;
}
.quick-nav-btn {
right: 1rem;
bottom: 1rem;
width: 48px;
height: 48px;
}
.quick-nav-menu {
right: 1rem;
bottom: 6rem;
width: 200px;
}
}
</style>
</head>
<body class="bg-gray-50">
<!-- Progress Bar -->
<div class="progress-container">
<div class="progress-bar" id="progressBar"></div>
</div>
<!-- Floating Navigation -->
<div class="floating-nav" id="floatingNav">
<div class="nav-item" data-section="introduction">
<span class="number">0</span> Intro
</div>
<div class="nav-item" data-section="choosing-tool">
<span class="number">1</span> Tools
</div>
<div class="nav-item" data-section="windsurf-features">
<span class="number">2</span> Features
</div>
<div class="nav-item" data-section="language-stack">
<span class="number">3</span> Stack
</div>
<div class="nav-item" data-section="planning">
<span class="number">4</span> Planning
</div>
<div class="nav-item" data-section="version-control">
<span class="number">5</span> Version Control
</div>
<div class="nav-item" data-section="ai-rules">
<span class="number">6</span> AI Rules
</div>
<div class="nav-item" data-section="workflow">
<span class="number">7</span> Workflow
</div>
<div class="nav-item" data-section="tips">
<span class="number">8</span> Tips
</div>
<div class="nav-item" data-section="conclusion">
<span class="number">9</span> Conclusion
</div>
<div class="nav-expand-btn" id="navExpandBtn">
<i class="fas fa-ellipsis-h"></i>
</div>
</div>
<!-- Quick Navigation Button -->
<div class="quick-nav-btn" id="quickNavBtn">
<i class="fas fa-bars"></i>
</div>
<!-- Quick Navigation Menu -->
<div class="quick-nav-menu" id="quickNavMenu">
<div class="quick-nav-item" data-section="introduction">
<i class="fas fa-home"></i> Introduction
</div>
<div class="quick-nav-item" data-section="choosing-tool">
<i class="fas fa-tools"></i> Choosing Tools
</div>
<div class="quick-nav-item" data-section="windsurf-features">
<i class="fas fa-star"></i> Windsurf Features
</div>
<div class="quick-nav-item" data-section="language-stack">
<i class="fas fa-layer-group"></i> Language Stack
</div>
<div class="quick-nav-item" data-section="planning">
<i class="fas fa-tasks"></i> Planning
</div>
<div class="quick-nav-item" data-section="version-control">
<i class="fas fa-code-branch"></i> Version Control
</div>
<div class="quick-nav-item" data-section="ai-rules">
<i class="fas fa-robot"></i> AI Rules
</div>
<div class="quick-nav-item" data-section="workflow">
<i class="fas fa-sync-alt"></i> Workflow
</div>
<div class="quick-nav-item" data-section="tips">
<i class="fas fa-lightbulb"></i> Tips
</div>
<div class="quick-nav-item" data-section="conclusion">
<i class="fas fa-flag-checkered"></i> Conclusion
</div>
</div>
<!-- Section Indicator Dots -->
<div class="section-indicator">
<div class="indicator-dot active" data-section="introduction" data-title="Introduction"></div>
<div class="indicator-dot" data-section="choosing-tool" data-title="Choosing Tools"></div>
<div class="indicator-dot" data-section="windsurf-features" data-title="Windsurf Features"></div>
<div class="indicator-dot" data-section="language-stack" data-title="Language Stack"></div>
<div class="indicator-dot" data-section="planning" data-title="Planning"></div>
<div class="indicator-dot" data-section="version-control" data-title="Version Control"></div>
<div class="indicator-dot" data-section="ai-rules" data-title="AI Rules"></div>
<div class="indicator-dot" data-section="workflow" data-title="Workflow"></div>
<div class="indicator-dot" data-section="tips" data-title="Tips"></div>
<div class="indicator-dot" data-section="conclusion" data-title="Conclusion"></div>
</div>
<!-- Main Content -->
<div class="container mx-auto px-4 py-20">
<div class="prose">
<section id="introduction">
<h1 class="text-3xl font-bold mb-6 text-blue-800">The Complete Guide to Vibe Coding</h1>
<p class="text-lg mb-6">This guide walks you through the essentials of Vibe Coding, a method leveraging AI to assist in software development, as explained in Matthew Berman's video tutorial.</p>
<div class="bg-blue-100 p-4 rounded-lg mb-6">
<p class="font-semibold">Use the navigation at the bottom or the quick menu to jump between sections.</p>
</div>
</section>
<section id="choosing-tool" class="pt-16 -mt-16">
<h2>1. Choosing Your Vibe Coding Tool</h2>
<p>The first step is selecting the right tool. Here are the options discussed:</p>
<h3>Windsurf & Cursor:</h3>
<ul>
<li>Code editors, with Windsurf being a fork of the popular VS Code.</li>
<li>The speaker primarily uses Windsurf.</li>
<li>Natural transition for existing VS Code users.</li>
<li>Considered "agentic," meaning they iterate on code more effectively than simple AI chat interfaces for coding tasks.</li>
</ul>
<h3>Cline (VS Code Extension):</h3>
<ul>
<li>An extension for VS Code itself.</li>
<li>Good if you prefer sticking with your existing VS Code setup.</li>
<li>The speaker has heard good things but hasn't tested it extensively.</li>
</ul>
<h3>Replit:</h3>
<ul>
<li>A completely online code editor.</li>
<li>Advantage: Easy deployment since everything is cloud-based.</li>
</ul>
<h3>AI Canvas Features (Claude, ChatGPT, Google):</h3>
<ul>
<li>Easiest way to get started.</li>
<li>Allows writing and executing code (primarily HTML/JavaScript) directly in the browser without installing anything.</li>
<li>Example: Generating and running a three.js animation in Claude's canvas.</li>
<li>Limitations: Mainly restricted to HTML/JS; less "agentic" - they generate code but don't iterate on it like dedicated tools.</li>
</ul>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>For simple browser-based tasks, AI canvases work. For more complex projects requiring iteration and more control, dedicated tools like Windsurf or Cursor are preferred.</p>
</div>
</section>
<section id="windsurf-features" class="pt-16 -mt-16">
<h2>2. Deep Dive: Windsurf Features</h2>
<p>The speaker highlights several features of Windsurf:</p>
<h3>Model Switching:</h3>
<p>Easily switch between different AI models (Claude variants, GPT-4o, DeepSeek) to use the best one for the current task.</p>
<h3>Tab Completion Enhancements:</h3>
<p>Advanced tab completion with context from your codebase, terminal, and Cascade (Windsurf's AI interaction panel). Includes features like "tab to jump" and "tab to import".</p>
<h3>Browser Preview:</h3>
<p>Automatically offers an embedded browser preview of your web project as you build it. Allows clicking elements in the preview to give targeted feedback to the AI (@dom-element).</p>
<h3>Contextual Knowledge:</h3>
<p>Paste URLs (e.g., library/API documentation) into Cascade to give the AI extra context for writing code.</p>
</section>
<section id="language-stack" class="pt-16 -mt-16">
<h2>3. Choosing Your Language & Stack</h2>
<p>Selecting the right programming language and technology stack is crucial:</p>
<h3>The Rule: Choose Popularity</h3>
<p>Opt for popular languages because the AI will have been trained on more examples, leading to potentially better code generation.</p>
<h3>Top Choices:</h3>
<ul>
<li><strong>JavaScript (JS):</strong> The world's most popular language. Great option.</li>
<li><strong>Python:</strong> De facto language for AI; the speaker likes it.</li>
</ul>
<h3>Recommended Stack (Speaker's Preference):</h3>
<ul>
<li><strong>Backend:</strong> Python</li>
<li><strong>Frontend:</strong> HTML & JavaScript</li>
<li>Alternative: JavaScript backend (Node.js) is also viable.</li>
</ul>
<h3>Finding Popular Languages:</h3>
<p>Use resources like GitHut 2.0 to see language popularity rankings (Python, Java, Go, JS, C++, TypeScript mentioned).</p>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>Stick to popular languages like JavaScript or Python. The speaker prefers Python (backend) + JS/HTML (frontend).</p>
</div>
</section>
<section id="planning" class="pt-16 -mt-16">
<h2>4. Planning Your Project: The Crucial Step</h2>
<p>Thorough planning is essential for success:</p>
<h3>Invest Time Here:</h3>
<p>Create a detailed, thorough plan before coding. Think through features, edge cases, and desired behavior. This prevents problems later, as future changes are harder.</p>
<h3>Use AI for Planning:</h3>
<ul>
<li>Tools like Grok can help brainstorm features and identify gaps.</li>
<li>Prompt AI to ask clarifying questions.</li>
<li>Iterate with the AI until the plan is solid.</li>
</ul>
<h3>Format as PRD (Product Requirements Document):</h3>
<ul>
<li>Ask the AI to format the final plan as a PRD in Markdown (.md) format.</li>
<li>Copy this PRD into your project directory.</li>
</ul>
<h3>Create a To-Do List:</h3>
<ul>
<li>Ask the AI to generate a step-by-step to-do list for building the project, also in Markdown.</li>
<li>Refine the list as needed (e.g., remove ETAs).</li>
</ul>
<h3>Living Documents:</h3>
<p>Your plan and to-do list aren't static. Update them as you realize changes are needed (adding/removing features, changing behavior). The AI can reference these updated documents.</p>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>Don't skimp on planning. Use AI to help create a detailed PRD and to-do list in Markdown, and keep them updated.</p>
</div>
</section>
<section id="version-control" class="pt-16 -mt-16">
<h2>5. Version Control: Your Safety Net</h2>
<p>Version control is non-negotiable for any coding project, especially vibe coding:</p>
<h3>What it is:</h3>
<p>A system to save snapshots (versions) of your code at different points in time.</p>
<h3>Why it's Critical:</h3>
<ul>
<li>Allows you to roll back to a previous working state if something breaks.</li>
<li>Essential because AI can sometimes make large, breaking changes.</li>
<li>Avoids frustrating loops of trying to fix broken AI-generated code; just revert and try again from a stable point.</li>
</ul>
<h3>Git: The Standard:</h3>
<ul>
<li>The most common version control software.</li>
<li>Allows saving points ("commits"), managing different lines of development ("branches"), and more.</li>
</ul>
<h3>Git Complexity & AI Assistance:</h3>
<ul>
<li>Git can be complex, but you don't need deep expertise for vibe coding.</li>
<li>Your AI agent can handle most Git commands for you (init, commit, etc.).</li>
<li>Learning basic terms (commit, revert, log) is helpful.</li>
</ul>
<h3>Setting up Git with AI:</h3>
<p>Simply ask your AI agent (e.g., in Windsurf's Cascade) to "install git" (it checks if already present) and then "add git to this project". The AI will run commands like git init, create a .gitignore file (to exclude files from version control), set up the main branch, and make the initial commit (first save point).</p>
<h3>GitHub: Cloud Backup:</h3>
<ul>
<li>Use GitHub (or similar services) to push your local Git repository to the cloud.</li>
<li>Provides secure offsite backup ("like Google Docs for code").</li>
<li>Free for basic use. Ask AI to help set up the connection.</li>
</ul>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>Use Git for version control. Let your AI assistant handle the commands. Use GitHub for cloud backup. Commit frequently!</p>
</div>
</section>
<section id="ai-rules" class="pt-16 -mt-16">
<h2>6. Guiding the AI with Rules</h2>
<p>Rules act like system prompts, ensuring the AI follows your desired coding style, structure, and workflow consistently.</p>
<h3>What are Rules?:</h3>
<p>Instructions included with every prompt sent to the AI, guiding its behavior. Supported by tools like Windsurf, Cursor, and Cline.</p>
<h3>Accessing Rules (Windsurf Example):</h3>
<ul>
<li>Go to Windsurf Settings -> Memories and Rules -> Manage.</li>
<li>Rules are stored alongside "Memories" (AI-generated notes about the project).</li>
</ul>
<h3>Types of Rules:</h3>
<ul>
<li><strong>Global Rules:</strong> Apply to all projects. Edited via "Edit global rules". Stored in global_rules.md.</li>
<li><strong>Workspace Rules:</strong> Apply only to the current project.</li>
</ul>
<h3>Example Global Rules (from speaker's gist)</h3>
<pre>
After making changes, ALWAYS make sure to start up a new server so I can test it.
Always look for existing code to iterate on instead of creating new code.
Do not drastically change the patterns before trying to iterate on existing patterns.
Always kill all existing related servers that may have been created in previous testing before trying to start a new server.
Always prefer simple solutions
Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality
Write code that takes into account the different environments: dev, test, and prod
You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested
When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we don't have duplicate logic.
Keep the codebase very clean and organized
Avoid writing scripts in files if possible, especially if the script is likely only to be run once
Avoid having files over 200-300 lines of code. Refactor at that point.
Mocking data is only needed for tests, never mock data for dev or prod
Never add stubbing or fake data patterns to code that affects the dev or prod environments
Never overwrite my .env file without first asking and confirming
Focus on the areas of code relevant to the task
Do not touch code that is unrelated to the task
Write thorough tests for all major functionality
Avoid making major changes to the patterns and architecture of how a feature works, after it has shown to work well, unless explicitly instructed
Always think about what other methods and areas of code might be affected by code changes</pre>
<h3>Language-Specific Rules:</h3>
<ul>
<li>Find pre-made rule sets for specific languages/frameworks.</li>
<li>Example Resource: awesome-cursorrules repository on GitHub.</li>
<li>Contains Markdown files (.cursorrules) with best practices for React, Python/FastAPI, etc.</li>
<li>You don't need to understand every rule initially; they generally represent good practices.</li>
</ul>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>Use rules (global and workspace/language-specific) to guide the AI's coding style and workflow. Start with the speaker's examples and explore resources like awesome-cursorrules.</p>
</div>
</section>
<section id="workflow" class="pt-16 -mt-16">
<h2>7. The Vibe Coding Workflow Cycle</h2>
<p>Follow this iterative process for building your project:</p>
<h3>Setup:</h3>
<p>Create prd.md and todo.md files in your project (can ask AI to do this by pasting content).</p>
<h3>The Workflow Loop:</h3>
<ol>
<li><strong>Reference Plan & Todo:</strong> Tell the AI to read the PRD and todo list.</li>
<li><strong>Build Next Feature:</strong> Instruct the AI to build one item/feature from the to-do list. (May involve initial framework setup first).</li>
<li><strong>Write Tests:</strong> Ask the AI to write tests for the newly added feature. Tests are separate code that verifies your main code works correctly.</li>
<li><strong>Run New Feature Tests:</strong> Run the tests specifically for the new feature.
<ul>
<li><strong>Pass:</strong> Proceed to next step.</li>
<li><strong>Fail:</strong> Fix the tests or the code causing the failure. Ask AI for help.</li>
</ul>
</li>
<li><strong>Run All Tests:</strong> Run the entire test suite for the whole project.
<ul>
<li><strong>Pass:</strong> Proceed to next step.</li>
<li><strong>Fail:</strong> Fix the tests that failed. This might involve:
<ul>
<li>Fixing the code that broke existing functionality.</li>
<li>Updating old tests if the functionality intentionally changed and the old tests are now incorrect.</li>
<li>Ask AI to explain failures and help decide how to fix.</li>
</ul>
</li>
</ul>
</li>
<li><strong>Commit Changes:</strong> Once all tests pass, save your progress using Git. Ask the AI: "commit the code". It will handle staging files and writing a commit message.</li>
<li><strong>Repeat:</strong> Go back to step 1 for the next item on the to-do list.</li>
</ol>
<h3>Handling Major Issues: Rollback:</h3>
<ul>
<li>If the AI irrecoverably breaks the code, don't waste time trying to fix it endlessly.</li>
<li>Ask the AI to "rollback to the previous commit". This discards recent broken changes and reverts to the last known good state (your last successful commit).</li>
<li>(Mentioned: git stash can temporarily save changes instead of discarding, but rollback is the primary recovery method discussed).</li>
</ul>
<div class="bg-yellow-100 p-4 rounded-lg mt-4">
<p class="font-semibold">Key Takeaway:</p>
<p>Follow a strict cycle: Build Feature -> Write Tests -> Run Tests (New & All) -> Fix -> Commit -> Repeat. Tests are crucial for stability. Use git commit often and git rollback when needed.</p>
</div>
</section>
<section id="tips" class="pt-16 -mt-16">
<h2>8. Miscellaneous Tips & Best Practices</h2>
<p>Final tips to improve your vibe coding experience:</p>
<h3>Chat vs. Write Mode:</h3>
<ul>
<li>Use Write mode when you want the AI to generate/modify code.</li>
<li>Use Chat mode to ask questions about the codebase or concepts without modifying code.</li>
</ul>
<h3>Model Selection:</h3>
<p>Choose the best model for the task (speaker finds Claude 3.5/3.7 Thinking best for coding).</p>
<h3>Frontend Appearance:</h3>
<ul>
<li>AI isn't great at creating beautiful UIs from scratch.</li>
<li>Find free/paid UI templates (e.g., Bootstrap themes) online.</li>
<li>Download the template, add it to your project, and tell the AI to use its components.</li>
</ul>
<h3>Targeting Code (@ Symbol):</h3>
<ul>
<li>Use the @ symbol in your prompts to reference specific files, directories, docs, or web links, giving the AI precise context for updates.</li>
<li>Requires some understanding of your codebase.</li>
</ul>
<h3>three.js for Games:</h3>
<ul>
<li>A popular 3D JavaScript library often used for vibe coding games.</li>
<li>Most AIs know how to use it. Just ask: "build me a game [description] using three.js".</li>
</ul>
<h3>Security Concerns:</h3>
<ul>
<li>Vibe-coded projects can be insecure or hard to maintain if you lack foundational knowledge.</li>
<li><strong>Learn Best Practices:</strong> Spend time learning security fundamentals. Ask AI to explain.</li>
<li><strong>Use Rules:</strong> Add security best practices as rules (e.g., "Rate limit all API endpoints", "Use row-level security", "Add Captcha").</li>
<li><strong>Find Checklists:</strong> Look for security checklists online (speaker shows examples from @jackfriks and @tedx_ai / Ted Werbel on X).</li>
<li><strong>API Keys:</strong> NEVER share API keys publicly (even in screenshots!). NEVER commit keys to Git (use .gitignore).</li>
<li><strong>Auditing:</strong> Use tools like npm run audit (for Node.js). Ask AI to perform a security audit of your code.</li>
<li><strong>Don't Roll Your Own Auth:</strong> Use established authentication services (e.g., Clerk).</li>
<li><strong>Infrastructure:</strong> Implement rate limiting, DDoS protection, firewalls, monitoring.</li>
<li><strong>Test Critical Areas:</strong> Write thorough tests for sensitive parts like payments, subscriptions, etc.</li>
</ul>
<h3>Maintainability:</h3>
<ul>
<li>AI code might not be "pretty" initially, but AI capabilities are improving.</li>
<li>It's okay if early projects are brittle; it's part of learning.</li>
<li><strong>Refactoring:</strong> Ask the AI to "refactor" the code (make it cleaner, more modular, remove duplication) based on best practices (which can also be added to rules).</li>
</ul>
<h3>MCP Servers (Advanced):</h3>
<ul>
<li>Model Control Protocol (MCP) allows giving AI agents additional tools/capabilities.</li>
<li>Configured in Windsurf (Configure MCP -> mcp_config.json). Ask AI for help writing the config.</li>
<li><strong>Examples:</strong>
<ul>
<li><strong>Unity MCP:</strong> Control the Unity game editor via chat.</li>
<li><strong>Firecrawl MCP:</strong> Enable deep web research capabilities for the agent.</li>
</ul>
</li>
<li>Explore once comfortable with basic vibe coding.</li>
</ul>
</section>
<section id="conclusion" class="pt-16 -mt-16">
<h2>9. Conclusion</h2>
<p>Vibe coding is presented as a fun, relaxing way to build things, whether you're an experienced programmer or just starting. It's a great way to get exposure to coding concepts and begin a learning journey. The technology will only improve.</p>
</section>
</div>
</div>
<script>
// Navigation functionality
document.addEventListener('DOMContentLoaded', function() {
// Get all navigation elements
const navItems = document.querySelectorAll('.nav-item');
const quickNavItems = document.querySelectorAll('.quick-nav-item');
const indicatorDots = document.querySelectorAll('.indicator-dot');
const quickNavBtn = document.getElementById('quickNavBtn');
const quickNavMenu = document.getElementById('quickNavMenu');
const navExpandBtn = document.getElementById('navExpandBtn');
const floatingNav = document.getElementById('floatingNav');
const progressBar = document.getElementById('progressBar');
// Track if quick nav is open
let isQuickNavOpen = false;
// Function to scroll to section
function scrollToSection(sectionId) {
const targetElement = document.getElementById(sectionId);
if (targetElement) {
const targetPosition = targetElement.getBoundingClientRect().top + window.pageYOffset - 100;
window.scrollTo({
top: targetPosition,
behavior: 'smooth'
});
// Update URL without jumping
history.pushState(null, null, `#${sectionId}`);
// Update active states
updateActiveStates(sectionId);
}
}
// Function to update all active states
function updateActiveStates(activeSection) {
// Update floating nav items
navItems.forEach(item => {
if (item.dataset.section === activeSection) {
item.classList.add('active');
} else {
item.classList.remove('active');
}
});
// Update quick nav items
quickNavItems.forEach(item => {
if (item.dataset.section === activeSection) {
item.classList.add('active');
} else {
item.classList.remove('active');
}
});
// Update indicator dots
indicatorDots.forEach(dot => {
if (dot.dataset.section === activeSection) {
dot.classList.add('active');
} else {
dot.classList.remove('active');
}
});
}
// Add click event to all nav items
navItems.forEach(item => {
item.addEventListener('click', function() {
scrollToSection(this.dataset.section);
});
});
// Add click event to quick nav items
quickNavItems.forEach(item => {
item.addEventListener('click', function() {
scrollToSection(this.dataset.section);
toggleQuickNav(); // Close the quick nav menu after selection
});
});
// Add click event to indicator dots
indicatorDots.forEach(dot => {
dot.addEventListener('click', function() {
scrollToSection(this.dataset.section);
});
});
// Toggle quick nav menu
function toggleQuickNav() {
isQuickNavOpen = !isQuickNavOpen;
quickNavMenu.classList.toggle('active', isQuickNavOpen);
quickNavBtn.innerHTML = isQuickNavOpen ? '<i class="fas fa-times"></i>' : '<i class="fas fa-bars"></i>';
}
quickNavBtn.addEventListener('click', toggleQuickNav);
// Expand floating nav
navExpandBtn.addEventListener('click', function() {
floatingNav.style.overflowX = 'auto';
floatingNav.style.whiteSpace = 'nowrap';
floatingNav.style.width = '90%';
floatingNav.style.left = '50%';
floatingNav.style.transform = 'translateX(-50%)';
// After a delay, return to normal
setTimeout(() => {
floatingNav.style.overflowX = 'hidden';
floatingNav.style.whiteSpace = 'normal';
floatingNav.style.width = '';
floatingNav.style.left = '';
floatingNav.style.transform = '';
}, 3000);
});
// Update progress bar on scroll
window.addEventListener('scroll', function() {
const scrollTop = document.documentElement.scrollTop || document.body.scrollTop;
const scrollHeight = document.documentElement.scrollHeight - document.documentElement.clientHeight;
const scrollPercentage = (scrollTop / scrollHeight) * 100;
progressBar.style.width = scrollPercentage + '%';
// Update active section based on scroll position
const sections = document.querySelectorAll('section');
let currentSection = '';
sections.forEach(section => {
const sectionTop = section.offsetTop;
const sectionHeight = section.clientHeight;
if (window.scrollY >= (sectionTop - 200)) {
currentSection = section.id;
}
});
if (currentSection) {
updateActiveStates(currentSection);
}
});
// Check for hash on load and scroll to section
if (window.location.hash) {
const sectionId = window.location.hash.substring(1);
scrollToSection(sectionId);
}
});
</script>
<p style="border-radius: 8px; text-align: center; font-size: 12px; color: #fff; margin-top: 16px;position: fixed; left: 8px; bottom: 8px; z-index: 10; background: rgba(0, 0, 0, 0.8); padding: 4px 8px;">Made with <img src="https://enzostvs-deepsite.hf.space/logo.svg" alt="DeepSite Logo" style="width: 16px; height: 16px; vertical-align: middle;display:inline-block;margin-right:3px;filter:brightness(0) invert(1);"><a href="https://enzostvs-deepsite.hf.space" style="color: #fff;text-decoration: underline;" target="_blank" >DeepSite</a> - 🧬 <a href="https://enzostvs-deepsite.hf.space?remix=dominiklukes/vibe-coding-study-guide" style="color: #fff;text-decoration: underline;" target="_blank" >Remix</a></p></body>
</html> |