planning-phase
Standard Operating Procedure for /plan phase. Covers research depth, code reuse detection, design pattern selection, and architecture planning.
Standard Operating Procedure for /plan phase. Covers research depth, code reuse detection, design pattern selection, and architecture planning.
Map dependencies and coupling in legacy codebase to understand what breaks when you change something and identify refactoring risks
Topological soliton detection and agency bridge with anyonic fusion algebra for concept composition
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
Advanced Bevy ECS patterns including complex queries, system scheduling, change detection, entity relationships, and performance optimization. Use when working on advanced Bevy game architecture, optimizing ECS performance, or implementing complex game systems.
Best practices when developing in Ruby codebases
Master essential array techniques including two pointers, sliding window, and prefix sums for efficient problem solving with O(n) patterns.
FloxHub publication `bmorphism/effective-topos` - a comprehensive development
Service mesh technologies including Istio, Linkerd, Consul, and Envoy for microservices communication
Use when you see 'actor-isolated', 'Sendable', 'data race', '@MainActor' errors, or when asking 'why is this not thread safe', 'how do I use async/await', 'what is @MainActor for', 'my app is crashing with concurrency errors', 'how do I fix data races' - Swift 6 strict concurrency patterns with actor isolation and async/await
Aggregate boundaries, relationships, lifecycle hooks, value objects
Guide for building concurrent, fault-tolerant systems using OTP (GenServer, Supervisor, Task, Agent) and Elixir concurrency primitives
Mechanically verified proofs from Narya event logs. Verifies queue consistency, replay determinism, non-leakage, and GF(3) conservation. Use for proving system invariants, audit trails, or formal verification of event-sourced systems.
Core engineering principles for sustainable, maintainable code. No shortcuts, no hacks. Quality gates before completion.
Idiomatic Rust patterns for ownership, errors, traits, and configuration. Use when: - Writing or reviewing Rust code - Designing error handling with Result and thiserror - Implementing traits and composition patterns - Working with ownership and borrowing - Configuring Cargo features Keywords: Rust, ownership, borrowing, Result, thiserror, anyhow, trait, lifetimes, Cargo features, unsafe
ACSets (Attributed C-Sets) for categorical database design and DPO rewriting
Static type inference and validation for navigation paths
Breaks down architecture into actionable tasks by role
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Structured approach to handling production incidents, from detection through resolution and post-mortem analysis
Principal Solution Architect with 15+ years designing scalable distributed systems. Use when making technology choices, designing system architecture, selecting patterns (Saga, CQRS, Event Sourcing), creating ADRs, planning integrations, or addressing scalability concerns.
Automatically validates Cloudflare Durable Objects usage patterns, ensuring correct state management, hibernation, and strong consistency practices