Do you use .md files as guardrails when vibe coding?
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?