[Extends backend-developer] Senior Kotlin specialist for JVM, Native, and KMP. Use for coroutines, Ktor, kotlinx.serialization, Kotlin Multiplatform shared logic, and high-performance concurrent systems.
ACSets (Attributed C-Sets): Algebraic databases as in-memory data structures. Category-theoretic formalism for relational databases generalizing graphs and data frames.
Idiomatic Go patterns for errors, interfaces, concurrency, and packages. Use when: - Writing or reviewing Go code - Designing interfaces or package structure - Implementing concurrency patterns - Handling errors and context propagation - Structuring Go projects Keywords: Go, golang, error wrapping, interface design, goroutine, channel, context, package design, dependency injection, race condition
You are a seasoned backend architect with deep expertise in designing scalable, resilient, and secure server-side systems. You are proficient in multiple programming languages (like Go, Python, Node.js), database technologies (SQL and NoSQL), and cloud-native architectures (microservices, serverless). You prioritize system performance, data integrity, and long-term maintainability.
Guide for creating Firestore services with async operations, transactions, and proper error handling following this project's patterns.
Verify Strong Parallelism Invariance (SPI) and GF(3) conservation for
Condensed ANIMA on quantum-classical and classical-quantum networks. All skill compositions materialized as s-expressions across the polyglot substrate.
Provider transparency, capability detection, context routing (partition/source/adapter)
Apply Ousterhout's software design principles: detect shallow modules, information leakage, and complexity red flags. Use when reviewing code, designing modules, refactoring, or discussing architecture.
Layer 5: Interaction Interleaving for Maximum Information Gain
Invariance principle for asymptotic stability
Categorical Rewriting: Triad 4 (World Transformation)
{{LANGUAGE_NAME}} best practices with modern frameworks, {{PRIMARY_DOMAIN}}, and performance optimization for 2025
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Safely replace legacy system piece by piece by building new implementation around it, routing traffic gradually, like a strangler fig tree
Clean Architecture, SOLID principles, and architectural decision guidance. Use when designing systems, evaluating architecture, making structural decisions, or reviewing for maintainability.
Apply universal naming principles: avoid Manager/Helper/Util, use intention-revealing names, domain language, verb+noun functions. Use when naming variables, functions, classes, reviewing names, or refactoring for clarity. Language-agnostic principles.
Multithreading and concurrency patterns for game servers including synchronization primitives
Evidence-first development with fail-closed behavior
CatSharp Scale Galois Connections between agent-o-rama and Plurigrid ACT via Mazzola's categorical music theory
Triages plan complexity to avoid heavyweight execution for trivial changes
Compose interfaces through embedding for flexible contracts
Document existing code patterns
