{"id":"65ae141c-8c16-43fd-8d2d-2edecb75d1ec","entityType":"agent","slug":"clawhub-athola-nm-archetypes-architecture-paradigm-client-serve","name":"architecture-paradigm-client-server","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve","canonicalPath":"/agent/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve","generatedAt":"2026-10-10T03:39:51.729Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":null},"description":"Applies client-server architecture for web/mobile apps Skill: architecture-paradigm-client-server Owner: athola Summary: Applies client-server architecture for web/mobile apps Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:04:55.307Z | user Release v1.9.19 v1.9.18 | 2026-08-15T21:28:54.277Z | user Release v1.9.18 v1.9.17 | 2026-07-30T05:28:44.790Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:45:52.574Z | user Release v1.9.16 v1.9.15 | 2026-07-04T21:20:05.","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.8K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-archetypes-architecture-paradigm-client-server","sourceUrl":"https://clawhub.ai/athola/nm-archetypes-architecture-paradigm-client-server","homepage":"https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-archetypes-architecture-paradigm-client-server","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":41,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Applies client-server architecture for web/mobile apps Skill: architecture-paradigm-client-server Owner: athola Summary: Applies client-server architecture for "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":null},"stars":null,"forks":null,"downloads":1790,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.8K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T01:57:56.183Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T01:57:56.184Z","lastCrawledAt":"2026-10-10T01:57:56.183Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T01:57:56.183Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:04:55.307Z","changelog":"Release v1.9.19","fileCount":3,"zipByteSize":3403},{"version":"1.9.18","createdAt":"2026-08-15T21:28:54.277Z","changelog":"Release v1.9.18","fileCount":3,"zipByteSize":3317},{"version":"1.9.17","createdAt":"2026-07-30T05:28:44.790Z","changelog":"Release v1.9.17","fileCount":3,"zipByteSize":3414},{"version":"1.9.16","createdAt":"2026-07-14T19:45:52.574Z","changelog":"Release v1.9.16","fileCount":3,"zipByteSize":3465},{"version":"1.9.15","createdAt":"2026-07-04T21:20:05.822Z","changelog":"Release v1.9.15","fileCount":3,"zipByteSize":3377},{"version":"1.9.14","createdAt":"2026-06-30T17:50:40.179Z","changelog":"Release v1.9.14","fileCount":3,"zipByteSize":3442},{"version":"1.9.13","createdAt":"2026-06-27T16:15:12.194Z","changelog":"Release v1.9.13","fileCount":3,"zipByteSize":3390},{"version":"1.9.12","createdAt":"2026-06-19T03:08:30.302Z","changelog":"Release v1.9.12","fileCount":3,"zipByteSize":3447}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-archetypes-architecture-paradigm-client-server","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T03:39:51.728Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-archetypes-architecture-paradigm-client-serve/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":null},"readme":"Skill: architecture-paradigm-client-server\n\nOwner: athola\n\nSummary: Applies client-server architecture for web/mobile apps\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:04:55.307Z | user\n\nRelease v1.9.19\n\nv1.9.18 | 2026-08-15T21:28:54.277Z | user\n\nRelease v1.9.18\n\nv1.9.17 | 2026-07-30T05:28:44.790Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:45:52.574Z | user\n\nRelease v1.9.16\n\nv1.9.15 | 2026-07-04T21:20:05.822Z | user\n\nRelease v1.9.15\n\nv1.9.14 | 2026-06-30T17:50:40.179Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:15:12.194Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:08:30.302Z | user\n\nRelease v1.9.12\n\nv1.8.6 | 2026-06-07T21:22:31.438Z | user\n\nRelease v1.9.11\n\nv1.8.5 | 2026-05-09T02:15:17.020Z | user\n\nRelease v1.9.5\n\nv1.8.4 | 2026-05-06T14:14:59.096Z | user\n\nRelease v1.9.4\n\nv1.8.3 | 2026-04-10T05:45:26.625Z | user\n\nRelease v1.8.3\n\nv1.8.2 | 2026-04-06T22:06:44.746Z | user\n\nRelease v1.8.2\n\nvv1.8.2 | 2026-04-06T16:19:12.703Z | user\n\nRelease v1.8.2\n\nArchive index:\n\nArchive v1.9.19: 3 files, 3403 bytes\n\nFiles: skill-card.md (1939b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.19:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787749495307\n}\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nApplies client-server architecture for web/mobile apps\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and architects use this skill to structure web, mobile, distributed, and offline-first systems around client-server or peer-to-peer responsibilities, API contracts, trust boundaries, and rollout planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Architecture guidance can be applied too broadly or substituted for project-specific review.\n\nMitigation: Review the generated architecture decisions, API contracts, trust boundaries, and rollout plans against the specific system before adoption.\n\nRisk: The artifact references an external Claude Code plugin for a fuller experience.\n\nMitigation: Install the external plugin only after independently trusting the publisher and reviewing that plugin's behavior.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server)\n- [Claude Night Market archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown prose with architecture steps, deliverables, risks, and component vocabulary]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [No code execution, persistence, credential access, or hidden data handling identified by server security evidence.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release evidence and target metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.18: 3 files, 3317 bytes\n\nFiles: skill-card.md (1773b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.18:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.18:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.18\",\n  \"publishedAt\": 1786829334277\n}\n\nFile v1.9.18:skill-card.md\n\n## Description:\n\nApplies client-server architecture for web/mobile apps.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to choose and document client-server, peer-to-peer, and offline-first architecture decisions for web and mobile systems, including trust boundaries, API contracts, version skew, connectivity, and rollout planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may appear for general architecture discussions, not only client-server design.\n\nMitigation: Confirm the task needs client-server, peer-to-peer, trust-boundary, API-versioning, or offline-sync guidance before applying it.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server)\n- [claude-night-market archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, configuration]\n\n**Output Format:** [Markdown guidance with architecture decision, API contract, compatibility, security, and rollout recommendations.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Non-executable guidance; no API keys, MCP tools, or shell commands are required.]\n\n## Skill Version(s):\n\n1.9.18 (source: ClawHub release evidence; artifact frontmatter lists 1.9.8)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.9.17: 3 files, 3414 bytes\n\nFiles: skill-card.md (2050b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.17:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.17\",\n  \"publishedAt\": 1785389324790\n}\n\nFile v1.9.17:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and software architects use this skill to reason about client-server, peer-to-peer, and offline-first application designs, including trust boundaries, API contracts, version skew, connectivity, and rollout coordination. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad architecture triggers may activate the skill in general design conversations. <br>\nMitigation: Use the guidance when client-server, peer-to-peer, offline-first sync, trust boundary, or API evolution concerns are relevant. <br>\nRisk: Architecture proposals may be incomplete or unsuitable for a specific system. <br>\nMitigation: Review the generated recommendations against project requirements, security constraints, and operational rollout plans before adoption. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server) <br>\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance with architecture deliverables and mitigation recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable behavior; produces architecture guidance for agent responses.] <br>\n\n## Skill Version(s): <br>\n1.9.17 (source: server release evidence; artifact frontmatter lists 1.9.8) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.16: 3 files, 3465 bytes\n\nFiles: skill-card.md (2157b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.16:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.16\",\n  \"publishedAt\": 1784058352574\n}\n\nFile v1.9.16:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to reason about client-server, peer-to-peer, and offline-first application architecture, including trust boundaries, API contracts, version negotiation, and rollout deliverables. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad architecture triggers may cause the skill to influence conversations where client-server guidance is not desired. <br>\nMitigation: Narrow or disable triggers when installing the skill in environments where architecture guidance should be opt-in. <br>\nRisk: Architecture recommendations can be incomplete or misleading if adopted without project-specific review. <br>\nMitigation: Review generated guidance against the actual system requirements, security model, and operational constraints before using it for implementation decisions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server) <br>\n- [Project homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance with architecture steps, deliverables, and risk mitigations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces advisory architecture content only; no tools, scripts, credentials, or external services are invoked by the artifact.] <br>\n\n## Skill Version(s): <br>\n1.9.16 (source: ClawHub release evidence; artifact frontmatter says 1.9.8) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.15: 3 files, 3377 bytes\n\nFiles: skill-card.md (1953b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.15:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.15:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.15\",\n  \"publishedAt\": 1783200005822\n}\n\nFile v1.9.15:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and architects use this skill to reason about client-server, peer-to-peer, and offline-first architecture choices, including trust boundaries, API contracts, version skew, connectivity, and rollout planning. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad architecture triggers may cause the skill to appear in general system design conversations. <br>\nMitigation: Treat its output as design advice and review recommendations before applying them to implementation plans. <br>\nRisk: The artifact links to an external Claude Code plugin that was outside the security review. <br>\nMitigation: Review and scan the linked external plugin separately before installing or executing it. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server) <br>\n- [Claude Night Market Archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance and structured architecture recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Guidance-only; no executable tools or credential access are declared.] <br>\n\n## Skill Version(s): <br>\n1.9.15 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.14: 3 files, 3442 bytes\n\nFiles: skill-card.md (2125b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.14:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.14\",\n  \"publishedAt\": 1782841840179\n}\n\nFile v1.9.14:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and architects use this skill to evaluate client-server, peer-to-peer, and offline-first design choices, then produce architecture decisions, API contracts, rollout plans, and risk mitigations for web or mobile systems. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad architecture triggers may cause the skill to activate during generic architecture discussions. <br>\nMitigation: Review activation behavior before installation and narrow triggers or invocation practices where unwanted context injection would be disruptive. <br>\nRisk: Architecture guidance can be incomplete or misapplied if adopted without project-specific review. <br>\nMitigation: Have qualified engineers review generated architecture decisions, API contracts, trust boundaries, and rollout plans before implementation. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server) <br>\n- [claude-night-market archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance with architecture deliverables and implementation recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable code, credential access, persistence, or external tool use is included in the skill artifact.] <br>\n\n## Skill Version(s): <br>\n1.9.14 (source: ClawHub release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.13: 3 files, 3390 bytes\n\nFiles: skill-card.md (2013b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.13:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.13\",\n  \"publishedAt\": 1782576912194\n}\n\nFile v1.9.13:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and architects use this skill to frame client-server, peer-to-peer, and offline-first system design decisions. It helps document trust boundaries, API contracts, compatibility planning, and rollout assumptions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Architecture guidance may appear for broad architecture prompts and may not fit the user's system constraints. <br>\nMitigation: Review the recommendations against the target system's requirements, trust boundaries, and operational constraints before adoption. <br>\nRisk: The artifact mentions a separate external Claude Code plugin that was not reviewed as part of this skill release. <br>\nMitigation: Treat installation of the external plugin as a separate trust decision and review it independently before use. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server) <br>\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown guidance and architecture recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable code or credential requirements were found in the reviewed artifact.] <br>\n\n## Skill Version(s): <br>\n1.9.13 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.9.12: 3 files, 3447 bytes\n\nFiles: skill-card.md (2151b), SKILL.md (3961b), _meta.json (169b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.9.12:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.12\",\n  \"publishedAt\": 1781838510302\n}\n\nFile v1.9.12:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and architects use this skill to evaluate client-server, peer-to-peer, and offline-first architecture choices, then document trust boundaries, API contracts, version-skew strategies, and rollout concerns for web or mobile systems. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad architecture trigger wording may activate the skill in conversations where client-server or peer-to-peer guidance is only partly relevant. <br>\nMitigation: Review the generated guidance against the actual system context and use it only when the task involves client-server, peer-to-peer, trust-boundary, or offline-first design. <br>\nRisk: Documentation-only architecture guidance can still introduce incorrect or misleading recommendations into ADRs, API contracts, or runbooks. <br>\nMitigation: Have a qualified reviewer check recommendations before using them for design decisions, implementation plans, or operational procedures. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-archetypes-architecture-paradigm-client-server) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Documentation-only architecture guidance with no executable code or tool calls.] <br>\n\n## Skill Version(s): <br>\n1.9.12 (source: server release evidence; artifact frontmatter lists 1.9.8) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.8.6: 3 files, 3451 bytes\n\nFiles: skill-card.md (2108b), SKILL.md (3961b), _meta.json (168b)\n\nFile v1.8.6:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n\n## Concrete Components\n\nThese vocabulary items name the concrete tools and abstractions\nthat show up when the paradigm is implemented. They are not\nrequired dependencies and they are not part of the skill's\n``tools:`` frontmatter (which is reserved for Claude Code tool\nrestrictions). Use this list to disambiguate during architecture\ndiscussions.\n\n- ``api-contract-generator`` -- produces machine-readable OpenAPI/RPC contracts the client and server share\n- ``networking-debugger`` -- captures request/response traces for diagnosing latency, retries, and timeout issues\n\nFile v1.8.6:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.8.6\",\n  \"publishedAt\": 1780867351438\n}\n\nFile v1.8.6:skill-card.md\n\n## Description: <br>\nApplies client-server architecture for web/mobile apps. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and architects use this skill to structure client-server or peer-to-peer architecture discussions, including trust boundaries, API contracts, version-skew handling, connectivity tradeoffs, and rollout deliverables. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad activation wording may cause the skill to appear in unrelated architecture conversations. <br>\nMitigation: Invoke it explicitly for client-server, peer-to-peer, distributed-systems, or trust-boundary work, and narrow or disable it if it interferes with unrelated tasks. <br>\nRisk: Architecture guidance can be incomplete or unsuitable for a specific production system. <br>\nMitigation: Review recommendations against project requirements, security controls, operational constraints, and compatibility needs before implementation. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-archetypes-architecture-paradigm-client-server) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Configuration] <br>\n**Output Format:** [Markdown guidance with architecture steps, deliverables, risks, and component vocabulary] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces advisory text for architecture planning; it does not execute commands or call external services.] <br>\n\n## Skill Version(s): <br>\n1.8.6 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.8.5: 3 files, 3376 bytes\n\nFiles: skill-card.md (2359b), SKILL.md (3586b), _meta.json (168b)\n\nFile v1.8.5:SKILL.md\n\n---\nname: architecture-paradigm-client-server\ndescription: |\n  Client-server architecture for web/mobile apps with centralized services and API design\nversion: 1.9.5\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often becomes duplicated and out-of-sync with the server. Share validation logic by packaging it in a common library or move the rules definitively to the server.\n- **Peer-to-Peer Data Conflicts**:\n  - **Mitigation**: In a peer-to-peer model, data conflicts are inevitable. Design formal conflict resolution strategies (e.g., CRDTs, last-write-wins) and consensus mechanisms from the beginning.\n## Troubleshooting\n\n### Common Issues\n\n**Command not found**\nEnsure all dependencies are installed and in PATH\n\n**Permission errors**\nCheck file permissions and run with appropriate privileges\n\n**Unexpected behavior**\nEnable verbose logging with `--verbose` flag\n\nFile v1.8.5:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.8.5\",\n  \"publishedAt\": 1778292917020\n}\n\nFile v1.8.5:skill-card.md\n\n## Description: <br>\nClient-server architecture for web/mobile apps with centralized services and API design <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to reason about client-server and peer-to-peer architecture, including API contracts, trust boundaries, version skew, and rollout planning. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate during broad architecture discussions where client-server guidance is only partially relevant. <br>\nMitigation: Use it for architecture, API design, versioning, or distributed-systems planning tasks, and review recommendations against the project context. <br>\nRisk: The linked external Claude Code plugin is separate from this documentation-only artifact and may include agents, hooks, or commands. <br>\nMitigation: Review and scan the external plugin separately before installing or enabling it. <br>\nRisk: Architecture guidance can be too generic for a specific system's security, latency, consistency, or operational requirements. <br>\nMitigation: Validate any proposed ADRs, API contracts, rollout plans, or peer-to-peer conflict strategies with the responsible engineering and security reviewers. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-archetypes-architecture-paradigm-client-server) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown prose, checklists, and architecture recommendations] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Documentation-only guidance; no code execution or credential access behavior is reported by server security evidence.] <br>\n\n## Skill Version(s): <br>\n1.8.5 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: architecture-paradigm-client-server Owner: athola Summary: Applies client-server architecture for web/mobile apps Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:04:55.307Z | user Release v1.9.19 v1.9.18 | 2026-08-15T21:28:54.277Z | user Release v1.9.18 v1.9.17 | 2026-07-30T05:28:44.790Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:45:52.574Z | user Release v1.9.16 v1.9.15 | 2026-07-04T21:20:05.","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: architecture-paradigm-client-server\ndescription: Applies client-server architecture for web/mobile apps\nversion: 1.9.8\ntriggers:\n  - architecture\n  - client-server\n  - peer-to-peer\n  - distributed-systems\n  - designing systems with centralized backend services\n  - trust boundaries\n  - or offline-first sync\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/archetypes\", \"emoji\": \"\\ud83c\\udfd7\\ufe0f\"}}\nsource: claude-night-market\nsource_plugin: archetypes\n---\n\n> **Night Market Skill** — ported from [claude-night-market/archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# The Client-Server and Peer-to-Peer Paradigms\n\n## When to Employ This Paradigm\n- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.\n- For systems exploring decentralized or \"offline-first\" capabilities that rely on peer-to-peer synchronization.\n- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.\n\n## Adoption Steps\n1. **Define Responsibilities**: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.\n2. **Document the Contracts**: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.\n3. **Plan for Version Skew**: Implement a strategy to manage different client and server versions, such as using feature flags, `Accept` headers for content negotiation, or semantic versioning for APIs.\n4. **Address Connectivity Issues**: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.\n5. **Secure All Communications**: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.\n\n## Key Deliverables\n- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.\n- Formal API or protocol specifications, along with a suite of compatibility tests.\n- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.\n\n## Risks & Mitigations\n- **\"Chatty\" Clients**:\n  - **Mitigation**: A client making too many small requests can lead to poor performance. Consolidate API calls using patterns like the Façade or Gateway, and implement caching strategies on the client or at the network edge.\n- **\"Thick\" Clients with Duplicated Logic**:\n  - **Mitigation**: When clients contain too much business logic, it often bec"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-archetypes-architecture-paradigm-client-server\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787749495307\n}"},{"path":"skill-card.md","content":"## Description:\n\nApplies client-server architecture for web/mobile apps\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and architects use this skill to structure web, mobile, distributed, and offline-first systems around client-server or peer-to-peer responsibilities, API contracts, trust boundaries, and rollout planning.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Architecture guidance can be applied too broadly or substituted for project-specific review.\n\nMitigation: Review the generated architecture decisions, API contracts, trust boundaries, and rollout plans against the specific system before adoption.\n\nRisk: The artifact references an external Claude Code plugin for a fuller experience.\n\nMitigation: Install the external plugin only after independently trusting the publisher and reviewing that plugin's behavior.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-archetypes-architecture-paradigm-client-server)\n- [Claude Night Market archetypes](https://github.com/athola/claude-night-market/tree/master/plugins/archetypes)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown prose with architecture steps, deliverables, risks, and component vocabulary]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [No code execution, persistence, credential access, or hidden data handling identified by server security evidence.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release evidence and target metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Applies client-server architecture for web/mobile apps Skill: architecture-paradigm-client-server Owner: athola Summary: Applies client-server architecture for web/mobile apps Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:04:55.307Z | user Release v1.9.19 v1.9.18 | 2026-08-15T21:28:54.277Z | user Release v1.9.18 v1.9.17 | 2026-07-30T05:28:44.790Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:45:52.574Z | user Release v1.9.16 v1.9.15 | 2026-07-04T21:20:05.","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1064,"uniquenessScore":54,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T01:57:56.184Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T03:39:51.729Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}