Rules

1. Team Size

Only solo participation & team of 2-4 members during the hackathon is allowed!

2. Code of Conduct

Harassment of any kind, or the inclusion of NSFW content in your project, will result in an immediate ban. We follow the GitHub Community Code of Conduct.

3. Intellectual Property

You own everything you build! By submitting, you grant the organizers the right to feature your project in highlight reels, social media, and wrap-up reports to celebrate your work.

4. Progress Tracking

YOU MUST KEEP TRACK OF YOUR PROGRESS! This can be done by having a public GitHub repository for your project. We may ask to see it at the end of the hackathon.

5. AI & "Vibe Coding" Disclosure

We encourage AI tools (like GitHub Copilot, Cursor, etc.). However, you must include a "Vibe Log" in your README explaining how you used AI to accelerate your build and what prompts or workflows were key.

6. The "No Ghosting" Rule

Participants are expected to be active in the community (Discord/Slack) during the hacking period. If your project is selected for a prize, you must be available to answer brief technical questions from the judges during the judging window.

7. Be Kind

Provide constructive feedback to others and maintain a supportive community atmosphere!

8. Originality & Plagiarism

While you can use libraries, APIs, and open-source frameworks, the core logic and "vibe" of the project must be your own. "Skinning" an existing project (changing just the UI of someone else's work) is strictly prohibited and will lead to immediate disqualification.

9. Submissions Timeline

Your project must have been entirely made during the hackathon period. You may use pre-existing assets, but you must disclose them and explain how your project relates & what problem it solves.

10. Technical Requirements (The "Ship" Rule)

To be eligible for judging, your submission must include: a link to the public GitHub repository; a short demo video (1–2 minutes) or a live hosted link (Vercel, Netlify, etc.); and a clear README with setup instructions.

11. Eligibility Check

Projects without a working demo or a README will be automatically moved to the bottom of the pile to save judges' time.