Discover gists

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

How to install game-porting-toolkit (aka proton for macOS)

You also might wanna just use Whisky which does this automatically

This guide works on macOS 13.4+ using Command Line Tools for XCode 15 Beta!

What is this?

In the recent WWDC, Apple announced and released the "game porting toolkit", which upon further inspection this is just a modified version of CrossOver's fork of wine which is a "compatibility layer" that allows you to run Windows applications on macOS and Linux.

Config files

To configure Zsh for your user’s session, you can use the following files:

$ZDOTDIR/.zshenv
$ZDOTDIR/.zprofile
$ZDOTDIR/.zshrc
$ZDOTDIR/.zlogin
$ZDOTDIR/.zlogout

By default, Zsh will try to find the user’s configuration files in the $HOME directory. You can change it by setting the environment variable $ZDOTDIR.

Windows 10 - Using Git Bash With TMUX

Why Not Use WSL?

I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve, dotnet watch run, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.

That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull on my "windows" project folder, and do a production build there

Docker Hub 镜像加速器

国内从 Docker Hub 拉取镜像有时会遇到困难，此时可以配置镜像加速器。

Dockerized 实践 https://github.com/y0ngb1n/dockerized

1️⃣ Docker daemon 配置代理（推荐）

参考 Docker daemon 配置代理

	#!/usr/bin/env bash

	# chmod +x this script (terminal command e.g. `chmod +x xseed_qbit_cat_filter.sh`)
	# put the following execution command in your qbit with its absolute path from qbit's
	# perspective (container path if docker).
	#
	# /path/to/xseed_qbit_cat_filter.sh "%F" "%L" "%N" "%T" "%I"

	TORRENT_PATH=$1
	TORRENT_CAT=$2

	tap "homebrew/bundle"

	brew "ffmpeg"
	brew "git"
	brew "git-flow"
	brew "hugo"
	brew "imagemagick"
	brew "mas"
	brew "node"
	brew "rbenv"

	networking.firewall = {
	# 8000 = Rustdesk?
	# 21115-21117 = Rustdesk https://rustdesk.com/docs/en/self-host/
	# 21118 and 21119 = Rustdesk Web Client
	allowedUDPPorts = [ ... 22 21116 ... ];
	allowedTCPPorts = [ ... 22 8000 21115 21116 21117 21118 21119 ... ];
	};

	systemd.tmpfiles.rules = [
	"d /opt/rustdesk 0700 root root"

	MIT License

	Copyright (c) 2022-present, cayter

	Permission is hereby granted, free of charge, to any person obtaining a copy
	of this software and associated documentation files (the "Software"), to deal
	in the Software without restriction, including without limitation the rights
	to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	copies of the Software, and to permit persons to whom the Software is
	furnished to do so, subject to the following conditions:

	https://www.chronophoto.app/web.html \| Chronophoto - The Photographical History Game
	https://maxbittker.github.io/broider/ \| broider
	https://www.searchthedeck.com/ \| Search The Deck
	https://news.ycombinator.com/item?id=34531989 \| Ask HN: What have you created that deserves a second chance on HN? \| Hacker News
	https://www.coursera.org/learn/modernrobotics-course1/supplement/htN7x/welcome-to-the-specialization \| Welcome to the Specialization! \| Coursera
	http://hades.mech.northwestern.edu/index.php/Modern_Robotics \| Modern Robotics - Northwestern Mechatronics Wiki
	https://pypi.org/project/modern_robotics/ \| modern_robotics · PyPI
	https://beagleboard.org/blue \| BeagleBoard.org - blue
	https://odriverobotics.com/ \| ODrive
	https://datasette.io/examples \| Datasette Examples