Vibe coding is fast, but it often skips the fundamentals: project structure, typing, testing, error handling, and review discipline.
Matt Pocock's skills repo https://github.com/mattpocock/skills is one of the most practical attempts to fix that. It doesn't just say "write tests" — it gives you repeatable, context-rich engineering prompts you can drop into your workflow.
What makes it useful:
If you're using AI to ship quickly, the bottleneck is no longer generation speed — it's whether the output is actually maintainable. Skills like these are how you close that gap. Have you tried structuring your AI-assisted workflow around reusable engineering skills?
source & further reading
dev.to — original article
Retry patterns: when you should give up (and why most code doesn't)
A blockchain is a line. We built a mesh: the architecture of offline-first validation
Your agent ignored a failed tool call. Here's how to catch that in CI.