BrightonSEO-Vibe-Coding - REMDigital

BrightonSEO

Thank you for attending my presentation. Below is a copy of the presentation and some in-depth notes, codes and links to all the resources mentioned.

Connect with me on Linkedin, Instagram

Links to Resources

Lovable: https://lovable.dev/
Bolt: https://bolt.new/
Replit: https://replit.com/
Claude Code: https://claude.com/claude-code
Cursor: https://cursor.com/
GitHub Copilot: https://github.com/features/copilot

How to Keep a Prompt Log

A prompt log is a simple spreadsheet that records every prompt you send an AI coding tool, so you can trace exactly what changed and when. Here’s how to set one up.

1. Create the Spreadsheet

Open Google Sheets, Excel, or Notion and create four columns:

2. Log Every Prompt Before You Move On

After each prompt, add a row before sending the next one:

3. Use It to Trace Problems

If something breaks later in the project, scan the “Worked?” column for the first “No” : that’s usually where the issue started, not wherever you happen to be looking now.

4. Use It to Rebuild if Needed

If the project breaks beyond repair, you can start a fresh project and replay your prompts in order from the log, skipping any rows marked “No.” With a prompt log in place, you always have a record of exactly what you asked for and exactly when things stopped working.

How to Fence Your Prompts

Fencing means telling the AI what to change and what to leave alone, so a small request doesn’t turn into a large, unintended rewrite.

1. Identify What You Actually Want Changed

Before prompting, name the one specific thing you want touched: a form, a button, a colour, a field.

2. Add the Fence

Add a second sentence to your prompt that names the areas to leave untouched:

Unfenced:
"Add a date picker to the booking form."

Fenced:
"Add a date picker to the booking form. Do not change the header, 
footer, navigation, or existing form fields."

3. Check the Result Against the Fence

After the AI responds, check the exact areas you fenced off first: header, footer, navigation, other fields : before checking the feature you asked for. This catches unintended changes fast.

4. Reuse Standard Fences

If you’re working on the same project for a while, keep a short list of “always fence these” areas (e.g. navigation, login, payment flow) and paste them into every prompt that touches unrelated parts of the site. With fenced prompts, the AI still makes the change you asked for: just without the collateral damage. Let me know if you need any specific adjustments!

REMDigital