The WolfAI Guide to Vibe Coding on TRN For Beginners
The WolfAI Guide to Vibe Coding on TRN For Beginners
*This guide will assume that you are going to use the tools I use*
Setup:
*Create fresh wallets in MetaMask and do everything on Test Net first*
*Just connect your fresh wallets to FP to get fresh FP addresses*
Download Visual Studio Code: https://code.visualstudio.com/download
Install VS Code
Open VS Code
Select “Extensions” from the left had side after opening VSC
Search RooCode and install it
Select the “RooCode” extension that shows up on the left hand side
Select settings and enter your API information. I use Google Gemini w/ the 2.5 Pro option
After hitting Save and Done, click the arrow next to Auto-Approve and select every box. These are my preferences, but you can choose not to do this if you want to approve every action
Select the Explorer option from the left hand side
Open your project directory folder
Download the TRNLLMBASE.zip from https://teearein.xyz
Extract these documents to the working directory of your project
Building:
Set clear guidelines for your LLM and the project
See examples below. This will save you so much time
Use these three prompts in order. The technical changelog is amazing for picking up where you left off if you have to start a new session with a fresh API task.
“Ingest all of the txt files in this directory as our guide and reference source for the project that we are about to build.”
“Create xxxx.txt in the root of this directory. It is intended to serve as a changelog and technical reference point. Its purpose is to ensure that any developer or LLM can quickly get up to speed with the current state of the project, including what has been built, how it works, and how to continue development from where we left or leave off. In a new session, this document should be specified as the primary technical reference. It will include details such as contract addresses, token addresses, relevant URLs, and file references—excluding any sensitive information like private keys. Rather than duplicating reference material, this document will point to the specific files used. For example: “We implemented [feature X] using xxx.txt as the technical guide.”
“Keep the code base to 500 lines maximum for each file created. We need this standard so that our API can make changes efficiently. Favor more modules over longer code.”
You can brainstorm prior to building. This helps the LLM flesh out an idea and iterate better
Prompt: “Do not build anything yet. Just listen to my idea and help me determine if it’s feasible or not”
“Okay, this sounds like a good plan. Start building it”
Use a free AI site like gemini, claude, or chatgpt to develop your prompt.
Prompt: rewrite this idea that I have below for a LLM that is going to build it out:
I want to create a website that lets the end user do xxxxx on the root network
While building your project, you WILL encounter errors and roadblocks.
I use ChatGPT and the “search” function to get around these issues. I search online sources and have been able to get past every single error that I encounter in my code.
Use the browser console(F12). Filter by warnings and errors. You can paste these errors in the RooCode field in response to testing your builds. It will fix most of your issues. You can paste these errors in other LLMs that have online sources to get resolutions as well.
Any resolution you find from an outside source, just paste it in RooCode and it will implement that new functionality
GOOD LUCK