ClashCode

The description states that ClashCode is a real-time, 1v1 competitive coding platform designed for university students. It includes features such as:

• Instant matchmaking between rival students.
• College-based global leaderboards and “War Rooms” for scheduled battles.
• AI-generated algorithmic problems using GPT-5.6 that are unique per match.
• A hidden sandbox judge for code execution in Python, JS, Java, or C++.
• Sub-second real-time sync via Socket.io.
• Post-match AI mentorship using GPT-5.6 to analyze submitted code.

The platform was built with a full-stack tech stack including React, Node.js, Express, PostgreSQL (via Supabase), and OpenAI API (GPT-5.6).

Confidence Low — all details are self-reported by the author.

The description states that ClashCode aims to gamify algorithmic problem-solving, turning it into a “high-stakes esports arena” rather than a silent test environment. It positions itself as an alternative to traditional hackathons and coding competitions, which it claims suffer from static problem sets and cheating.

Key claims:

• Competitive programming should feel like esports.
• AI eliminates cheating by generating novel problems on the fly.
• The platform is built for university students.
• It introduces a “College War” concept where rival colleges compete.

Confidence Low — these are positioning statements, not evidence of traction or adoption.

The description states that ClashCode is designed specifically for university students, particularly those engaged in competitive programming or preparing for coding interviews. It also mentions targeting “rival colleges” as a unit of competition.

No further segmentation or customer personas are provided.

Confidence Low — no evidence of actual users, surveys, or market research.

The description does not mention any business model or pricing strategy. There is no indication of monetization, subscriptions, fees, or revenue streams.

Confidence Not evidenced.

The project was built in a single weekend using:

• Frontend: React, Vite, TypeScript, TailwindCSS
• Backend: Node.js, Express, TypeScript
• Real-time sync: Socket.io
• Database: PostgreSQL via Supabase
• AI engine: OpenAI API (GPT-5.6)
• Tools used: Codex for rapid development

The author notes that Codex helped with:

• Architecture and type resolution.
• UI component mapping.
• Adding the “Declare War” functionality.

Challenges included:

• Ensuring deterministic outputs from GPT-5.6.
• Managing race conditions in real-time code submission.

Confidence Medium — technical details are provided but not independently verified.

There is no evidence of traction, customers, or adoption beyond the author’s own description. The project was submitted to a hackathon and has no known usage data, user growth metrics, or product iteration history.

Confidence Not evidenced.

The description does not reference existing competitors or market positioning in relation to other competitive coding platforms or esports tools. It only contrasts itself with traditional hackathons and algorithmic competitions.

Confidence Not evidenced.

• Unverified claims: The use of GPT-5.6 for problem generation, real-time sync, and AI mentorship is self-reported.
• No traction or revenue: No evidence of users, customers, or monetization.
• Single founder team: Only one member listed (Praveen Patil).
• Hackathon project: The product was built in a weekend and submitted to a hackathon — no indication of long-term development or commercial viability.
• AI hallucination risk: The description notes that early GPT prompts caused issues with deterministic outputs, suggesting potential instability.

Confidence Medium — risks are inferred from the self-reported nature of the project.

1. What is your plan for scaling beyond a single weekend hackathon?
2. Have you validated demand among university students or colleges?
3. How do you intend to monetize this platform, if at all?
4. Can you demonstrate any user testing or feedback from target customers?
5. What are the technical limitations of using GPT-5.6 for real-time problem generation?
6. Is there a roadmap beyond the current MVP?