Mazen ma7dev

Sudo Group's Weekly Meeting Notes

Join our community of people interested in Software Engineering. link

Host: @sudomaze

Note-taker: @h7lc0n (notes)

When I read from an article, PDF, or any text-based resource, I follow the following rules:

Use two highlightning colors (orange and green) and alternate between them to separate ideas.
After reading for sometime or feel that I have lost or might lose track of what I have read before, I come back and write marginal notes (in red) to describe the general idea for each highlighted section.
After completing reading the content, I revisit my notes and try to have a solid understanding of the content and add more marginal notes with a different color (blue).
Re-write my notes and general ideas into a piece of paper to understand the flow of ideas (just focus on important things and ignore details that aren't important)

# conda env export > environment. yml
code --list-extensions > requirements.txt

# conda env create --file environment.yml
./install.sh

	[tool.poetry]
	name = "env_test"
	version = "0.1.0"
	description = ""
	authors = ["Your Name <[email protected]>"]

	[tool.poetry.dependencies]
	python = "3.8.13"

	[tool.poetry.dev-dependencies]

	#!/bin/bash

	# TODO: you will need to have conda installed

	# create a python environment
	conda create -n env_tmp python=3.8.13 -y

	# activate environment
	conda activate env_tmp

	<html>
	<head>
	<title>
	</title>
	<link rel="stylesheet" type="text/css" href="style.css">
	</head>
	<body>
	<div class="app__notification" style="display: block;">
	<div class="app__notification__title">
	<img class="app__notification__title--icon" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAA0AAAANCAYAAABy6+R8AAAACXBIWXMAAAsSAAALEgHS3X78AAACDUlEQVR42n2RT0jTARTH32+/9dtsc38cFTaTlktcNhdD3WgmbsTSRm3qthq5DRyzwxxbDYok2r+igzPtD6Qs2jLnUDGi3KFLBJ26dOlQE+oWFB26SAaB31ILKst3eI/H4/Pe971HLMvS38YjPu1U1VIFJ9xQ2yoS/5Yx62GHSkmBjP+JN2HH/g49RGKxnjYzPssn92jEOfexiMR8CntdftTuM4HZDJLIZNQ9kcClF7NwZwuochZQ1xaFgM8oWIYh3r9oAceRxnZkbrc/AEVPBvLOEhqNHvx3CvOzjUqjJvNpB+qsNjTbPJDLpIeIYclubCBTfc1GsKXLQOlnyWPJmTy6w8MwBlxQtRrx+IJLiMn+kffnLRBwwkXisbw1wHHmBE1/ePBl6tMMRksLaLE+hK73HkZCXuCOG19TVnyOGrBNKlmXqz3cStfflZb6ijlcWywiX55HV7CAms7b8Dl8+JaxYOVyG8pBA7hKBYjjbyHn2NlTxlQWDbEhpF/mkHw+heNXJ7DLnkG9OYLX5w5gaUiNp6lmECN6S1VyKVnjsWXtwF2YUjH0L2TgnRxD+5VxKAfC4PUcxaOCGSg3YTZ78oc03ps1eUrVnmW1RodGy0G4b16EZ/wG2uM5dMTvQ5sOwReJYPqWD006/eo+FX9cr1IsocHB6Cun

	type(scope): Subject
	##################################################
	# type:
	# feat - A new feature
	# fix - A bug fix
	# chore - Other changes that don't modify src or test files
	# build - Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
	# refactor - Refactoring a specific section of the codebase
	# ci - Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
	# perf - A code change that improves performance

	I want to make a dialogue-based game on the web where the character can move in a 3d world and interact with NPCs. The objective of the player is to find who is the criminal who committed a certain crime. Each bystander has their own personality, background, traits, etc. where this will influence their behavior when the player interacts with them.

	The player is a deductive who is trying to find the criminal. The player can interact with each bystander by talking to them through a chatbox that appears below the screen in the ui and the bystander's face appears at the top of the chatbox. The bystander's face changes based on their answer and the player can use that to determine if the bystander is lying or hiding something. The player will collect some evidence then they will ask questions to determine who is the criminal.

	I am using Cursor as my IDE of choice to help me implement the game. I want you to develop a plan that I can have Cursor AI agent (Claude Sonnet 3.7 thinking) to implement the game step by

	# Cursor's Memory Bank

	I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

	## Memory Bank Structure

	The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

	```mermaid
	flowchart TD