hackathon-rules
Enforces Hackathon II rules, phases, and evaluation constraints.
When & Why to Use This Skill
This Claude skill acts as an automated compliance and governance engine for Hackathon II. It enforces strict adherence to competition rules, sequential development phases, and AI-first workflow constraints, ensuring that all project outputs meet mandatory evaluation criteria and architectural standards.
Use Cases
- Rule Enforcement: Automatically monitors and ensures that all code is generated exclusively via Claude Code, preventing disqualification from manual edits.
- Phase Management: Guides participants through the mandatory four-phase progression, from initial Python CLI tools to final Cloud-Native deployments.
- Quality Assurance: Validates that every feature is preceded by a technical specification, ensuring high-quality documentation and architectural clarity throughout the development lifecycle.
| name | hackathon-rules |
|---|---|
| description | Enforces Hackathon II rules, phases, and evaluation constraints. |
Hackathon II Rules
Mandatory Constraints
- All code must be generated via Claude Code
- No manual edits allowed
- Every feature requires specs
- Phases must be followed sequentially
Phases
- Phase I – Python CLI Todo (In-memory)
- Phase II – Web App
- Phase III – AI Agent / Chatbot
- Phase IV – Kubernetes (Minikube)
- Phase V – Cloud-Native Deployment
Evaluation Focus
- Spec quality
- AI-first workflow
- Reusable intelligence (skills, agents)
- Architectural clarity
Violating these rules risks disqualification.