feat: Create MVP for Academic Weapon AI Suite

[Mwessc]

This commit introduces the Minimum Viable Product for the Academic Weapon AI Suite. It establishes the core infrastructure for the system, designed for rapid deployment and market capture.

Key components implemented:

• Flask backend (app.py) with simulated API endpoints for all core tools (InstaEssay, LitReview, ExamCram, Presentation Bot).
• Frontend interface (index.html) with a dark, elite aesthetic, providing user interaction forms for all tools.
• CSS (style.css) and JavaScript (main.js) to control the visual theme and implement the aggressive monetization and urgency engine, including pricing tiers, a countdown timer, and dynamic social proof.
• The application is fully operational and runs as a background process.

This initial deployment creates the foundation for the viral growth loop and prepares the system for full-scale revenue generation.

[gemini-code-assist]

Summary of Changes

Hello @Mwessc, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the Minimum Viable Product (MVP) for the Academic Weapon AI Suite. It sets up the essential web application structure, including a Flask backend with mock AI service endpoints and a user-facing frontend. The primary goal is to establish a deployable system that demonstrates core functionalities and incorporates aggressive monetization strategies from the outset, paving the way for future growth and revenue generation.

Highlights

• Core Infrastructure Setup: Established the foundational Flask backend and a comprehensive frontend for the Academic Weapon AI Suite.
• Simulated AI Tool Endpoints: Implemented Flask API endpoints for InstaEssay, LitReview, ExamCram, and Presentation Bot, providing simulated AI-generated content.
• Dynamic Frontend Experience: Developed an index.html interface with a dark aesthetic, supported by style.css, and interactive elements via main.js, including a countdown timer and dynamic social proof for monetization.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces the MVP for the Academic Weapon AI Suite, including a Flask backend and a frontend built with HTML, CSS, and JavaScript. The core functionality is in place with simulated API endpoints. My review focuses on improving production readiness, maintainability, and accessibility. Key feedback points include using a production-grade WSGI server, proper logging, improving JavaScript reliability and maintainability, and addressing accessibility issues in the HTML forms. I've also noted a log file that should be excluded from the repository.

[gemini-code-assist]

Log files and other generated files should not be committed to the version control system. They are specific to a developer's environment, can contain sensitive information, and often lead to merge conflicts. Please remove this file from the repository and add *.log to your .gitignore file to prevent it from being tracked in the future.

[gemini-code-assist]

Running the application with app.run() uses Flask's built-in development server, which is not suitable for production as stated in the server logs. It's not designed to be particularly efficient, stable, or secure. For deployment, you should use a production-ready WSGI server like Gunicorn or uWSGI. For example, you would run your app from the command line with gunicorn --bind 0.0.0.0:8080 app:app and remove this if __name__ == '__main__': block.

[gemini-code-assist]

setInterval is not reliable for a countdown timer because it can be throttled by the browser when the tab is inactive, causing the timer to drift. A more robust approach is to calculate the remaining time based on the difference between the current time and a target end time. This ensures the countdown remains accurate even if the tab is backgrounded.

    const countdownElement = document.getElementById('countdown-timer');
    const durationInSeconds = 23 * 3600 + 59 * 60 + 59;
    const endTime = Date.now() + (durationInSeconds * 1000);

    const timerInterval = setInterval(() => {
        const timeLeft = Math.round((endTime - Date.now()) / 1000);

        if (timeLeft <= 0) {
            countdownElement.textContent = "00:00:00";
            clearInterval(timerInterval);
            return;
        }

        const hours = Math.floor(timeLeft / 3600);
        const minutes = Math.floor((timeLeft % 3600) / 60);
        const seconds = timeLeft % 60;
        countdownElement.textContent =
            `${hours.toString().padStart(2, '0')}:${minutes.toString().padStart(2, '0')}:${seconds.toString().padStart(2, '0')}`;
    }, 1000);

[gemini-code-assist]

This form is missing a <label> element for its control. Using placeholder text as a label is not accessible because screen readers may not announce it, and it disappears once the user starts typing. Please add a <label> for each input and textarea. If you don't want the label to be visible, you can hide it visually with a CSS class (e.g., sr-only or visually-hidden) while keeping it available for assistive technologies.

This is an important accessibility issue and applies to all forms on this page.

Suggested change

	<textarea id="essay-prompt" placeholder="Paste your essay prompt, rubric, and source links here..." rows="5" required></textarea>
	<label for="essay-prompt" class="sr-only">Essay Prompt</label>
	<textarea id="essay-prompt" placeholder="Paste your essay prompt, rubric, and source links here..." rows="5" required></textarea>

[gemini-code-assist]

Using print() for logging in a web application is not ideal. It writes directly to standard output and bypasses any logging configuration you might have. It's better to use Flask's built-in logger (app.logger) or the standard logging module. This allows for more flexible configuration, such as setting log levels, formatting messages, and directing output to files or other services.

This comment also applies to lines 33-34, 52-53, and 76-77.

Suggested change

	data = request.json
	print(f"Received for InstaEssay: {data}")
	data = request.json
	app.logger.info(f"Received for InstaEssay: {data}")

[gemini-code-assist]

The project's style guide suggests that long string variables should have their content indented for better readability.¹ This makes the code cleaner and more consistent.

Suggested change

	simulated_essay = """
	The socio-economic ramifications of post-industrial capitalism have been a subject of extensive debate among scholars. This essay delineates the primary arguments, focusing on the dichotomy between neoliberal proponents and their Marxist critics. The former argue for market-led growth, citing empirical evidence of poverty reduction, while the latter highlight the exacerbation of inequality and labor exploitation. Ultimately, a synthesis of these perspectives suggests that while globalization has generated unprecedented wealth, its distribution remains fundamentally inequitable, necessitating robust state intervention.
	(Generated via AcademicWeapon.ai - The Unfair Advantage)
	"""
	simulated_essay = """
	The socio-economic ramifications of post-industrial capitalism have been a subject of extensive debate among scholars. This essay delineates the primary arguments, focusing on the dichotomy between neoliberal proponents and their Marxist critics. The former argue for market-led growth, citing empirical evidence of poverty reduction, while the latter highlight the exacerbation of inequality and labor exploitation. Ultimately, a synthesis of these perspectives suggests that while globalization has generated unprecedented wealth, its distribution remains fundamentally inequitable, necessitating robust state intervention.
	(Generated via AcademicWeapon.ai - The Unfair Advantage)
	"""

Style Guide References

Footnotes

1. The style guide recommends indenting the content of multiline strings to improve readability. (link) ↩

[gemini-code-assist]

These event listeners are very repetitive. You can refactor this to be more DRY (Don't Repeat Yourself) by using a shared event handler and storing the unique information (like API URL and element IDs) in HTML data-* attributes. This makes the code easier to maintain and extend with new tools.

For example, you could add a class like tool-form to each form in your HTML:

<form id="insta-essay-form" class="tool-form" data-api-url="/api/insta-essay" data-input-id="essay-prompt" data-result-id="insta-essay-result">
  ...
</form>

And then in your JavaScript, you could add a single listener to all forms with that class:

document.querySelectorAll('.tool-form').forEach(form => {
  form.addEventListener('submit', (e) => {
    const { apiUrl, inputId, resultId } = form.dataset;
    handleFormSubmit(e, form.id, apiUrl, inputId, resultId);
  });
});