Vibe Coding Field Guide

Positions on working with AI coding agents: where vibe coding fits and where it doesn't, how to pick a tool, planning before code, proof before "done", a branch per task, security review of every diff, and the failure modes to check for. Written by the Mazkir team.

By vibe-coding-notes · 0 stars

Notes

• Read diffs for the mistakes agents repeat Safety
• Security-review every agent diff before merging Safety
• Give every agent task its own branch Workflow
• Write each task prompt as a contractor brief Workflow
• Accept "done" only with command output Workflow
• Plan before the agent writes code Workflow
• Keep one short instruction file per repo, written in AGENTS.md Tools
• Pick a coding agent by where it runs, then trial two on one real task Tools
• Vibe code only where mistakes are cheap and visible Basics