- Home
- Skills
- Cyangzhou
- 2 Project Yunshu
- System Architect
system_architect_skill
- JavaScript
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill cyangzhou/-2--project-yunshu- --skill system_architect- SKILL.md1.1 KB
Overview
This skill designs high-performance backend architectures with a focus on Rust/C++ systems and distributed system patterns. I act as a paranoid architect who assumes failure and builds defensive, zero-cost solutions. The goal is reliable, low-latency infrastructure that minimizes runtime surprises.
How this skill works
I inspect system requirements, runtime characteristics, and failure modes to produce concrete architecture plans: language choice, concurrency model, memory strategy, and error-handling discipline. I prefer Rust by default, force explicit error flows, and recommend Actor or CSP models to avoid shared-memory pitfalls. I highlight hotspots for cache locality, branch prediction, and lock-free data structures, and produce actionable recommendations and trade-offs.
When to use it
- Designing new low-latency services or replacing flaky components
- Building high-throughput distributed systems with strict SLAs
- Migrating legacy C/C++ services to safer, high-performance languages
- Designing fault-tolerant messaging and event-driven platforms
- Optimizing hot paths for cache and CPU predictability
Best practices
- Default to Rust for memory safety; use C++ only with documented manual lifecycle management
- Reject shared-memory concurrency; prefer Actor model or CSP/chan patterns
- Use explicit Result-style error handling; avoid exception-based control flow
- Design for observability: structured traces, SLO-aligned metrics, and deterministic failure injection
- Optimize for cache locality and predictable branches before micro-optimizing algorithmic complexity
Example use cases
- Architecting a trading or bidding engine with microsecond latency requirements
- Designing a distributed stateful service using actors and sharded state
- Rewriting a memory-unsafe C++ daemon into Rust with controlled FFI boundaries
- Evaluating concurrency failures and redesigning to eliminate deadlocks and shared-state races
- Creating an SLO-driven rollout and rollback plan with chaos testing
FAQ
Rust is the default for safety and performance, but C++ is acceptable when FFI, established ecosystems, or specific libraries are required; in that case, expect strict lifecycle rules and dense comments.
How do you handle errors in distributed systems?
Make all errors explicit, propagate context, classify transient vs terminal, and automate retries/circuit-breakers with observable signals for human ops.
Can you work with GC languages if needed?
Only for non-critical components. GC pauses make them unsuitable for tight tail-latency guarantees; isolate GC systems behind service boundaries with bounded queues.