Beyond Vibe Coding

From AI Experiments to Enterprise Solutions

Agenda

  • Vibe Coding
  • The Problem
  • The Three Pillars
  • The Workflow
  • GitHub Copilot Starter

Who Am I?

  • ๐Ÿ‘‹ Iโ€™m Raymon
  • ๐Ÿ“… 37 years
  • ๐Ÿง‘โ€๐Ÿ’ป Tech Lead at
  • ๐Ÿค– I love working with AI
  • ๐Ÿซถ Frontend Dev is my specialty since 2010

About SBB

  • ๐Ÿข Semi-government organization connecting MBO education with industry
  • ๐ŸŽ“ Ensuring MBO students learn skills that companies actually need
  • ๐Ÿค Matching students with internships at recognized training companies
  • ๐Ÿ‡ณ๐Ÿ‡ฑ Collaborating with educational institutions & businesses across the Netherlands
  • ๐Ÿ’ก Bridge between what's taught and what's needed in practice

Vibe Coding

Generating code with AI without clear rules,
standards, or context.

Then spending hours debugging when it breaks

The scenario

๐Ÿค”๐Ÿค”๐Ÿค”

AI is a fantastic engine

But it needs guidance

What's the problem?

  • AI is a pleaser
  • It's a guessing game
  • It will never ask you what you exactly mean
center

AI needs context

  • Instructions
  • Documentation
  • Design system
  • Component library
  • Code styleguides
  • Commit style
  • Database schema's
  • Figma design
  • Tickets / Userstories
  • etc..
center

How are we going to give that?

The Three Pillars

Custom Instructions

Always in context
Project-wide rules
Code standards

Agent Skills

Dynamic, modular
Specific tasks
Reusable scripts

MCP

External services
Data & integrations
Real-time context

Instructions / Rules

Universal guidelines

  • One or multiple markdown files (specific which AI coding agent your using)
  • Project conventions & architecture patterns
  • Database schema & core entities
  • Security & compliance requirements
  • High-level coding principles
  • Language-agnostic decisions

Agent skills

Structured, reusable instructions

  • SKILL.md with frontmatter (name, description) + content
  • Github Copilot, Cursor, Claude Code use the same spec ๐Ÿ™Œ
  • Dynamically loaded when needed, saves tokens

Docs: AgentSkills.io

Agent skills

Perfect for:

  • Language-specific style guides (Python, TypeScript, C#)
  • Workflow-specific tasks (testing, deployment, PR reviews)
  • Framework style guides (Vue, Angular, React, etc.)

MCP

Model Context Protocol

  • Standardized protocol for AI agents to connect with external services
  • Like USB, but for AI tooling & integrations
  • Real-time access to external data & systems
  • Integrated into agent workflows seamlessly

MCP

Perfect for:

  • Version Control: Azure DevOps, GitHub, Git
  • Design Tools: Figma, design systems
  • Frameworks & Docs: Library documentation, API references
  • Data & Services: Web search, databases, Azure/AWS
  • Communication: Slack, Teams, email integrations

Use case Custom instructions Agent Skills MCP
Universal architecture patterns โœ…
Database schema & entities โœ…
Security & compliance โœ…
Language & framework style guides โœ…
Specific task workflows โœ…
Script & tool execution โœ…
Dynamically loaded on demand โœ…
Version control integration โœ…
Design tools & systems (Figma) โœ…
Library documentation & API references โœ…
External data & services โœ…
center
center

Phase 1: Planning

  1. Refine User Stories โ€“ Sharpen the problem (Azure DevOps MCP)
  2. Verify Criteria โ€“ Check the Definition of Done (Acceptance Criteria)
  3. Create Technical Plan โ€“ Design before coding (Copilot)
  4. Generate & Sync Tasks โ€“ Automate the admin (Azure DevOps MCP)

Phase 1: Planning

What does this solve?

  • ๐Ÿš€ No context switching โ€“ Stay in your editor
  • ๐Ÿ“Š Real-time data access โ€“ User stories & criteria instantly loaded
  • ๐ŸŽฏ Skills guide Copilot โ€“ Find user stories, tasks & project context automatically
  • ๐Ÿ”— Automatic linking โ€“ Code connected to work items
  • ๐Ÿง  Knowledge reuse โ€“ Skills become team standards
  • ๐Ÿ’ฐ Token efficiency โ€“ Pay only for what you use

Phase 2: Build

  1. Guided Implementation โ€“ Build within the lines (Copilot + Instructions + MCP + Skills)
  2. Design Verification โ€“ Validate against Figma specs (Figma MCP)
  3. Best Practice Check โ€“ Ensure quality standards (Context7 MCP + Azure DevOps)
  4. Test Validation โ€“ Verify unit tests coverage (Copilot)

Phase 2: Build

What does this solve?

  • โœ… Verified against design โ€“ No surprises in code review
  • ๐Ÿ—๏ธ Architecture compliance โ€“ Best practices enforced automatically
  • ๐Ÿงช Test coverage maintained โ€“ Confidence in changes
  • ๐Ÿ“ Quality gates โ€“ Catch issues before they reach production
  • ๐Ÿ” Context-aware decisions โ€“ Real specs, not guesses
  • โšก Development speed โ€“ Build right the first time

Phase 3: Push

  1. Semantic Commits โ€“ Document the "why" (Copilot)
  2. Automated PR โ€“ Bridge the gap to the team (Azure DevOps MCP)

Phase 3: Push

What does this solve?

  • ๐Ÿ“ Clear history โ€“ Why was this change made?
  • ๐Ÿ”— Traceability โ€“ Link commits to user stories automatically
  • ๐Ÿ‘ฅ Team alignment โ€“ Everyone knows what's being pushed
  • ๐Ÿค– Automation ready โ€“ MCP handles linking & PR creation
  • ๐Ÿ“ฆ Professional handoff โ€“ Code review becomes easier
  • ๐ŸŽฏ Knowledge transfer โ€“ Future devs understand decisions

Phase 4: Review

  1. AI-Assisted Review โ€“ The Gatekeeper for quality (Prompt)

Phase 4: Review

What does this solve?

  • ๐Ÿ” Consistent quality โ€“ AI gatekeeper catches issues before merge
  • ๐Ÿ’ก Learning opportunity โ€“ AI explains why changes matter
  • โšก Faster reviews โ€“ Checklist automated, humans focus on logic
  • ๐ŸŽฏ Standards enforcement โ€“ Code quality never drops
  • ๐Ÿ›ก๏ธ Risk mitigation โ€“ Production always stays stable

TLDR;

  1. Context is everything
  2. Vibe coding is cool, but not within product applications in our organizations

GitHub Copilot Starter

github.com/devbyray/github-copilot-starter

1. It starts fun 2. We give that initial prompt in a new project 3. Everything is fine! 4. That first prompt is magic!

1. After building, everything works!

But then the frustration starts! This change was not what you mend

Ahh it changed the wrong file! Your frustration is rising

Your build is not running anymore, it gives so many errors!

Ahhh that final moment of AI breaking everything down!

Maybe AI is not that good?

Your done with AI! From now on you are coding everything by hand again!