ArguMentor: Building an AI Debate Partner in Five Days
Inspiration
The idea for ArguMentor was born from frustration.
I noticed that many students — including myself — could memorize information, but struggled to defend ideas under pressure. In debates, the real challenge is not knowledge, but structure. An argument is not emotion. It is logic.
At its core, a strong argument can be simplified as:
[ Argument = Claim + Evidence + Reasoning ]
Yet most students skip the reasoning layer entirely.
I wanted to build a tool that forces users to confront their weak logic — instantly.
That is how ArguMentor began.
What I Learned
Before starting this project, I had little to no experience building full-stack applications. Over five intense days, I learned:
- How web applications communicate with APIs
- How to structure asynchronous JavaScript requests
- How prompt engineering influences AI output
- How to design minimal but functional UI
- How to deploy a live product
I also learned something more important:
[ Execution > Perfection ]
Speed and clarity matter more than complexity in a hackathon environment.
How I Built the Project
The architecture was intentionally simple:
- Frontend: HTML, CSS, Vanilla JavaScript
- AI Engine: OpenAI API
- Deployment: Static hosting platform
The logic flow was straightforward:
- User inputs an argument.
- The system sends it to the AI model.
- The model responds as a critical opponent.
- The response is displayed instantly.
To strengthen the interaction, I designed a structured AI prompt:
- Challenge logical fallacies.
- Demand evidence.
- Offer counterexamples.
- Avoid emotional bias.
In mathematical terms, I imagined debate quality as:
[ Q = \frac{Logical\ Strength + Evidence\ Depth}{Emotional\ Noise + Vagueness} ]
ArguMentor’s goal is to maximize ( Q ).
Challenges I Faced
1. API Errors and Debugging
The first obstacle was understanding why requests failed.
Authentication errors, incorrect headers, malformed JSON — each mistake required careful reading and debugging.
I learned that most technical problems are not dramatic. They are precise.
2. Prompt Engineering
At first, the AI responses were too generic.
Then too aggressive.
Then too vague.
Refining prompts taught me that small wording changes can drastically alter output quality.
AI is powerful — but direction defines its usefulness.
3. Time Pressure
Five days is short.
There was a constant trade-off between adding features and ensuring stability. I made a deliberate decision:
Ship a minimal, reliable core — not an overloaded prototype.
What This Project Represents
ArguMentor is more than a chatbot.
It represents a shift from passive learning to active intellectual resistance.
In a world filled with information overload and misinformation, the ability to defend an idea logically is critical.
Debate is not conflict.
It is structured thinking under pressure.
And that is a skill worth training.
Future Vision
If expanded, ArguMentor could include:
- Argument scoring algorithms
- Logical fallacy detection
- Debate history tracking
- Competitive multiplayer mode
Ultimately, I envision it as a platform that helps students transform from reactive thinkers into structured, analytical minds.
Because in the long run:
[ Strong\ Thinking \rightarrow Strong\ Decisions \rightarrow Strong\ Future ]
And that is the real objective.
Built With
- api
- css
- fetchapi
- gpt-4o-mini
- html
- javascript
- openai
Log in or sign up for Devpost to join the conversation.