Skip to content

Commit cb5f1f2

Browse files
committed
Checkpoint
1 parent 7459d47 commit cb5f1f2

File tree

2 files changed

+156
-57
lines changed

2 files changed

+156
-57
lines changed

src/content/blog/vibe-coding-guide/page.mdx

Lines changed: 19 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ import vibeCodingPremium from '@/images/vibe-coding-premium.webp'
1515
import secretsHero from '@/images/vibe-coding-survival-guide.webp'
1616
import gitSafetyNet from '@/images/git-safety-net.webp'
1717
import gettingGot from '@/images/getting-got.webp'
18+
import introToGit from '@/images/intro-to-git.webp'
1819
import secretsFlow from '@/images/secrets-flow.webp'
1920
import secretsGuard from '@/images/secret-guard.webp'
2021
import secretsLeak from '@/images/secrets-leak.webp'
@@ -73,8 +74,8 @@ Building with AI feels like you've hacked the system... until you:
7374
- Realize your "private" repo was public all along
7475

7576
**This happens because:**
76-
Cursor, Windsurf and Claude Code are still tools designed for professional developers, which assumes you know things like:
77-
- Where secrets actually live in production
77+
Cursor, Windsurf and Claude Code are still tools designed for professional developers, which assume you know things like:
78+
- How to safely manage secrets in production (and that you SHOULD be using DIFFERENT secrets for local development and production!)
7879
- How Git history really works
7980
- That API keys = credit cards
8081

@@ -148,16 +149,20 @@ git reset --hard HEAD~1
148149
2. Panic? No! Run `git reset --hard HEAD~1` to revert to your last save.
149150
3. Try again on a new branch: `git checkout -b retry-feature`.
150151

151-
<div className="not-prose my-4 p-4 rounded-md border border-yellow-400 bg-yellow-50 text-yellow-800 dark:border-yellow-600/30 dark:bg-yellow-900/20 dark:text-yellow-200">
152-
<strong className="font-semibold">🔒 Premium Only:</strong> Get pre-commit hooks and AI-powered rules that nudge Cursor to offer branches or checkpoints.
153-
<Image src={secretsGuard} alt="The premium version of this guide protects your secrets" />
154-
</div>
152+
<Link href="/products/vibe-coding-mastery">
153+
<div className="not-prose my-4 p-4 rounded-md border border-yellow-400 bg-yellow-50 text-yellow-800 dark:border-yellow-600/30 dark:bg-yellow-900/20 dark:text-yellow-200 cursor-pointer">
154+
<strong className="font-semibold">🔒 Premium Only:</strong> Get zero-bullshit, highly-visual and easy-to-understand explanations. Only what you need to know so you can get back to building.
155+
<Image src={introToGit} alt="The premium version of this guide explains git and secrets in a visual-first manner" />
156+
</div>
157+
</Link>
155158

156159
---
157160

158161
## 3. Secrets & Environment Variables — Baby Steps 🍼
159162

160-
<Image src={secretsFlow} alt="How secrets flow" />
163+
<Link href="/products/vibe-coding-mastery">
164+
<Image src={secretsFlow} alt="How secrets flow" />
165+
</Link>
161166

162167
**Secret** = Your code's credit card number. Leak it, pay for it.
163168
**Branch** = A sandbox for experiments. No branch? Bugs go live.
@@ -174,26 +179,12 @@ Quick checklist:
174179
### 💡 Try This (Free):
175180
Run `git add . && git commit -m "test"` to save your code.
176181

177-
**Premium Bonus:** Watch the screencast and get the exact commands to set up a tool that makes it impossible to leak your secrets via git!**
178-
179-
---
180-
181-
## Set Up GitGuardian for Automatic Secret Scanning
182-
183-
To make sure you never accidentally commit secrets to any of your projects, you can install a global pre-commit hook with GitGuardian. This is a one-time setup that protects every repo on your machine.
184-
185-
**What does this mean?**
186-
- A "pre-commit hook" is a tiny program that runs every time you try to make a Git commit.
187-
- With GitGuardian, this hook will automatically scan your code for secrets (like API keys) before the commit goes through.
188-
- If it finds something dangerous, it will block the commit and show you exactly what needs fixing—before anything leaks!
189-
190-
**To install the global pre-commit hook, run:**
191-
192-
```bash
193-
ggshield install -m global
194-
```
195-
196-
*This is a powerful safety net: it works for every project on your computer, not just one folder.*
182+
<Link href="/products/vibe-coding-mastery">
183+
<div className="not-prose my-4 p-4 rounded-md border border-yellow-400 bg-yellow-50 text-yellow-800 dark:border-yellow-600/30 dark:bg-yellow-900/20 dark:text-yellow-200 cursor-pointer">
184+
<strong className="font-semibold">🔒 Premium Only:</strong> Watch the screencast and get the exact commands to set up a tool that makes it impossible to leak your secrets via git!
185+
<Image src={secretsGuard} alt="The premium version of this guide protects your secrets" />
186+
</div>
187+
</Link>
197188

