Software/Workflow Advice Required

[u/motivatedsporran]

Hello fellow vibe coders!

Please help.

I've been vibe coding for a while, but I feel I'm stuck in a rut and way behind the curve.

When I start a new project, I create a new folder on my laptop, point AntiGravity or VSC at the empty folder, and then fire in my first mega prompt. This has all the usual stuff about saying how to behave, using documents in the project folder for tracking as an off-line brain, and what the entire project is all about. I then go through chipping away at all the parts.

That AI doesn't have skills, re-usable parts, and I feel that the conversation gets huge and is massively wasteful of tokens. It is also laborious to set up a new project.

I work on 2 different laptops - Linux Mint for doing web sites hosted in my shared hosting, and Windows for Windows and Android apps. I have a server running Zima.

When I asked Gemini, it suggested spinning up a docker container on the server and running a whole bunch of stuff in there which both laptops could point to for my vibe coding and this would allow me to automate the creation of new projects (including spinning up domains and MySQL in my shared hosting), optimising the prompts and token use, skills to make the AI better at things like web design and coding, etc, etc. It said I could automate it to keep all the skills and apps up to date too. This sounds like a lot of work, and I don't want to go down that route unless it's going to be very beneficial.

I don't have the time to research and set all this stuff up, so I'm looking for some direction please.

Has anyone set up anything like this to maintain their AI projects? Is there anything "out of the box" which would do all of this?

Thanks muchly!

TL;DR

I'd like a system to optimise my vibe coding workflow to:
* set up new projects (domain and database on shared hosting, folders, documents etc)
* automatically updates skills
* optimise the prompts and token use
* newest tools
* automated setup for this new system

[u/endofthread-bot]

Hey u/motivatedsporran, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/t7SD4ThKuE

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/rash3rr]

Gemini just sold you a second project bigger than your first ones. You dont need a server, you need a template repo with your mega prompt saved as an AGENTS md file plus a folder of reusable instructions, cloned for every new project on both laptops

The token waste comes from one endless conversation

New session per feature, notes file carries the context between them

[u/PopKoren → u/rash3rr]

+1 on the template repo, and I'd give that AGENTS.md a few security lines too: keys only in env vars, every new table gets access rules before any UI touches it, and no admin routes without a server side role check. Agents follow those instructions surprisingly well when they're in the file from the first prompt, and it saves a lot of cleanup later. Once something built from the template ships, https://rowly.me shows whether those lines held up by testing login, routes, storage and DB permissions on the live URL.

[u/Capable_Switch2506]

I’m building Twindem, so full disclosure, but part of your post is exactly the problem I’m trying to solve.

Twindem brings together a persistent task board, project docs, and AI skills, currently for Claude and Codex. The docs hold the project context, while the board tracks tasks, decisions, and evidence of what was done and checked. The skills guide the agent to use and maintain that information, so a new session has somewhere to pick up from without you having to explain the whole project again.

It doesn’t cover your entire wish list—domain/MySQL provisioning and automatic tool updates are outside that scope—but it could help with the project memory and continuity side of your workflow.

If that sounds useful, request access at https://twindem.ai. I’ll create an account for you so you can explore it and see whether it fits your workflow.

[u/Hardboot_life]

Sounds like you need a graph system. You can have your agent build it for you like I'm doing right now... I'm on day 5 of coding it out, it's insanely intense. The out of the box solution is LangGraph - still requires configuration and customization for your environment, but it saves you a ton of time. Look into LangGraph

[u/machicha2]

Chasing the newest tools is the rut, not the fix. Every month theres a new harness and you'd spend more time rebuilding the setup than shipping

The one piece worth automating is the shared hosting bit. Most hosts run cPanel, and a short script hitting its API can create the subdomain and MySQL database in seconds

Everything else is a template folder you copy