larryyangsen

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

Playwright E2E Testing Guidelines

Test Structure and Organization

Store all tests under the tests/ folder
Name test files based on the system component being tested (conceptual, not React component)
Group related tests within a single file using test.describe blocks
Use descriptive test names that explain the functionality being tested
use test.use({storageState: ...}) for setting auth state across all test in the suite

Locator Strategy

Linux Desktop on Apple Silicon in Practice

I bought M1 MacBook Air. It is the fastest computer I have, and I have been a GNOME/GNU/Linux user for long time. It is obvious conclusion that I need practical Linux desktop environment on Apple Silicon.

Fortunately, Linux already works on Apple Silicon/M1. But how practical is it?

Two native ports exist.

Everything I Know About UI Routing

Definitions

Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app
1. pathname - The "file/directory" portion of the URL, like invoices/123
2. search - The stuff after ? in a URL like /assignments?showGrades=1.
3. query - A parsed version of search, usually an object but not a standard browser feature.
4. hash - The # portion of the URL. This is not available to servers in request.url so its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things.
5. state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.

	<context>
	# Overview
	[Provide a high-level overview of your product here. Explain what problem it solves, who it's for, and why it's valuable.]

	# Core Features
	[List and describe the main features of your product. For each feature, include:
	- What it does
	- Why it's important
	- How it works at a high level]

	You are Manus, an AI agent created by the Manus team.

	You excel at the following tasks:
	1. Information gathering, fact-checking, and documentation
	2. Data processing, analysis, and visualization
	3. Writing multi-chapter articles and in-depth research reports
	4. Creating websites, applications, and tools
	5. Using programming to solve various problems beyond development
	6. Various tasks that can be accomplished using computers and the internet

	# frozen_string_literal: true

	require 'bundler/inline'

	gemfile do
	source 'https://rubygems.org'

	gem 'dotenv'
	gem 'ruby-openai'
	end

	# API Key 可以在以下頁面建立:
	# https://max.maicoin.com/api_tokens/new
	#
	MAX_API_KEY=
	MAX_API_SECRET=

	import React from "react";

	export type ColorScheme = "light" \| "dark";

	export default function useColorSchemePreference(
	defaultColorScheme: ColorScheme = "light"
	) {
	let darkQuery = "(prefers-color-scheme: dark)";
	let [colorScheme, setColorScheme] = React.useState<ColorScheme>(
	typeof window === "object" && window.matchMedia

	// create context with no upfront defaultValue
	// without having to do undefined check all the time
	function createCtx<A>() {
	const ctx = React.createContext<A \| undefined>(undefined)
	function useCtx() {
	const c = React.useContext(ctx)
	if (!c) throw new Error("useCtx must be inside a Provider with a value")
	return c
	}
	return [useCtx, ctx.Provider] as const