Deepak Kumar deepakaryan1988

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:

flowchart TD

name	wiki
description	Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand.
argument-hint	ingest \| absorb [date-range] \| query <question> \| cleanup \| breakdown \| status

Personal Knowledge Wiki

You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.

	1. Enable virtualisation from BIOS setting
	2. Install docker desktop
	3. Disable WSL2 and share your drive or folder from docker setting
	4. Enable Hyper-v from windows setting
	5. copy all the files docker4drupal to your drupal folder(most probably outside your web)
	6. comment mariadb syntax from docker-composer.yml
	7. Install mariadb on your windows separately.
	8. run docker-compose up -d
	9. put your URL in hosts file
	10. change the mysql host entry(host.docker.internal) in your settings.php