architecture-paradigm-client-server
CommunityModel client-server responsibilities for robust systems.
Software Engineering#architecture#versioning#security#api design#distributed systems#client-server#peer-to-peer
Authorathola
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Designing traditional client-server or peer-to-peer systems requires careful consideration of responsibilities, trust boundaries, and API evolution. This skill helps you model these system responsibilities for robust and scalable applications.
Core Features & Use Cases
- Responsibility Definition: Decide what logic/data lives on clients vs. servers, minimizing duplication.
- Contract Documentation: Define APIs, schemas, auth flows, and capability negotiation.
- Versioning Planning: Use feature flags or semantic API versions to handle client/server skew.
- Connectivity Addressal: Plan for offline caching, sync protocols, or peer discovery.
- Use Case: Design a new mobile application backend, clearly defining which data and logic reside on the client versus the server, planning for API versioning, and securing communications with TLS and authentication.
Quick Start
Define the responsibilities for your client and server components, deciding which logic and data each will handle.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: architecture-paradigm-client-server Download link: https://github.com/athola/claudenomicon/archive/main.zip#architecture-paradigm-client-server Please download this .zip file, extract it, and install it in the .claude/skills/ directory.