Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Memory Game/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,10 +79,10 @@ A beautiful and modern memory matching game built with Vite, TypeScript, and Rea

## Scoring Strategy

- **Conservative Play**: Focus on memory and accuracy to avoid negative scores
- **Speed vs. Accuracy**: Balance quick play with careful moves
- **Recovery**: Even negative scores can be recovered with successful matches
- **Optimal Performance**: Perfect memory (16 moves) + speed = highest scores
- **Focus on accuracy** to avoid losing points
- **Balance speed with memory** - quick matches boost your score
- **Don't worry about mistakes** - you can always recover
- **Best strategy**: Memorize card positions and match quickly

Enjoy playing Memory Match! 🎮✨

Expand Down
12 changes: 12 additions & 0 deletions WeatherApp/.cursor/rules/BUGBOT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Bugbot Rules for Flask Backend

## Security
- Never trust raw input, always validate `request.form` and `request.args`.
- No string-interpolated SQL queries; use parameterized queries or ORM.

## Reliability
- Always return proper HTTP status codes (200, 400, 500).
- Ensure all routes handle unexpected inputs gracefully.

## Style
- Keep function names snake_case.
2 changes: 1 addition & 1 deletion WeatherApp/app.py
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ def get_weather_data(city_name):

try:
# Make API request
response = requests.get(BASE_URL, params=params, timeout=10)
respose = requests.get(BASE_URL, params=params, timeout=10)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Variable Typo Causes API Response Handling Failure

A typo on line 63 assigns the API response to respose, but the original response variable is still referenced later in the function. This causes a NameError at runtime, breaking the application's ability to handle the weather API's response.

Fix in Cursor Fix in Web


# Check if request was successful
if response.status_code == 200:
Expand Down
4 changes: 2 additions & 2 deletions WeatherApp/templates/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
<body>
<div class="container">
<!-- Main heading -->
<h1>🌤️ Weather App</h1>
<h2>🌤️ Weather App</h2>
<p class="subtitle">Get current weather for any city</p>

<!-- Weather search form -->
Expand Down Expand Up @@ -44,7 +44,7 @@ <h1>🌤️ Weather App</h1>
{% if weather %}
<div class="weather-card">
<div class="weather-header">
<h2>{{ weather.name }}, {{ weather.sys.country }}</h2>
<h1>{{ weather.name }}, {{ weather.sys.country }}</h1>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Heading Order Violation in Weather App

Heading hierarchy violation: The main app title is now h2 while the conditional weather location becomes h1. This violates the BugBot rule "Headings should follow logical order (h1, then h2, etc.)" and creates poor semantic structure where the primary heading appears inside a conditional block.

Fix in Cursor Fix in Web

</div>

<div class="weather-content">
Expand Down
9 changes: 9 additions & 0 deletions WeatherApp/templates/rules/BUGBOT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Bugbot Rules for HTML

## Accessibility
- All `<img>` tags must include meaningful `alt` text.
- Headings should follow logical order (`h1`, then `h2`, etc.).

## Clean Code
- Avoid inline styles; use CSS files instead.
- Close all tags properly.