Altug Sahin sahina

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

Community

Elixir Slack Group

Cheatsheets

GenServer Cheatsheet by Benjamin Tan Wei Hao

Books

My Openshift Cheatsheet

List all non openshift/kube namespaces

requires jq CLI

oc get namespaces -o json | jq '[.items[] | select((.metadata.name | startswith("openshift") | not) and (.metadata.name | startswith("kube-") | not) and .metadata.name != "default" and (true)) | .metadata.name ]'

Project Quotes, Limits and Templates

Build Server

Go to Digital Ocean
Create new droplet
London
Ubuntu
No apps
Add SSH keys

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

This is not intended to be comprehensive or authoritative, just free online resources I've found valuable while learning more about Erlang.

Joe Armstrong's Swedish Institute of Computer Science homepage (Wayback Machine)

https://web.archive.org/web/20070429181654/http://www.sics.se/~joe/


	<TEMPLATE>
	<INSTRUCTIONS>
	Use the <CODEBASE> code as reference, and convert the high-level <TASK> into a set of very detailed step-by-step instructions that an AI coding agent can complete.
	Only includes steps an AI coding agent can take. Do not include testing or any other work a human would do to confirm the task has been completed.
	ALWAYS have the agent run a build when it is complete. Be specific and decisive about what the agent should do.
	Do not include any additional meta instructions to the user. Use markdown formatting.
	</INSTRUCTIONS>
	<TASK>

	# .cursorrules

	Components & Naming

	- Use functional components with `"use client"` if needed.
	- Name in PascalCase under `src/components/`.
	- Keep them small, typed with interfaces.
	- Use Tailwind for common UI components like textarea, button, etc. Never use radix or shadcn.

	Prisma

	#!/usr/bin/env python

	'''Using Webhook and self-signed certificate'''

	# This file is an annotated example of a webhook based bot for
	# telegram. It does not do anything useful, other than provide a quick
	# template for whipping up a testbot. Basically, fill in the CONFIG
	# section and run it.
	# Dependencies (use pip to install them):
	# - python-telegram-bot: https://github.com/leandrotoledo/python-telegram-bot

	# Set variables in .bashrc file

	# don't forget to change your path correctly!

	export GOPATH=$HOME/golang
	export GOROOT=/usr/local/opt/go/libexec
	export PATH=$PATH:$GOPATH/bin
	export PATH=$PATH:$GOROOT/bin