Diagnose distributed system bottlenecks and prescribe architecture patterns.
npx skills add https://github.com/Fearvox/data-algo-skill --skill data-algo-system
Please help me install this Agent Skill. Skill: data-algo-system Source: https://github.com/Fearvox/data-algo-skill/tree/main/data-algo-system Command: npx skills add https://github.com/Fearvox/data-algo-skill --skill data-algo-system
System design bottlenecks are diagnosed and architecture patterns are prescribed to guide infrastructure-level decisions, empowering teams to reason about scale, reliability, and performance using proven patterns.
Describe your system bottleneck and I will generate a phased design plan using the six pillar references.
High-intent search queries and answers about installing and using this skill.
Diagnosing distributed system bottlenecks involves evaluating constraints across load balancing, caching, and data partitioning. This skill applies a structured four-phase workflow to evaluate infrastructure and prescribe proven architecture patterns for scale.
Choosing a consensus and replication pattern requires referencing domain patterns to match reliability constraints. The skill implements a Diagnose, Recommend, Decide, and Ship workflow to evaluate options and archive architecture decisions per project.
Data partitioning is needed when single-node capacity limits distributed system throughput. By diagnosing bottlenecks, the skill prescribes partitioning strategies alongside load balancing and caching to guide infrastructure scaling decisions.
Applying rate limiting patterns involves referencing probabilistic structures and load balancing rules to protect services. The skill uses a reference-driven catalog to guide implementation across distributed services and auto-archives decisions.
Yes, it supports growing projects by maintaining per-project algorithm profiles. As constraints change, the skill auto-archives architecture decisions across its four-phase workflow, ensuring system design evolves logically.
Reference-driven system design patterns prescribe architecture for infrastructure problems like caching and consensus, but require accurately describing your bottleneck first. They guide implementation rather than automatically deploying distributed services.
OzeroHAXSelect system-level performance patterns for latency, throughput, or cost constraints.
first-flukeDesign scalable software architectures with system design patterns and modularity analysis.
zerAdaAnalyze system performance metrics and predict future capacity needs.
buitrankimlongImplement rate limiting for Supabase Edge Functions using RPC calls.
