AI & Machine Learning
Hackathon Brief Design
Write the hackathon challenge document teams read before they build - problem statements sized to the time box, thematic challenge tracks, the published rules and eligibility text, the submission-artifact checklist, sponsor-challenge framing, and naming (never weighting) the evaluation categories. Use whenever the user mentions a hackathon brief, challenge or track prompts, hackathon rules or eligibility, submission guidelines, or turning a sponsor's API into a challenge - even if they never say "brief". Challenge tracks here are thematic categories a team enters, not parallel session streams. Do NOT use for rubric weights and judging mechanics - use samber/dev-event-organizer-skills@hackathon-judging instead.
- Publisher / source
- samber/dev-event-organizer-skills (found on skills.sh)
- Upstream record
- samber/dev-event-organizer-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
2ab366c7f1f10b995e6a22655cb0146e8074cc9004d75aaf4b753961d3caf768