Define language-agnostic appget contracts for models, specs, REST, and gRPC.
npx skills add https://github.com/devixlabs/appget --skill appget-contracts
Please help me install this Agent Skill. Skill: appget-contracts Source: https://github.com/devixlabs/appget/tree/main/.claude/skills/appget-contracts Command: npx skills add https://github.com/devixlabs/appget --skill appget-contracts
This Skill provides the authoritative definitions for appget's cross-language contracts, ensuring consistency across all language implementations and simplifying the addition of new language targets.
models.yaml and specs.yaml schemas for domain models, views, and business rules.decimal and proto naming conventions.Consult the appget-contracts skill to understand the proto naming conventions for new language targets.
High-intent search queries and answers about installing and using this skill.
Cross-language API contracts for REST and gRPC are defined by establishing language-agnostic intermediate representations and authoritative schemas that enforce identical outputs across all language implementations. This includes standardizing resource naming, CRUD operations, and proto naming conventions.
Domain models, views, and business rules for appget are defined using the authoritative `models.yaml` and `specs.yaml` schema formats. These YAML schemas provide the language-agnostic intermediate representations required for consistent cross-language implementation.
Consistent decimal representation across different language implementations is ensured by adhering to standardized data type definitions and intermediate representations. These contracts specify exact proto naming conventions and decimal formats that all current and future language targets must follow.
Yes, these API contracts are designed specifically to simplify adding new language targets like Go or Python to appget. By consulting the established Java-implemented contracts for models, rules, and APIs, new implementations can ensure identical outputs and semantic consistency.
Proto naming conventions for appget cross-language schemas are defined within the authoritative API contract specifications. These conventions dictate how intermediate representations are named and structured, ensuring that all gRPC contracts and data types remain consistent across different language targets.
musujDefine project terminology, entities, relationships, and data structures.
333-333-333Define protobuf contracts and generate Go gRPC stubs for microservices.
bitsoexOrchestrate CustomRPC service migration to gRPC with RFC-33 error handling.
davidrrowleyDesign and validate REST, GraphQL, and gRPC API contracts with OpenAPI schemas.