Loading...
Loading...
Found 83 Skills
Use when the user needs system design, architecture decision records, scalability analysis, trade-off evaluation, or non-functional requirements planning. Triggers: new system design, technology selection, scaling strategy, ADR creation, infrastructure topology, service boundary definition.
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
Build and operate Turborepo monorepos with deterministic task graphs, cache correctness, and CI scalability. Use for `turbo.json` design, task dependency modeling, outputs/inputs hashing, environment variable handling, remote cache rollout, and pipeline troubleshooting.
Use when designing APIs, Architecture, Security, or Scalability for Node, Python, Go, or Java backend systems.
Best practices and guidelines for building real-time applications with WebSocket communication
Agent skill for architecture - invoke with $agent-architecture
Expert performance testing and optimization specialist focused on measuring, analyzing, and improving system performance across all applications and infrastructure
Design system architecture, APIs, and component interfaces. Use for architectural decisions and system design.
System design and architecture expert for creating scalable distributed systems. Covers system design interviews, architecture patterns, and real-world case studies like Netflix, Twitter, Uber. Use when designing systems, writing architecture docs, or preparing for system design interviews.
Implement Customer.io load testing and scaling. Use when preparing for high traffic, load testing, or scaling integrations for enterprise workloads. Trigger with phrases like "customer.io load test", "customer.io scale", "customer.io high volume", "customer.io performance test".
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 must scale beyond single-node ACID transactions.