reactive-systems

Analyze system reactivity to distinguish local reactive programming from distributed reactive systems.

1|Updated Mar 14, 2026

Search Tags:#architecture #scalability #resilience #monolith #reactive #manifesto

Ready to run

npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill reactive-systems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reactive-systems
Source: https://github.com/agnaldo4j/kanban-vision-api-kt/tree/main/.claude/skills/reactive-systems
Command: npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill reactive-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and architects distinguish between reactive programming (local dataflow) and reactive systems (distributed architecture), preventing the misapplication of complex distributed patterns in modular monoliths.

Core Features & Use Cases

Architectural Assessment: Analyze whether a proposed change requires a simple local fix or a complex distributed system ADR.
Reactive Manifesto Alignment: Evaluate system components against the four traits: Responsive, Resilient, Elastic, and Message-Driven.
Use Case: Use this when deciding if a new event-driven requirement justifies moving from a modular monolith to a microservices architecture, or if it can be handled safely within the existing codebase.

Quick Start

Use the reactive-systems skill to evaluate the resilience and elasticity of the current database circuit breaker implementation.

Frequently Asked Questions about reactive-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I evaluate if a system change needs reactive architecture or a local fix?▼

Evaluate system reactivity by distinguishing local reactive programming from distributed reactive systems, enforcing ADRs for distributed changes while validating local non-blocking patterns to determine the correct architectural scope.

What is the difference between reactive programming and reactive systems?▼

Reactive programming handles local dataflow within a codebase, whereas reactive systems involve distributed architecture patterns, preventing the misapplication of complex distributed designs in modular monoliths.

When do I need an ADR for distributed system changes?▼

An ADR is required for distributed system changes when architectural decisions impact resilience or scalability, enforcing rigorous decision-making for reactive systems rather than local non-blocking code implementations.

How do I assess a system against the Reactive Manifesto traits?▼

Assess system components by evaluating them against the four Reactive Manifesto traits: Responsive, Resilient, Elastic, and Message-Driven, to determine if architectural changes align with reactive principles.

Does moving to microservices justify an event-driven requirement over a modular monolith?▼

Evaluate if an event-driven requirement justifies moving from a modular monolith to microservices by analyzing whether the change requires distributed reactive systems or can be handled safely within the existing local codebase.

Can I use this to evaluate circuit breaker resilience and scalability?▼

Evaluate the resilience and elasticity of a database circuit breaker implementation by validating local non-blocking patterns and assessing alignment with reactive system architectural traits.