architecture-paradigm-client-server

Model system responsibilities across clients, servers, and optional peer-to-peernodes for traditional distributed applications.Triggers: client-server, web architecture, mobile backend, API design, thin client,thick client, peer-to-peer, P2P, offline-first, synchronizationUse when: traditional web/mobile applications with centralized services,clear separation between client and server responsibilities neededDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.Consult this skill when designing client-server systems or API architectures.

// tip: Run this command in your terminal to install the skill