198189
---
199190

@@ -210,6 +201,4 @@ ggshield install -m global
210201
<Link href="/products/vibe-coding-mastery">
211202

212203
</Link>
213-
*Premium unlocks screencasts, exact commands, tools that auto-block leaks before they happen, and custom Cursor Rules to help you learn and protect you as you vibe code.*
214-
215-
[Join Waitlist for Early Access](/contact)
204+
*Premium unlocks screencasts, exact commands, tools that auto-block leaks before they happen, and custom Cursor Rules to help you learn and protect you as you vibe code.*

src/content/blog/vibe-coding-mastery/page.mdx

Lines changed: 137 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -21,43 +21,143 @@ import cursorRules from '@/images/cursor-rules.webp'
2121
import { createMetadata } from '@/utils/createMetadata';
2222
import { importContentMetadata } from '@/lib/content-handlers'
2323

24+
Perfect — thanks for the schema. Here’s the corrected version of the metadata object using the contentSections array with properly structured title and subsections, accurately reflecting your guide’s TOC and flow:
25+
2426
export const metadata = createMetadata({
25-
author: "Zachary Proser",
26-
date: "2025-04-28",
27-
title: "Vibe Coding Survival Guide",
28-
description: "A simple guide to safe coding with AI tools: master Git basics, protect secrets with GitGuardian, and use Cursor rules effectively.",
29-
image: vibeCodingPremium,
30-
commerce: {
31-
isPaid: true,
32-
price: 49,
33-
previewLength: 450,
34-
previewElements: 32,
35-
paywallHeader: "Vibe Coding Survival Guide",
36-
paywallBody: "Get the essential guide to safe coding with AI tools: master Git, protect secrets with GitGuardian, and use Cursor rules.",
37-
buttonText: "Get the Survival Guide ($49)",
38-
miniPaywallTitle: "Master safe development with AI tools",
39-
miniPaywallDescription: "Includes Git basics, GitGuardian setup, and Cursor rules.",
40-
paywallImage: vibeCodingPremium,
41-
paywallImageAlt: "Vibe Coding Survival Guide cover",
42-
profileImage: gettingGot
43-
},
27+
author: "Zachary Proser",
28+
date: "2025-05-04",
29+
title: "Vibe Coding Survival Guide",
30+
slug: "vibe-coding-survival-guide",
31+
type: "blog",
32+
description:
33+
"Tired of worrying about API key leaks or Git disasters? This step-by-step survival guide helps you prevent costly mistakes using GitGuardian, AI-powered Cursor rules, and proven workflows used by 1500+ developers.",
34+
image: vibeCodingPremium,
35+
tags: ["Git", "AI coding", "GitGuardian", "Secrets", "Cursor IDE"],
36+
commerce: {
37+
isPaid: true,
38+
price: 49,
39+
previewLength: 450,
40+
previewElements: 32,
41+
paywallHeader: "Vibe Coding Survival Guide",
42+
paywallBody:
43+
"Get the battle-tested system to stop secret leaks, fix Git mistakes, and protect your codebase. Used by 1500+ developers to avoid $2.8M+ in breach costs.",
44+
buttonText: "Get the Survival Guide ($97)",
45+
miniPaywallTitle: "Master safe development with AI tools",
46+
miniPaywallDescription:
47+
"Includes GitGuardian integration, AI-powered Cursor rules, recovery checklists, and premium screencasts.",
48+
paywallImage: vibeCodingPremium,
49+
paywallImageAlt: "Vibe Coding Survival Guide cover",
50+
profileImage: gettingGot,
51+
bonus: "Limited time: Includes $300 GitGuardian credits"
52+
},
53+
landing: {
54+
heroTitle: "🚨 Your Code's Credit Card Just Got Stolen (You Just Don't Know It Yet)",
55+
subtitle:
56+
"Based on years of real-world incidents and my own GitGuardian playbook — now tailored for the AI coding era.",
57+
problemSolved:
58+
"Prevent costly API key leaks, avoid Git disasters, and secure your codebase with professional workflows – even if you're new to AI-powered development.",
59+
benefitStatement:
60+
"Ship code confidently knowing your secrets are safe, your Git history is clean, and your deployments are bulletproof.",
61+
features: [
62+
{
63+
title: "🔒 Secret Leak Forcefield",
64+
description:
65+
"GitGuardian integration + pre-commit hooks that block API key leaks before they reach GitHub",
66+
icon: "shield"
67+
},
68+
{
69+
title: "🤖 AI-Powered Git Mentorship",
70+
description:
71+
"Cursor rules that give real-time guidance like 'Never commit .env files!' as you code",
72+
icon: "robot"
73+
},
74+
{
75+
title: "🚑 Emergency Recovery Checklists",
76+
description:
77+
"Step-by-step guides to scrub leaked keys from Git history (tested on 12 incident responses)",
78+
icon: "emergency"
79+
},
80+
{
81+
title: "⚡ Deployment Safeguards",
82+
description:
83+
"CI/CD templates that auto-scan for secrets + Vercel/Netlify configs",
84+
icon: "deploy"
85+
},
86+
{
87+
title: "🎥 Exclusive Screencasts",
88+
description:
89+
"Watch me fix a live secret leak in 4 minutes flat (includes botched merge recovery)",
90+
icon: "video"
91+
}
92+
],
93+
contentSections: [
94+
{
95+
title: "How to Use This Guide"
96+
},
97+
{
98+
title: "Git: Your Software Save System",
99+
subsections: [
100+
"Commits",
101+
"Branches",
102+
"Sharing",
103+
"Viewing History & Time Travel",
104+
"Typical Git Flow",
105+
"Your First Safe Commit & Push",
106+
"Set Up Your Remote on GitHub"
107+
]
108+
},
109+
{
110+
title: "Secret Protection",
111+
subsections: [
112+
"What is a Secret? (And What Isn't)",
113+
"Install Homebrew (macOS Only)",
114+
"Install GitGuardian",
115+
"How it Works",
116+
"Test the Protection"
117+
]
118+
},
119+
{
120+
title: "Setting Up Cursor Rules for Safety and Mentorship"
121+
},
122+
{
123+
title: "Deployment Checklist (Simplified)"
124+
},
125+
{
126+
title: "Emergency Recovery (If a Secret Leaks)"
127+
},
128+
{
129+
title: "Help and Support"
130+
}
131+
],
132+
faqs: [
133+
{
134+
question: "I already know Git basics – why should I care?",
135+
answer:
136+
"This isn't Git 101. You'll get pro workflows for secret rotation, branch strategies, and incident response that even senior devs overlook."
137+
},
138+
{
139+
question: "What if I leak a key after buying?",
140+
answer:
141+
"The emergency recovery section walks you through scrubbing it from history + contains email templates for AWS/OpenAI revocation."
142+
},
143+
{
144+
question: "How is this different from free Git tutorials?",
145+
answer:
146+
"Battle-tested systems from 13 years in the field + exclusive tools you can’t Google (GitGuardian configs, Cursor rules)"
147+
}
148+
]
149+
}
44150
});
45151

