Learning path map
Detailed content
🖥️ Vibe Coding: Live Frontend Fixes
The agent stops guessing at code. It opens the visible browser, injects the change live, shows it on screen, and only writes it to the source code after your approval—always on a safe sandbox branch.
Reverse the agent’s classic workflow: instead of editing files and hoping for the best, it opens the browser, inspects, and tests the change live first.
Ends the "edit → build → check → revert" cycle. Every fix is visually validated before touching the code.
This is how a real developer works: DevTools open, visual adjustment, then permanent code.
A hard stop right at the start: the agent detects the active directory and asks whether it’s the right repository before any git, browser, or editing action.
Avoids the nightmare of changing the wrong project. A cheap step that prevents costly damage.
Detect the workspace, show the path, and wait for explicit confirmation. No directory guesswork.
Before analyzing or opening the browser, the agent creates a local branch and switches to it vibe/descricao — a safe testing area.
You experiment without fear: the main is never touched, and each fix stays isolated in its own branch.
Verify git status, offer to back up uncommitted work, create the branch BEFORE any work.
An automated browser, NOT headless, opens the target URL on your screen. The agent inspects the DOM and injects CSS/JS directly into the live page.
You watch the automation happen live as the agent tests fixes without editing a single project file.
Local dev server OR hosted URL, DOM inspection, screenshots, session recovery if the page reloads.
Four required approval gates: visual approval, strategy approval, code review, and push approval.
The agent literally can’t skip steps. You give the “go ahead” at every critical point—your code, your rules.
Anti-merge and anti-steamroll rule: strategy and execution NEVER in the same response. Each step gets its own approval.
Translate the browser’s temporary adjustment into clean, permanent source code—only after the strategy is approved—and close the session.
Only the final, polished fix becomes code. The git history stays clean, without a dozen failed attempts.
"Persist in the source" (not "hardcode"), clean up hacks, push to a dedicated branch, start a new session for the next fix.
🧲 Funnel Builder: one prompt, entire funnel
A suite of coordinated skills with a central orchestrator that takes your offer and produces a complete funnel ready to publish — pages, emails, scripts, and the digital lead magnet itself — in a single session.
A set of specialist skills (landing page, email, VSL, lead magnet, quiz...) with a central orchestrator that decides who steps in and when.
The bottleneck was never strategy—it was execution. A coordinated suite produces everything consistently in a single session.
Orchestrator + specialists, asset map, build order determined by dependencies.
Lead magnet, opt-in, webinar, VSL, launch, low/high-ticket, challenge, quiz, flash sale, re-engagement, and SaaS/trial — each with its own asset map.
Naming the funnel type lets the suite automatically choose which pages come first and which emails depend on what.
For each type, it knows the exact order: which scripts to write before the sequence, which pages before the emails.
Pages with complete copy, email sequences, the lead magnet as an actual file (downloadable PDF), social packs, headline variants, and the entire project folder.
It’s not an outline: it’s the actual file, ready to drop into Kajabi, ClickFunnels, Webflow, or plain HTML.
One subfolder per asset type, everything named and saved as you go, confirming each piece.
A kickoff ritual: start a new session, state the offer in one sentence, paste existing assets, specify the platform, type, and funnel goal.
Doing this produces dramatically better results. A fresh session isolates the project, and nothing leaks from previous work.
A clear offer ("a $27 mini-course for freelancers...") > vague ("a course about pricing").
After intake, the suite shows the complete asset map — every deliverable, in order. One approval triggers the entire build.
It doesn’t pause to ask permission for each piece: approve the plan and let it finish, saving and confirming each asset.
Review the plan, say "build it," and let it finish. Everything ends up organized in a single folder.
A real-world case: a short webinar brief generates a 75-minute script, registration page, confirmation, email sequences, replay page, and social pack.
Seeing the entire funnel take shape from one sentence shows what coordination between skills actually delivers.
Brief → plan → script → pages → emails (reminder, attended, no-show) → replay → social. All in one folder.