ipenywis

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

gaetschwartz

"explorer.fileNesting.enabled": true,
"explorer.fileNesting.expand": false,
"explorer.fileNesting.patterns": {
    "pubspec.yaml": ".flutter-plugins, .packages, .dart_tool, .flutter-plugins-dependencies, .metadata, .packages, pubspec.lock, build.yaml, analysis_options.yaml, all_lint_rules.yaml",
    ".gitignore": ".gitattributes, .gitmodules, .gitmessage, .mailmap, .git-blame*",
    "readme.*": "authors, backers.md, changelog*, citation*, code_of_conduct.md, codeowners, contributing.md, contributors, copying, credits, governance.md, history.md, license*, maintainers, readme*, security.md, sponsors.md",
    "*.dart": "$(capture).g.dart, $(capture).freezed.dart",
},

anoop4real

enum ResultStatus { success, error }

class Result<T, E> {
  final E error;
  final T value;
  final ResultStatus status;

  const Result.success(this.value)
      : status = ResultStatus.success,
        error = null;

jthodge

defaults write com.apple.Dock appswitcher-all-displays -bool true
killall Dock

TheHemantKaushik

///
/// Example GIF image:
/// https://ibb.co/mbqF72Q
///


import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() {

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit \
  -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

birdofpray70

Working Effectively with Legacy Code

Notes by Jeremy W. Sherman, October 2013, based on:

Feathers, Michael. Working Effectively with Legacy Code. Sixth printing, July 2007.

Foreword:

• Software systems degrade into a mess.
• Requirements ALWAYS change.
• Your goal as a software developer: Create designs that tolerate change.

mishagray

//
//  RealmSwift+Codable.swift
//
//  Created by Michael Gray on 8/16/17.
//

import Foundation
import RealmSwift

// swiftlint:disable line_length identifier_name

JadenGeller

class Number /* class cluser */ {
    class Int8: Number {
        var value: Swift.Int8
        init(_ value: Swift.Int8) { self.value = value }
    }
    class Int: Number {
        var value: Swift.Int
        init(_ value: Swift.Int) { self.value = value }
    }

perlguy99

Alamofire.request(urlString).responseJSON { response in
    guard case let .failure(error) = response.result else { return }

    if let error = error as? AFError {
        switch error {
        case .invalidURL(let url):
            print("Invalid URL: \(url) - \(error.localizedDescription)")
        case .parameterEncodingFailed(let reason):
            print("Parameter encoding failed: \(error.localizedDescription)")
            print("Failure Reason: \(reason)")