libsync-architecture-contract

Document libsync backend design decisions, invariants, and weak points.

4|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/arthursoares/libsync --skill libsync-architecture-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: libsync-architecture-contract
Source: https://github.com/arthursoares/libsync/tree/main/.claude/skills/libsync-architecture-contract
Command: npx skills add https://github.com/arthursoares/libsync --skill libsync-architecture-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit serves as a reference guide for maintaining the architecture of the libsync backend. It helps prevent regressions in system design by providing explicit requirements and guidelines for changing backend services and integrating new features.

Core Features & Use Cases

  • Backend Changes Documentation: It states load-bearing design decisions, invariants that must not be broken, and known-weak points.
  • Code Verification: Verifies facts against the repo as of a specific date and highlights code verification procedures.
  • Usage: Ideal for anyone making backend modifications or troubleshooting, such as resolving deduplication issues, SDK integrations, or understanding system behavior post-change.

Quick Start

When preparing to modify backend services or SDK integrations in libsync, refer to the libsync-architecture-contract to understand invariants, decision rationales, and known weaknesses.

Frequently Asked Questions about libsync-architecture-contract

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

FAQPage Schema
How do I enforce architecture invariants when modifying backend services?

To enforce architecture invariants during backend service modifications, reference design decision documentation to identify load-bearing constraints, verify code changes against repository facts, and prevent system design regressions.

What are load-bearing design decisions in backend architecture?

Load-bearing design decisions in backend architecture are fundamental structural constraints and invariants that must not be broken, serving as explicit requirements to prevent system design regressions during service modifications and feature integrations.

How do I verify code changes against backend architecture rules?

Verify code changes against backend architecture rules by checking facts against the repository snapshot, highlighting code verification procedures to ensure modifications comply with stated design decisions and invariants.

Can I use architecture invariants for debugging backend deduplication issues?

Yes, you can use architecture invariants for debugging backend deduplication issues by referencing known weak points and design decision rationales to understand system behavior, guide troubleshooting, and maintain architectural integrity.

When do I need to check architecture contracts for SDK integrations?

Check architecture contracts for SDK integrations when preparing to modify backend services, ensuring new integrations respect existing invariants, understand system behavior post-change, and avoid breaking load-bearing design decisions.