r/builderstudio

First of all, I am not a pro developer. Therefore, take my observations with a grain of salt.

When vibe coding, do you create ".md" files as guardrails, or do you mostly rely on GitHub to track source code changes?

I am starting to think these are two different things.

GitHub is great for tracking what changed in the code.

But ".md" files can explain why the project is structured a certain way, what the AI should not touch, what rules it should follow, and what decisions were already made.

For example:

- "README.md" - what the app does

- "ARCHITECTURE.md" - how the system is designed

- "PROJECT_RULES.md" - what the AI should not change

- "API.md" - expected backend behavior

- "DATABASE.md" - schema and migration rules

- "PROMPT.md" - actual prompt used to generate the code especially for complex projects

I wonder how many people actually maintain these kinds of files while vibe coding.

Do you use ".md" files as project guardrails, or do you just rely on commits, branches, and pull requests to keep things under control?

Most AI tools still work like a single assistant: one prompt, one response, one path forward.

Agentic swarming changes that.

Read about our approach to Agentic Swarming in BuilderStudio below

https://builderstudio.dev/assets/research/agentic_swarming_wundercorp.pdf

Instead of asking one AI agent to do everything, a swarm breaks a larger goal into coordinated specialist lanes. One agent might work on product copy. Another might prepare outreach. Another might inspect QA issues. Another might review security risks. Each lane has a role, a goal, and a clear output.

A good agentic swarm is controlled, reviewable, and approval-gated. The user sets the goal, reviews the plan, approves the run, and gets back separate outputs that can be inspected before anything moves forward.

Why it matters, agentic swarming helps you to:

· Move faster without forcing one AI agent to handle every task.
· Get better specialization across product, marketing, operations, QA, and security.
· See what each agent did instead of getting one blended black-box answer.
· Keep human approval at the center of the workflow.

For teams, this means AI can start to look less like a chatbot and more like a coordinated execution layer. One goal. Multiple specialist lanes. Clear outputs. Human control.

That is the promise of agentic swarming.

We would like to thank

u/NousResearch

u/Teknium

u/nvidia

For creating Hermes Agent and allowing us to make agentic swarming within BuilderStudio a reality.

https://reddit.com/link/1tw44ub/video/a9qb03in455h1/player

Recently inspired by the new Hermes footer design so we decided to build our own implementation of it.

If you would like us to drop a tutorial on how we achieved it let us know!

Lately, I have been thinking about agentic AI in general and skills in particular.

To me, agentic AI is not just a chatbot giving answers. It is more like an AI system that can take a goal, break it into steps, use tools, check the result, and keep moving forward.

But the part I find interesting is skills.

I don’t see skills as just prompts. I see them more like reusable playbooks. Almost like a way to teach the AI how you want certain work done.

For example, instead of explaining the same deployment process over and over again, you could have a deployment skill. Instead of explaining your code review process every time, you could have a code review skill. Same for testing, documentation, database setup, security checks, or app generation.

So the agent becomes the one deciding what needs to happen, and the skills become the repeatable ways of doing the work.

That feels like a big shift to me.

We are moving from:

“AI, answer this question”

to:

“AI, use the right process and get this done.”

I think this is especially important for software development, because a lot of value is not only in generating code, but in repeating the right process consistently: build, test, deploy, validate, improve.

Are skills just better prompts, or are they becoming something closer to reusable operating procedures for AI agents?

I am genuinely curious what everyone thinks about the subject. Let’s explore together.

Additionally, are you using tools like OpenClaw or Hermes?