aithy: Skill for Claude Code

AxAgent Codegen Rules (@ax-llm/ax)

Use this skill to generate small, correct AxAgent code. Prefer modern factory-style APIs and copyable patterns. Do not write tutorial prose unless the user explicitly asks for explanation.

Your job is to choose the smallest correct AxAgent shape for the user's needs:

• If the user wants a normal tool-using assistant, keep the config minimal.
• If the user wants long-running code execution, use the ax-agent-rlm skill.
• If the user wants callbacks, logs, tracing, or usage data, use the ax-agent-observability skill.
• If the user wants dynamic memory retrieval or skill-guide loading, use the ax-agent-memory-skills skill.
• If the user wants tuning or eval with agent.optimize(...), use the ax-agent-optimize skill.
• If the user wants MCP transports, authentication, catalogs, subscriptions, tasks, Apps, or event-driven wake/resume, use the ax-mcp skill.

Use These Defaults

• Use agent(...), not new AxAgent(...).
• Prefer string signatures or f() signatures over hand-written signature objects.
• Put ai, judgeAI, and agentIdentity on the agent(...) config when you want instance defaults or child-agent metadata.
• Prefer fn(...) for host-side function definitions instead of hand-writing JSON Schema objects.
• Prefer namespaced functions such as utils.search(...) or kb.find(...).
• Pass child agents directly in functions: [...]. They land under their agentIdentity.namespace (or utils if unset), exactly like a fn() tool.
• If discovery is enabled, call discover(...) before using callables whose docs are not already in the prompt.
• Use explicit child agents in functions: [...] for specialist delegation; do not model that as recursive llmQuery(...).
• Add bubbleErrors only for fatal infrastructure errors that should abort .forward().

Decision Guide

Map user intent to agent shape before writing code:

• "Use tools and answer" -> plain agent(...) with local functions, no extra observability.
• "Need child agents with distinct responsibilities" -> add child agents to the parent's functions: [...] list and set each child's agentIdentity.namespace when you want a specific runtime call site such as team.writer(...).
• "Need tool discovery because names/schemas are not stable" -> enable discovery and generate discovery-first actor code.
• "Need certain errors to escape the agent loop" -> add bubbleErrors with error classes; those errors propagate through function handlers, actor code, and llmQuery(...) sub-queries to .forward().
• "Inspect large context with code", "RLM", or "llmQuery(...)" -> use ax-agent-rlm.
• "Need debugging, traces, progress updates, tool-call logs, chat logs, or usage" -> use ax-agent-observability.
• "Need memories, recall, dynamic skill guides, discover({ skills }), or loaded/used tracking" -> use ax-agent-memory-skills.