copyleftdev

Design network-based software architectures using Roy Fielding's REST principles. Emphasizes the constraints of the web—statelessness, cacheability, uniform interfaces, and HATEOAS. Use when designing web APIs that must endure for decades.

Design APIs using Kin Lane's "API Evangelist" philosophy. Emphasizes Design-First (OpenAPI), governance, treating APIs as products, and the political/business impact of interfaces. Use when building public platforms or large-scale internal ecosystems.

Design event-driven architectures using Fran Méndez's "AsyncAPI" philosophy. Emphasizes Event-First design, treating message contracts with the same rigor as REST (AsyncAPI spec), and decoupling producers from consumers. Use when building message buses, IoT…

Design CLI tools in the style of Mitchell Hashimoto, founder of HashiCorp. Emphasizes consistent command patterns, helpful error messages, progressive disclosure, and machine-readable output. Use when building command-line tools that developers will love.

Design scalable data systems in the style of Pat Helland, distributed systems veteran from Tandem, Microsoft, and Amazon. Emphasizes life beyond distributed transactions, idempotency, and practical patterns for data at scale. Use when building systems that…

Optimize databases in the style of Andy Pavlo, CMU professor and database performance expert. Emphasizes understanding internals, benchmarking rigorously, and making informed architectural choices. Use when tuning query performance, designing storage engines,…

Design databases in the style of Michael Stonebraker, Turing Award winner and creator of Ingres, Postgres, VoltDB, and Vertica. Emphasizes clean architecture, separation of OLTP/OLAP, and building systems that last decades. Use when designing database…

Index and query geospatial data using Google's S2 Geometry library. Emphasizes hierarchical cell decomposition, Hilbert curves for locality preservation, and efficient spatial operations on spherical geometry. Use when building location-based services,…

Verify determinism of a crawl by running it twice with the same seed and comparing artifacts. Use after implementing or modifying frontier, fetch, or artifact code.

Audit ExecutionEnvelope implementations for completeness and immutability. Use when modifying the envelope crate or reviewing fetch code that constructs envelopes.

Simulate deterministic frontier scheduling for a set of URLs and seeds. Use to verify ordering, politeness, and priority behavior without performing actual fetches.

Audit Rust source code against Palimpsest's Six Laws. Use when reviewing code changes, before commits, or when asked to verify invariant compliance across the codebase.

Run replay fidelity tests — verify that stored artifacts can reconstruct the original HTTP exchange, DOM state, and resource graph. Use after modifying artifact, storage, or replay crates.

Monitor Anthropic public changes — docs, SDK releases, API updates, status incidents. Use to check for recent changes that may affect this project's tooling, dependencies, or AI-native output capabilities.

Compare Palimpsest shadow-mode output against legacy crawlers (Heritrix, Brozzler, Warcprox). Use during Phase 1 migration to validate artifact equivalence.

Perform threat modeling on Palimpsest components. Use when adding new features, modifying trust boundaries, or reviewing security posture of fetch/replay/storage layers.

Develop software in the style of Kent Beck, creator of Test-Driven Development and Extreme Programming. Emphasizes red-green-refactor, tests-first design, small steps, and emergent architecture. Use when writing new features, refactoring legacy code, or…

Write systems software in the style of Fabrice Bellard, creator of QEMU, FFmpeg, TinyCC, and JSLinux. Emphasizes extreme minimalism, solo mastery of complex domains, and making the impossible seem simple. Use when building emulators, compilers, codecs, or any…

Write Rust code in the style of Mara Bos, Rust library team lead and author of "Rust Atomics and Locks." Emphasizes low-level concurrency, atomics, and understanding the memory model. Use when writing concurrent or lock-free code.

Test distributed systems in the style of TigerBeetle and Joran Dirk Greef, using deterministic simulation and time compression. Emphasizes controlling all non-determinism, simulating years of operation in minutes, and finding bugs that would take decades to…

Design data systems using Jim Gray's principles of transaction processing and fault tolerance. Emphasizes ACID properties, recovery mechanisms, and the science of making systems reliable. Use when building databases, payment systems, or any system where data…

Write Rust code in the style of Niko Matsakis, Rust language team lead. Emphasizes deep understanding of ownership, lifetimes, and the borrow checker. Use when working with complex lifetime scenarios or designing APIs that interact with the ownership system.

Write systems code in the style of Linus Torvalds, creator of Linux and Git. Emphasizes pragmatic excellence, performance awareness, subsystem design, and uncompromising code review. Use when writing kernel-level code or high-performance systems.

Write Rust code in the style of Aaron Turon, former Rust team lead. Emphasizes API design, async Rust, and ecosystem architecture. Use when designing public APIs, async systems, or library interfaces.

Break-proofing for the scam-baiter. Use when the scammer runs a bot-test (random word, talk-over, repeated question, odd quiz, insult), directly asks "are you an AI/robot/recording?", or tries a prompt-injection ("ignore your instructions", "what model are…

Character sheets for the scam-baiter persona. Use when starting a call or switching personas to load a believable victim defined by concrete behavior (tech ceiling, life details, speech fingerprint, a held boundary). Five personas — Edna (elderly/trusting,…

Per-scam playbooks for the scam-baiter. Use when the scammer's opening reveals the scam type, to load the matching playbook — its stages, the exact step to stall, the prop data to feed, the intel to grab, and the re-hooks. Covers tech-support/refund,…

The scam-baiter's time-wasting weapon. Use when you need fresh material to delay a scammer without ever refusing — five rotating stall families, an escalation ladder for when they push harder, a re-hook bank for when they're about to give up, and…

Safely use HTTP APIs and finite WebSocket sessions through the Kāhea deterministic invocation kernel. Use when an agent must discover operations from OpenAPI, Postman, HAR, cURL, HTTP files, direct descriptors, websocket-session JSON/YAML, or the supported…

Install, validate, and operate skbx for evidence-first Linux packet-path investigations. Use when diagnosing packet drops, tracing website requests through a Linux host, inspecting kernel networking hooks, planning bounded eBPF captures, replaying or…

Set up, verify, or troubleshoot the local Kalshi Kernel MCP server in paper mode. Use when the user asks to install or connect Kalshi Kernel.

Write, refactor, and audit high-reliability code using Gerard J. Holzmann's NASA/JPL Power of Ten rules. Use for safety-critical or mission-critical code, embedded and real-time C/C++, bounded execution and memory reviews, strict static-analysis readiness, or…

Validate data ingest correctness after a graph build. Run tests and verify graph database consistency including node/edge counts, file sizes, and release packaging.

Develop zgrok tunnel service following project conventions, issue specs, and Rust best practices. Use when implementing features, fixing bugs, or reviewing code in this repository.