Do you know the best practices to start vibe coding?

Vibe coding empowers non-developers to build software using AI agents. However, without proper foundation and structure, vibe coding can result in unmaintainable code that fails "the bus test" – meaning if you were hit by a bus tomorrow, no one else could understand or maintain your code.

The key to successful vibe coding is starting with the right foundation. This means ensuring your code lives in a proper repository, uses proven architectural patterns, and leverages existing AI guidance.

Start in GitHub

Starting with code on your local machine or in an unmanaged environment

Create your repository in the SSWConsulting GitHub organization from the start

Starting your project in GitHub, specifically within your organization, ensures:

Version control - Every change is tracked and can be reverted
Collaboration - Others can contribute and review your code
Backup - Your code is safely stored in the cloud
Transparency - Team members can see what you're building
The bus test - If you're unavailable, others can take over

Use architecture templates

Don't start from scratch! Use one of these battle-tested SSW templates that already include comprehensive AI guidance:

Clean Architecture Template

Use the SSW Clean Architecture template which includes:

Proper separation of concerns (Domain, Application, Infrastructure, Presentation layers)
Built-in dependency injection
Comprehensive agents.md files guiding AI on architectural decisions
.github/copilot-instructions.md for GitHub Copilot integration
Pre-configured with best practices and patterns

Learn more about Clean Architecture principles and Rules to Better Clean Architecture

Vertical Slice Architecture Template

Alternatively, use the SSW Vertical Slice Architecture template which offers:

Feature-focused organization (each slice is a complete vertical through all layers)
Easier to understand for non-developers
AI guidance files pre-configured
Less ceremony than Clean Architecture for simpler projects
Faster to get started with

Learn more about working in vertical slices and Rules to Better Vertical Slice Architecture

Which template should I use?

Choose Clean Architecture if you need more structure and guardrails
Choose Vertical Slice Architecture if you want to move fast and iterate quickly

See the software architecture decision tree for more guidance on choosing the right architecture.

Drive development from GitHub Copilot Workspaces

Once your repository is set up with a template, use GitHub Copilot Workspaces to drive your development:

Open your repository in GitHub Copilot Workspace - This gives the AI full context of your codebase
Describe what you want to build - Use natural language to explain your feature or change
Review the AI's plan - The AI will propose changes based on your architecture template and existing code patterns
Let the AI implement - Copilot Workspace will make the changes directly in your repository
Create a Pull Request - Review the changes before merging to main

"Add a user registration feature with email and password"

Figure: Good example - Clear requirement that the AI can implement following the template's patterns

Why this approach passes the bus test

By following these practices, your vibe-coded project will be:

✅ Maintainable - Following proven architecture patterns ✅ Understandable - Using standard structures that developers recognize ✅ Documented - Architecture decisions are encoded in the template ✅ Reviewable - All changes go through pull requests ✅ Professional - Indistinguishable from code written by experienced developers

Remember: The goal isn't just to make code work – it's to create code that others can understand, maintain, and extend. Starting with these best practices ensures your vibe coding produces professional-quality software.

Learn more

AI Development