aashari

Cursor AI Prompting Framework Usage Guide

This guide explains how to use the structured prompting files (core.md, refresh.md, request.md) to optimize your interactions with Cursor AI, leading to more reliable, safe, and effective coding assistance.

Core Components

1. core.md (Foundational Rules)
   • Purpose: Establishes the fundamental operating principles, safety protocols, tool usage guidelines, and validation requirements for Cursor AI. It ensures consistent and cautious behavior across all interactions.
   • Usage: This file's content should be persistently active during your Cursor sessions.

RuiAAPeres

import UIKit

// Based on https://www.stephanboyer.com/post/132/what-are-covariance-and-contravariance
// > Denotes "a subtype of"
// UIButton > UIView > UIResponder > NSObject
//
// e.g. `UIButton` is a subtype of `UIView`
//
// This means that any function that takes a `UIView`, can receive a `UIButton`:
//

chriseidhof

final class Loader: BindableObject {
    let didChange = PassthroughSubject<Data?, Never>()
    var task: URLSessionDataTask!
    var data: Data? = nil {
        didSet {
            didChange.send(data)
        }
    }
    
    init(_ url: URL) {

TheiOSDude

xcrun simctl uninstall booted com.theiosdude.bundleid

shaps80

import Foundation
import os.log

public protocol StateMachineDelegate: class {

    associatedtype StateType: Hashable

    /// Invoked before a transition is about to occur, allowing you to reject even a valid transition. Defaults to true
    ///
    /// - Parameters:

chriseidhof

//
//  main.swift
//  RoutingApproaches
//
//  Created by Chris Eidhof on 01.08.18.
//  Copyright © 2018 objc.io. All rights reserved.
//

import Foundation

raulraja

import arrow.Kind
import arrow.core.Option
import arrow.core.Try
import arrow.core.functor
import arrow.effects.IO
import arrow.effects.fix
import arrow.effects.functor
import arrow.typeclasses.Functor

/* algebras */

shaps80

//
//  AppDelegate.swift
//  Scheduling
//
//  Created by Shaps Benkau on 19/02/2018.
//  Copyright © 2018 152percent Ltd. All rights reserved.
//

import UIKit

chriseidhof

import Foundation

protocol Channel: IteratorProtocol {
    func send(_ value: Element?)
}

/// A blocking channel for sending values.
///
/// `send` and `receive` must run in separate separate execution contexts, otherwise you get a deadlock.
final class BlockingChannel<A>: Channel {

anandabits

// This example shows how closed protocols can be emulated in Swift today.
// The technique leverages Swift's support for public (but not open) classes.

// First, it's worth observing that there is an almost trivial technique that can be used when
// it is possible to specify a (possibly abstract) superclass for all conforiming types.
// Simply declare a public (not open) base class and a protocol with a Self inheritance constraint.
// Swift does not support open subclasses of a public superclass so no classes outside the module
// will be able to meet the self inheritance constraint.
public class FooBase {}
public protocol Foo where Self: FooBase {}