Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/moradoadrian/carneroDev/llms.txt

Use this file to discover all available pages before exploring further.

Every project submitted at Carnero.Dev is evaluated against the same balanced, five-criteria rubric worth a maximum of 100 points. An independent panel of external judges scores each team separately — organiser staff do not participate in scoring. The rubric is intentionally multidimensional: it rewards technical depth while equally valuing the clarity of your solution’s real-world impact, the quality of its user experience, and your ability to communicate the vision concisely.

Scoring Rubric

Innovation — 30%

Measures the originality of the concept and the disruption level of the proposed solution. Judges ask: is this a genuinely fresh, creative idea that challenges conventional approaches, or an incremental improvement on something well-established? Bold technical and conceptual bets are rewarded here.

Real Impact — 25%

Assesses the viability and effectiveness of the technology solution in addressing the stated problem. A high score requires demonstrating that the project solves a real need, that the approach is technically feasible beyond the demo, and that the solution could realistically be deployed or scaled.

Technical Function — 25%

Evaluates the robustness of the architecture, quality of the source code, correct and purposeful use of tools and libraries, and the overall stability of the working prototype. Judges will inspect commit history and interact directly with the live demo to verify functionality.

UX/UI Design — 10%

Scores the usability and aesthetic quality of the product interface. Judges look for coherent user flows, intuitive navigation, accessible visual design, and an experience that a non-technical user could engage with confidently. Polish matters — but so does function over form.

Final Presentation — 10%

Rates the clarity and persuasiveness of the 3-minute pitch, including the quality of supporting slides and the team’s ability to field technical and business questions from the judge panel. Conciseness, structure, and confidence all factor into this score.

Scoring Eligibility Requirements

Two conditions must be met for a project to be eligible for scoring:
  • The team must have a valid public GitHub repository with demonstrable commits made during the event window (after the Friday 11:00 AM kickoff and before the Sunday 8:00 AM freeze).
  • Any evidence of pre-built or plagiarised software — including code carried over from a previous project, copied from another team, or AI-generated wholesale — will result in an immediate 0% on the entire technical rubric. Judges actively review commit timelines.

Special Recognitions

In addition to the main competition rankings, two honorary awards will be granted by the judge panel based on outstanding achievement in specific dimensions:

Mención de Innovación Disruptiva

Awarded to the team that demonstrates the most audacious software architecture or technical integration of the event. Recipients receive a physical medal and a digital badge recognising exceptional technical creativity that pushes the boundaries of what was expected in 36 hours.

Mención de Diseño & UX

A special recognition for the team that delivers the most aesthetic, usable, and user-centred digital product. This award celebrates projects where thoughtful UX decisions, visual design quality, and intuitive interaction set the experience apart from every other submission.
The most successful teams at Carnero.Dev will not be the ones who pour everything into a single criterion. A technically flawless project with a confusing interface and a weak pitch rarely outscores a well-rounded entry. Invest time across all five dimensions — solid code, clear UX, a defensible real-world use case, genuine novelty, and a confident 3-minute story. That balance is exactly what the rubric rewards.

Build docs developers (and LLMs) love