axir-language-backend

Implement and verify generated Ax language backends across Python, Java, C++, Go, and Rust.

2.9k|186|Updated Feb 23, 2023
One-click install
npx skills add https://github.com/ax-llm/ax --skill axir-language-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axir-language-backend
Source: https://github.com/ax-llm/ax/tree/main/tools/axir/skills/axir-language-backend
Command: npx skills add https://github.com/ax-llm/ax --skill axir-language-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides repo maintainers when adding or changing generated Ax language backends so the implementation stays consistent, verified, and aligned with the core compiler model.

Core Features & Use Cases

  • Backend Registration: Update target registration, package naming, capability manifests, and default verification coverage for new or changed language targets.
  • Code Generation: Adjust target emitters, templates, package metadata, README text, examples, and runtime support for generated Ax libraries.
  • Verification and Conformance: Keep smoke checks, manifest guards, conformance suites, and generated-output audits aligned with the claimed backend surface.
  • Use Case: A maintainer adds a new Go or Rust backend, then uses this Skill to wire the target into compilation, generate idiomatic package output, and confirm the published library behaves correctly.

Quick Start

Use this skill to update the generated Ax backend for the target language, then verify registration, templates, examples, and conformance coverage against the repo's compiler and release rules.

Frequently Asked Questions about axir-language-backend

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

FAQPage Schema
How do I add a new generated backend for a target language like Rust or Go?

To add a generated backend, you update target registration, package naming, and code generation templates. You then wire the target into compilation, generate idiomatic package output, and verify runtime support and conformance coverage against the core compiler model.

What does backend conformance coverage require for generated Ax libraries?

Backend conformance coverage requires explicit verification of compiler seams, truthful package manifests, deterministic output, and idiomatic generated APIs. It ensures the published library behaves correctly by running smoke checks, manifest guards, conformance suites, and generated-output audits.

Can I generate code for multiple language targets including Python, Java, and C++?

Yes, you can generate code for Python, Java, C++, Go, Rust, and future targets. The process adjusts target emitters, templates, package metadata, README text, and examples to produce verified and idiomatic generated libraries for each specific language target.

Why do generated backend manifests require explicit verification checks?

Manifest verification ensures the claimed backend surface is truthful and aligned with the repository's release rules. It prevents placeholder public methods and confirms that generated output, capability manifests, and compiler seams maintain deterministic behavior and conformance.

What is the best way to verify target registration and code generation for Ax backends?

The best way to verify target registration and code generation is by applying smoke checks and conformance suites. This validates that package metadata, examples, runtime support, and generated APIs remain consistent with the core compiler model and contain no placeholder methods.