Align OpenAPI/OpenRPC contracts with Pydantic models and services.
npx skills add https://github.com/mesca/claude-plugins --skill spec-driven-mesca
Please help me install this Agent Skill. Skill: spec-driven Source: https://github.com/mesca/claude-plugins/tree/main/plugins/wf/skills/spec-driven Command: npx skills add https://github.com/mesca/claude-plugins --skill spec-driven-mesca
API projects often suffer from drift between contracts (OpenAPI/OpenRPC) and implementation, leading to broken integrations and flaky tests.
Define the OpenAPI/OpenRPC contracts in contracts/ and derive aligned models in models/ before implementing services.
High-intent search queries and answers about installing and using this skill.
Contracts-first API design prevents drift by defining authoritative OpenAPI or OpenRPC schemas in contracts/ first. You then derive models in models/ from these schemas, ensuring strict synchronization and parity between contract definitions and implementation layers.
The best way to align JSON-RPC contracts with implementation is to define authoritative OpenRPC schemas in contracts/ first. You then generate models in models/ and enforce strict synchronization between schema definitions, tests, and service code to maintain versioned parity.
Start a contracts-first API workflow by defining OpenAPI or OpenRPC schemas in a contracts/ directory. Once contracts are established, derive aligned Pydantic models in models/ before implementing services to ensure end-to-end data consistency.
Yes, contracts-first API design works with Pydantic models by enforcing models-first development. You align Pydantic models with OpenAPI or OpenRPC contract schemas before coding, ensuring data consistency and strict parity across contracts, models, tests, and implementation.
API implementation breaks during integration due to drift between contracts and implementation. Without contracts-first API design enforcing strict synchronization between OpenAPI schemas and data models, schema definitions and services lose parity, resulting in broken integrations and flaky tests.
mescaAudit codebases against development guidelines and plugin conventions.
wfukatsuGenerate ScalarDB service artifacts from design specifications.
diegusclValidate FastAPI route definitions and OpenAPI schema completeness.
seifsheikhelarabGenerate and validate OpenAPI 3.1 specifications from code and design artifacts.
