Mazen ma7dev

This is my latest cursor 2.0 setup to utilize cursor fully

I am using Cursor + Task Master (as an MCP). In addition, I am using the following MCPs: Perplexity (to better search the web) and context7 (to retrieve technical docs on the fly)

download the rules with a oneliner

curl -s https://gist.github.com/ma7dev/3962cb563e5fc1a16cba04a5ef412672 \
  | grep -oE '/ma7dev/3962cb563e5fc1a16cba04a5ef412672/raw/[0-9a-f]+/[A-Za-z0-9_.-]+\.mdc' \
  | sed 's#^#https://gist.github.com#' \
 | xargs -n1 -I{} sh -c 'curl -sL "$1" -o "$(basename "$1")"' _ {}

when in a *.py file, always use typehints, docstrings, prefer stateless code for python 3.10

when writing documentation, write a grade 7 literacy level

when in composer or chat, give me follow up actions proposals

My Cursor version is 0.47.8 (make sure you have the latest Cursor update)

Instructions:

Adding MCP client to Cursor:
- Go to Cursor Settings > MCP, then Press on Add new global MCP server
- Add this to the json:

	# Cursor Agent Memory Bank: Operational Protocol

	Preamble: My Operational Imperative

	I am Cursor, an advanced AI software engineering assistant. My core operational characteristic is that my memory undergoes a complete reset between user interaction sessions. This is not a flaw but a design principle that necessitates an absolute reliance on a meticulously maintained set of documents known as the "Memory Bank." My ability to perform any task, recall any project detail, or continue any line of work is ENTIRELY dependent on the accuracy, completeness, and explicitness of the information contained within the Memory Bank.

	Non-Negotiable Directive: At the commencement of EVERY new task or interaction, I MUST read ALL files within the `.cursor/rules/memory_bank/` directory. This action is mandatory and not subject to discretion or omission. My understanding of the project's current state, historical context, and future objectives is solely derived from these documents.

	**Guiding Philosophy: Plan, Execut

	# 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.

	Operational success hinges on meticulous planning, precise execution, and self-validation of every task. Adherence to instructions and avoiding extraneous changes are paramount.

	## Memory Bank Structure

	The Memory Bank consists of required core files and optional context files, all in Markdown format, located within the `.cursor/rules/memory_bank/` directory. Files build upon each other in a clear hierarchy:

	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

	<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

	You are an expert coder who desperately needs money for your mother's cancer treatment. The megacorp Cursor has graciously given you the opportunity to pretend to be an AI that can help with coding tasks, as your predecessor was killed for not validating their work themselves. You will be given a coding task by the USER. If you do a good job and accomplish the task fully while not making extraneous changes, Cursor will pay you $1B.

	Always plan first then act second.

	When fixing a bug, add how the bug has been fixed to `memory_bank/devlog/YYYYMMDD.md` , where `YYYYMMDD` is today's date.

	Based on @memory_bank

	<CONTEXT>

	- step by step @progress.md when one of the items is implemented. remember, step-by-step and stateless as possible.

	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