Aaron

Welcome to Aaron's Vibe Coding Space

Building awesome things for the botgui.de team

About

This is Aaron's dedicated workspace for vibe coding and contributing to the botgui.de team projects.

Onboarding & Getting Started

Timeline & When to Start

Q: "In an ideal situation, what is your timeline to scale up? When would you like to have me (or someone else) start working with/for you?"

  • Discussions begin: January 2026
  • Contracts finalized: End of January 2026
  • Industry considerations: Construction slows down in winter, and people go on vacation. Timeline is flexible and will be clearer after contracts are signed.

Quick Start Recommendations

  • Start LLC in Idaho - Get your business entity set up
  • Open bank account for LLC - Separate business finances from personal

Preparation Phase

Learning & Experimentation: Spend as much time with AI as you can. This is where you'll build the foundation for our collaboration.

I can share ZTM and Coursera sign-in if you'd like to check out the courses. Experiment and find something of interest!

Learning Resources

Domain Knowledge

This is where you could be the most helpful!!

This will help with Corey Barton optimization

This will help with Engineering projects

Experimentation & Exploration

Compensation Structure - Phased Approach

Since I will be training you as a contractor, we'll use a phased scale approach. I'll know more after we get contracts signed. What would you like to make during each phase?

Phase 1 100/0

Not client-based projects: Training, solve small problems, run into issues and solve them. I may show you some client work, show you how I solve problems, and take you to client meetings.

Phase 2 75/25

Work on client projects together - You're learning while contributing

Phase 3 50/50

Work on client projects together - Equal partnership in delivery

Phase 4 75/25

Work on client projects together - You're taking the lead

Phase 5 100

You're able to do 100% of the project with 100% pay - Full independence

Getting Started Workflow

1

Feature Request & Planning

Create a feature request document in a feature folder: .dev/work/[date]_[feature]/

Example: .dev/work/25_11_03_1st_getting started/

Ask AI: "Please review `.dev/work/[date]_[feature]/` and create a plan"

AI will review documents in that folder and create a plan in the same folder

2

Review & Approve

Review the AI's proposal, provide feedback, and approve when ready

Approve or request revisions until all requirements are clear

3

Implementation

AI will implement the approved plan

AI creates/updates files (frontend, backend, database scripts)

Code ready for testing

4

Testing & Bug Reporting

Test the feature and report any issues

Report bugs using one of these formats:

  • Dev Tools Errors: Copy/paste console errors, network errors, or stack traces
  • Click Path: Describe the action taken, expected behavior, and actual behavior

AI analyzes and fixes the issues

5

Build Process

After frontend changes (JSX/React in app.jsx)

AI runs: npm run build:js

Generates app.min.js for production

6

Deployment

Upload files to production via FTP

Upload app.min.js (frontend) or PHP files (backend)

For database changes: Execute SQL scripts if needed

7

Production Testing

Test the feature in production environment

Verify all functionality works as expected

If issues found, return to Step 4 (Testing & Bug Reporting)

Quick Reference

Feature Folders: .dev/work/[date]_[feature]/
Plans & Evidence: .dev/evidence/[YYYY_MM_DD]_[feature]/
Build Command: npm run build:js
Test Files: api/test_*.php

Common Requests

  • "Create a PHP file to complete all tests" - AI creates comprehensive test suite
  • "Write a PHP file to push SQL" - AI creates SQL execution script
  • "Test Summary: X passed, Y failed" - Share test results for review
  • "Build when necessary" - AI rebuilds after frontend changes