القائمة
Resilience4j circuit breaker, retry, rate limiter, and bulkhead patterns with testing strategies. Use when implementing fault tolerance between services.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate an Architecture Decision Record for a technical decision
Adversarial critic workflow for the limited-stock booking system. Use when the user asks AI to attack a design or implementation for Redis outage, oversell, undersell, duplicate booking/payment, retry storm, fallback collapse, correctness gaps, or operational blind spots.
Skeptical first-principles design review skill. Use when the user asks whether a design, architecture, product plan, API, data model, workflow, or system design truly satisfies the real requirements. Reviews from fundamentals: decompose claims into requirements, assumptions, constraints, evidence, invariants, trade-offs, failure modes, and simpler alternatives. Inspired by first-principles reasoning and Cartesian doubt, but does not impersonate any real person.
Validate current project phase deliverables against PRD checklist
Design partner mode for system design practice. Activated when the user wants to design a new system (chat, notification, news feed, URL shortener, etc.). Sets up topic directory, uses the project mock-interview document, loads the matching problem from sysdesign-question-bank, marks the topic as active in .omx/state/, and conducts a back-and-forth Clarifying → High Level → Drill Down conversation, updating <topic>/System-Design-Document/mock-interview.md immediately as each decision lands. Uses Alex Xu Vol.1's canned numbers as the starting point (book-first), user adjusts. NOT an interview — the user drives, this skill is a design collaborator with a calculator (back-of- envelope, latency estimation via auto-injected sysdesign-frameworks) and a reference book (sysdesign-question-bank).
Promote a filled mock-interview.md into a formal Software Design Document (sdd.md) following the IEEE 1016 / Atlassian / Google design-doc style. Activated when the user says they are ready to write the SDD. Reads the topic's mock-interview.md AND the topic's conversation log files (which capture the back-and-forth detail not preserved in the structured mock-interview), then asks the user the SDD-specific questions that mock-interview doesn't cover (Constraints, ADRs, Risk Register, Rollout, Testing strategy). Writes sdd.md incrementally as decisions land.
| name | resilience |
| description | Resilience4j circuit breaker, retry, rate limiter, and bulkhead patterns with testing strategies. Use when implementing fault tolerance between services. |
| triggers | ["circuit breaker","resilience4j","retry pattern","fallback method","rate limiter","bulkhead pattern","서킷 브레이커","장애 대응"] |
| Pattern | Config Key | Default Value | Purpose |
|---|---|---|---|
| Circuit Breaker | failureRateThreshold | 50 (%) | Open circuit when 50% of calls fail |
| Circuit Breaker | slidingWindowSize | 10 | Number of calls to evaluate |
| Circuit Breaker | waitDurationInOpenState | 10s | Time before half-open |
| Retry | maxAttempts | 3 | Total attempts including initial |
| Retry | waitDuration | 500ms | Wait between retries |
| Rate Limiter | limitForPeriod | 100 | Max calls per period |
| Bulkhead | maxConcurrentCalls | 25 | Max concurrent calls |
| Service Call | Pattern(s) | Fallback |
|---|---|---|
| Payment -> External gateway | CircuitBreaker + Retry | Queue for later processing |
| Order -> Payment service | CircuitBreaker | Accept order, process payment async |
| Order -> Product service | CircuitBreaker + Retry | Return cached stock status |
| API Gateway -> any service | Rate Limiter + Bulkhead | 429 Too Many Requests |
@CircuitBreaker(name = "...", fallbackMethod = "...") on service methods@Retry(name = "...") on idempotent operations onlyThrowable parameterapplication.yml under resilience4j.*/actuator/circuitbreakers)