This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
The SPARC Automated Development System (claude-sparc.sh) is a comprehensive, agentic workflow for automated software development using the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion). This system leverages Claude Code's built-in tools for parallel task orchestration, comprehensive research, and Test-Driven Development.
Updated with info from https://developer.apple.com/documentation/testing fetched via Firecrawl on June 7, 2025.
See also my blog: See also my blog post: https://steipete.me/posts/2025/migrating-700-tests-to-swift-testing
A hands-on, comprehensive guide for migrating from XCTest to Swift Testing and mastering the new framework. This playbook integrates the latest patterns and best practices from WWDC 2024 and official Apple documentation to make your tests more powerful, expressive, and maintainable.
This implementation plan details the creation of the Authorization & Access Service (AAS), a centralized abstraction layer for managing access to shared resources across the Mindbots ecosystem. The AAS incorporates patterns from the AI Delegation Service to support both human users and AI agents accessing shared resources.
The AI Delegation Service provides critical patterns that enhance our AAS design:
--continue after Directory mv move - Migration Guide and Internal Mechanics explanation )This guide explains how to preserve Claude Code's --continue functionality when moving project directories, along with the underlying mechanics.
Note: Claude Code currently lacks built-in directory migration features. Each directory maintains independent conversation sessions, and history doesn't automatically transfer when projects are moved.
When you move a project directory and want to preserve your conversation history:
| import asyncio | |
| import json | |
| import traceback | |
| import uuid | |
| from typing import ( | |
| Any, | |
| Awaitable, | |
| Callable, | |
| Coroutine, | |
| Literal, |
Disclaimer: Grok generated document.
The Socket API is a foundational technology for network and inter-process communication, enabling processes to exchange data across networks or within a single system. Initially developed as part of Berkeley Software Distribution (BSD) UNIX in the early 1980s, the Socket API, often called the Berkeley sockets API, has become a standard interface for networked applications across platforms like Linux, Windows, and macOS. This article provides a thorough exploration of the Socket API, covering its architecture, address families, socket types, protocols, implementation details, practical examples, and advanced concepts.
| #!/usr/bin/swift | |
| // Required parameters: | |
| // @raycast.schemaVersion 1 | |
| // @raycast.title New UUID v7 | |
| // @raycast.mode compact | |
| // | |
| // Optional parameters: | |
| // @raycast.icon 🆔 | |
| // @raycast.packageName UUID Utilities | |
| // @raycast.description Generate a draft-spec UUID version 7 and copy it to the clipboard. |
| import pickle | |
| from typing import Any, Set, Type, TypeVar | |
| from redis.asyncio import Redis | |
| from redis.typing import AbsExpiryT, ExpiryT, KeyT, ResponseT | |
| T = TypeVar("T") | |
| class TypedRedis(Redis): |
