Contract-First
Coordinate frontend/backend work through one machine-checkable API contract, with no field drift.
- What
- Coordinate frontend/backend work through one machine-checkable API contract, with no field drift.
- Cost
- Free
- Needs
- Use "Contract-First" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a collaboration method for coordinating frontend/backend or service-to-service work through one authoritative, machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema). Consumers state what they need, providers implement that shape, and both sides verify against the same artifact before integration, so parallel work can evolve an API or event schema without field drift, mock/production shape mismatch, or one side silently redefining the interface. It governs how teams change a boundary: when field names, nullability, enums, or error shapes start drifting, when mocks no longer match production, or when a provider change can break consumers maintained by someone else. It complements API design guidance (what a good API looks like) and regression testing (guarding fixed bugs from returning). By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure method, nothing to install; do not add contract machinery to a tiny single-module boundary that one person changes alone, the overhead is not worth it there. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseWe automatically scan every listing and flag anything suspicious, but we can't review every line of community code. Here's how to check a build yourself before you install it.
Use "Contract-First" with your Muse. Prerequisites: the Muse app (mobile or web). Pure method skill, nothing to install. A frontend/backend boundary (or service-to-service interface) that two sides will evolve in parallel. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/contract-first/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "We are building [feature] with frontend and backend in parallel. Draft the contract first: [describe the operations, entities, and who consumes what]." 3. Ask Muse to produce the machine-checkable contract (OpenAPI, JSON Schema, or Protobuf), generate the consumer types from it, and define how each side verifies against it before integration. Tip: the contract is the boss, not a suggestion. When the provider wants a new field, the contract changes first, then both sides adapt. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any generated schema before adopting it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.