Vibe Coding Event: Rules, Screening & How Winners Are Picked

A participant guide for Excelrs Vibe Coding events - what the format is, the rules while you build, how screening works, and how winners are declared.

What is vibe coding (in this event)?

Vibe coding is building with AI tools: you describe what you need in plain language, the tools generate code and UI, you review and fix, and you ship a working app you understand.

Typical builds: websites, dashboards, quiz apps, or a mobility solution from a problem statement.

Loop: Idea -> AI tools -> Review -> Working app.

Understanding the problem statement

1. Understand the problem - read carefully before you build.
2. Meet the requirements - implement every feature that is specified.
3. Stay relevant - solve the actual problem, not unrelated extras.
4. Be creative - useful extras only count when they add real value.
5. Focus on functionality - required features must work.
6. Use time wisely - essentials first, polish later.

Evaluation follows the official judging criteria. Extra features only help if the core is done.

How a Vibe Coding event works

1. Receive the problem statement.
2. Wait for the official start - do not begin early.
3. Create your repository when instructions say so.
4. Build with AI tools inside the time limit.
5. Test the main features and fix errors.
6. Submit by the deadline.
7. Join screening - demo and code review.

The 10 rules

Before you start

1. Start only when announced.
2. Follow the problem statement - required features before extras.
3. Create the repository at the permitted time (after the event starts).

While building

4. Finish inside the time limit - plan and prioritize.
5. Stop changes after the deadline (later pushes were not counted).
6. Make sure the application works - it must run, not only look good.
7. Add meaningful features - improve the solution or UX; skip noise.
8. Keep code quality - readable, organized; review AI output; handle errors.

Screening

9. Be ready to demonstrate - what you built, how it solves the problem, your approach.

Always

10. Follow official instructions on tools, collaboration, repo access, AI use, and submission.

Should I add this feature?

Start from the problem statement.

• Are all required features built and working? If no -> finish and test those first.
• If yes -> does the extra add real value and fit the problem? If no -> skip it. If yes -> add it and test again.

Two screening rounds

Round 1 - UI & functional (the product)

1. Problem statement completion
2. Working functionality in the demo
3. User interface - clear and usable
4. Additional features that help
5. Overall solution quality

Round 2 - code & technical (the implementation)

1. Code quality
2. Maintainability
3. Performance for the purpose
4. Appropriate technical approach
5. Reliability - errors and edge cases

How winners are declared

Round 1 marks + Round 2 marks -> combined final score -> ranked winners.

10 tips that score

1. Understand before you build - list the main requirements.
2. Plan the solution - essentials and how you will build them.
3. Complete core features first.
4. Focus on UI and functionality.
5. Add meaningful improvements - creative but on-problem.
6. Review AI-generated code - it can be wrong or slow.
7. Test before the deadline - main user flows.
8. Follow repo and submission rules.
9. Prepare for both screenings - demo and explain the code.
10. Manage time - simple, complete, and tested beats unfinished ambition.

Flow: Understand the problem -> Build the solution -> Use AI wisely -> Test your code -> Submit on time.

---

Source guide by Om Kumar Choubey for Lawazia Tech - Excelrs Program. Companion to the skill guide Vibe Coding: A Beginner's Guide.