152+
Ready to drop in. Let me know if you’d like to add videoGallery or resourceLinks metadata fields next.
153+
46154
<Image
47155
src={vibeCodingPremium}
48156
alt="Vibe coding survival guide hero"
49157
/>
50158

51159
## Table of Contents
52160

53-
1. [How to Use This Guide](#how-to-use-this-guide)
54-
2. [⎇ Git: Your software save system](#-git-your-software-save-system)
55-
3. [🔑 Secret Protection](#-secret-protection)
56-
4. [Setting Up Cursor Rules for Safety and Mentorship](#setting-up-cursor-rules-for-safety-and-mentorship)
57-
5. [🚀 Deployment Checklist (Simplified)](#-deployment-checklist-simplified)
58-
6. [🆘 Emergency Recovery (If a Secret Leaks)](#-emergency-recovery-if-a-secret-leaks)
59-
7. [Help and support](#help-and-support)
60-
61161
---
62162

63163
## How to Use This Guide
@@ -250,6 +350,16 @@ Below is a quick video walkthrough of the Homebrew installation process:
250350
Your browser does not support the video tag.
251351
</video>
252352

353+
**Next, install GitGuardian globally so it can protect all your projects by default:**
354+
355+
> This step sets up GitGuardian's pre-commit protection for every repository on your machine, not just the current one. It's the recommended way to ensure you never accidentally leak secrets, even in new or cloned projects.
356+
357+
```bash
358+
ggshield install -m global
359+
```
360+
361+
*You'll see a confirmation message that GitGuardian's pre-commit hook is now active globally. From now on, every time you try to commit, your code will be scanned for secrets before anything leaves your computer.*
362+
253363
### Install GitGuardian
254364
<Image src={gitGuardian} alt="Git Guardian runs before your commit is even made" />
255365

0 commit comments

Comments
 (0)