appget-contracts

Name: appget-contracts
Availability: InStock
Author: Devix Labs, Inc.

Define language-agnostic appget contracts for models, specs, REST, and gRPC.

1|Updated Feb 13, 2026

Search Tags:#api #rest #protobuf #contracts #schemas #grpc #appget

Ready to run

npx skills add https://github.com/devixlabs/appget --skill appget-contracts

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

Authoritative Schemas: Defines models.yaml and specs.yaml schemas for domain models, views, and business rules.
API Contract Definitions: Specifies REST and gRPC contract conventions, including resource naming, CRUD operations, and error handling.
Data Type Standardization: Details the representation of types like decimal and proto naming conventions.
Use Case: When introducing a new language implementation (e.g., Go or Python) to the appget platform, use this Skill to understand and adhere to the established contracts for models, rules, and APIs.

Quick Start

Consult the appget-contracts skill to understand the proto naming conventions for new language targets.

Frequently Asked Questions about appget-contracts

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

FAQPage Schema

How do I define cross-language API contracts for REST and gRPC?▼

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.

What schema format is used for appget domain models and business rules?▼

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.

How do I ensure consistent decimal representation across different language implementations?▼

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.

Can I use these API contracts to add a new language target like Go or Python to appget?▼

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.

What are the proto naming conventions for appget cross-language schemas?▼

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.