Use when writing C++ code with `axllm` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add ax-llm/ax --skill ax-cpp-signature --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ax Cpp Signature?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ax-llm-ax-cpp-signature-ax)More formats (shields.io, HTML) on the badges page.
---
name: "ax-cpp-signature"
description: "Use when writing C++ code with `axllm` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes."
version: "24.0.16"
---
# Ax Signatures For C++
This skill helps an agent write C++ code with the generated Ax package `axllm`. Use the generated package API, examples, and manifests; do not import TypeScript-only APIs unless you are editing the TypeScript package.
## When To Use
- Declare input and output contracts with native generated-package APIs.
- Generate JSON-schema-compatible shapes for outputs, tools, prompts, and validation.
- Keep Standard Schema and TypeScript-only helper libraries out of generated-language code.
## Package Facts
- Language: C++.
- Package: `axllm`.
- Package API docs: `API.md` and `axir-api.json`.
- Capability manifest: `axir-capabilities.json`.
- Runnable examples: `examples/`.
- Real network support: yes.
- Scripted no-key transport support: yes.
- Runtime profiles: `javascript-quickjs`, `python-pyodide`.
## Core Pattern
```cpp
#include "axllm/axllm.hpp"
auto sig = axllm::s("question:string -> answer:string");
auto schema = axllm::to_json_schema(axllm::Core::get(sig, "outputs"));
```
## More Patterns
### Simple string contract
Use the string form when field names and types are enough.
```cpp
auto program = axllm::ax("questionText:string -> answerText:string");
```
### Bounded class output
A class field constrains the model to a known label set.
```cpp
auto router = axllm::ax(
"messageText:string -> routeClass:class \"support, sales, engineering\"");
```
### Native constraints
C++ exposes the generated record surface for constrained fields.
```cpp
auto party_type = axllm::Core::record_new(
"FieldType",
axllm::object({
{"name", "number"},
{"minimum", 1},
{"maximum", 12},
}));
```
### Validate and render
Validate the native record, then render its output fields as JSON schema.
```cpp
axllm::Core::validate_signature(signature);
auto schema = axllm::to_json_schema(
axllm::Core::get(signature, "outputs"),
"outputs");
```
### Reuse the signature
Pass the native signature record directly into AxGen.
```cpp
axllm::AxGen program = axllm::ax(signature);
auto output = program.forward(client, inputs);
```
Start from the complete programs under `examples/`, then browse the larger gallery at https://axllm.dev/cpp/subsystems/s/.
## Relevant API Surface
- Signatures: `axllm::s`, `axllm::FieldType`, `axllm::AxSignature`
- Tools: `axllm::Tool`, `axllm::Tool`
## Guardrails
- Start from package examples for exact native syntax before inventing a new call shape.
- Use `provider-api` examples only when the user explicitly has provider credentials available.
- Use `no-key` examples for deterministic local checks and provider request mapping.
- Treat AxIR as the source of generated package truth: if package docs disagree with source code, update the compiler and regenerate packages.
- Do not copy repo-maintainer skills from `tools/*/skills/` into user packages.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!