Circuit breaker visualization pattern
Skill kjuhwa/skills-hub/skills/design/circuit-breaker-visualization-pattern
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill circuit-breaker-visualization-patternAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Three-state circuit breaker visualization using color-coded state machine with real-time metrics dashboard
SKILL.md
1.8 KB, 295 tokens by cl100k_base, as published. Nobody here has run it
circuit-breaker-visualization-pattern
Circuit breaker UIs should render the three canonical states (CLOSED/OPEN/HALF_OPEN) as visually distinct zones with semantic colors: green for CLOSED (healthy passthrough), red for OPEN (tripped, rejecting), and amber/yellow for HALF_OPEN (probing recovery). Each state transition should animate along a directed graph showing the trip threshold (failure count ≥ N), the cooldown timer (OPEN → HALF_OPEN after T seconds), and the success probe path (HALF_OPEN → CLOSED after K consecutive successes, or back to OPEN on any failure). Place the current state badge prominently with a pulsing indicator when in HALF_OPEN to emphasize the fragile probing window.
The dashboard layout should split into three synchronized panels: (1) a live request stream showing individual call outcomes as green/red dots with fallback indicators, (2) a rolling failure-rate chart with the trip threshold line overlaid, and (3) a state-timeline Gantt-style bar showing how long the breaker spent in each state over the observation window. This triple view lets operators correlate cause (failure spikes), effect (state transitions), and impact (rejected traffic) at a glance.
For interactive simulators, expose sliders for failure threshold, cooldown duration, half-open probe count, and injected failure rate. Every parameter change should reset or smoothly update the visualization without losing the historical trace, so users can A/B tune thresholds against a reproducible load pattern.