concave-parity

Document and remove Concave parity bandaids in Convex runtime contracts.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill concave-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: concave-parity
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/concave-parity
Command: npx skills add https://github.com/udecode/kitcn --skill concave-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parity management between Convex runtime contracts and Concave parity introduces drift and bandaid scars; this Skill provides a structured approach to document, track, and responsibly remove temporary fixes as upstream parity matures.

Core Features & Use Cases

  • Defines explicit rules and removal criteria for Concave-related parity bandaids.
  • Documents where and how to apply shims and backstops to keep Convex contracts in sync with Concave parity.
  • Useful for dev tooling and governance of runtime contract behavior in kitcn projects.

Quick Start

Review the Concave parity guidelines and apply the documented bandaid removal criteria to your repo changes.

Frequently Asked Questions about concave-parity

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

FAQPage Schema
How do I prevent drift between Convex runtime contracts and Concave parity?

To prevent parity drift, you align Convex runtime contracts with Concave parity by enforcing explicit bandaid catalogs, removal triggers, and diagnostic notes. This structured approach tracks temporary shims until upstream parity matures.

What is a bandaid in runtime contract development?

A bandaid in runtime contract development is a temporary shim or backstop applied to maintain Convex and Concave parity. It requires explicit cataloging, diagnostic notes, and clear removal triggers to prevent long-term scarring.

How do I manage and remove temporary shims in kitcn projects?

You manage shims in kitcn projects by applying documented bandaid removal criteria to repository changes. This involves maintaining explicit catalogs and diagnostic notes to guide responsible removal when upstream parity improves.

When should I document parity gaps during scenario scaffolding?

You should document parity gaps during scenario scaffolding whenever temporary shims or backstops are introduced to align Convex and Concave. Documenting these gaps ensures the team tracks bandaids and knows when to remove them.

Does this approach require dependencies to enforce Concave parity?

No, enforcing Concave parity requires no external dependencies. It relies on structured guidelines applied during development and tooling reviews to document, implement, and remove bandaids within kitcn projects.