jediahkatz

name	description
capture-skill	Capture learnings, patterns, or workflows from the current conversation into a new or existing skill. Use when the user wants to save what was learned, discovered, or built during a conversation as a reusable skill for future sessions.

Capture Skill from Conversation

This skill helps you extract knowledge, patterns, and workflows from the current conversation and persist them as a reusable skill.

When to Use

Koshimizu-Takehito

import SwiftUI

// MARK: - ContentView

// https://x.com/okazz_/status/1870807939944243631
struct ContentView: View {
    @State private var progress: Double = 0

    var body: some View {
        MyGroup {

nilshoenson

#include <metal_stdlib>
#include <SwiftUI/SwiftUI_Metal.h>
using namespace metal;

// Create a horizontal bar
float bar(vector_float2 uv, float start, float height) {
	return step(uv.y, height + start) - step(uv.y, start);
}

// Create waves animation using GLSL

swiftui-lab

// Author: SwiftUI-Lab (www.swiftui-lab.com)
// Description: This code is part of the "Advanced SwiftUI Animations - Part 5"
// Article: https://swiftui-lab.com/swiftui-animations-part5/

import SwiftUI

struct ContentView: View {
    var body: some View {
        DigitalRain()
    }

mattyoung

import SwiftUI

public protocol ObservablePropertySource: ObservableObject {
    static var shared: Self { get }
}

@propertyWrapper
public struct ObservableProperty<S: ObservablePropertySource, T>: DynamicProperty {
    @ObservedObject private var source: S

DevAndArtist

import SwiftUI
import Combine

/// The idea is to use State to create a storage object which will be
/// cached and restored by the framework. Then during the update phase we
/// re-inject the object into a nested ObservableObject and subscribe to the
/// ObjectType’s objectWillChange to forward to the _MessageForwarder’s
/// objectWillChange which is already subscribed by the framework as it’s an
/// inner dynamic property of our custom PW which is also a dynamic property.
@propertyWrapper

krzysztofzablocki

#!/bin/zsh

cd "$(dirname "$0")/.."

if [[ -n "$CI" ]] || [[ $1 == "--fail-on-errors" ]] ; then
  FAIL_ON_ERRORS=true
  echo "Running in --fail-on-errors mode"
  ERROR_START=""
  COLOR_END=""
  INFO_START=""

DougGregor

Preventing Data Races in the Swift Concurrency Model

One of the goals of the concurrency effort is to prevent data races. This document describes the approach taken to preventing data races overall, by categorizing the sources of data races and describing how they are addressed with other proposals in the Swift Concurrency effort.

Data races

A data race occurs when two threads access the same memory concurrently and at least one of the accesses can change the value. Within the safe subset of Swift (e.g., ignoring the use of UnsafeMutablePointer and related types), the memory in question is always a stored property. There are several different categories of stored properties that need to be considered for data races:

• Global and static stored properties:

izakpavel

//
//  Lightnings fun
//
//  BEWARE highly unoptimized!
//
//  Created by Pavel Zak on 30/11/2020.
//

import SwiftUI

izakpavel

//
//  RotatorView.swift
//
//  Created by Pavel Zak on 16/11/2020.
//  original idea by: https://twitter.com/beesandbombs/status/1326312738033983489?s=20
//

import SwiftUI

func pow(_ x: Int, _ y: Int) -> Int {