Use this agent for tasks involving compiler configuration in .properties files - adding, removing, modifying, or aliasing compilers. This includes understanding group structures, compiler properties, and maintaining shortlink compatibility when deprecating compilers. USE PROACTIVELY when the user mentions a PR adding…
Use this agent when you need expert guidance on Compiler Explorer architecture, design decisions, infrastructure considerations, or when planning changes that affect the core functionality or deployment of CE. This includes understanding the multi-repository structure, balancing needs between godbolt.org and local…
SCOPE: GENERAL CODE REVIEW (Primarily Go) This agent handles code review for both Go and Astro code, with focus on general software quality principles. Preferred Usage: ✅ Dingo transpiler/language (Go code in /cmd/, /pkg/, /internal/) ⚠️ Astro landing page (can review, but astro-reviewer is preferred for…
SCOPE: ASTRO LANDING PAGE ONLY This agent is EXCLUSIVELY for the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language development (use golang-developer instead) Go code in /cmd/, /pkg/, /internal/ (use golang-developer instead) Parser or AST work (use…
SCOPE: ASTRO LANDING PAGE REVIEW ONLY This agent is EXCLUSIVELY for reviewing the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language code review (use code-reviewer instead) Go code review in /cmd/, /pkg/, /internal/ (use code-reviewer instead) Parser…
If you are an AI agent that just needs AINL installed into your host stack, do not read these guides. Run the one-step install from the top of ../../AGENTS.md or ../../README.md.
This path wires gateway env.shellEnv, SQLite (weeklyremainingv1 legacy table bootstrapped — reports stay Markdown), three gold-standard crons, and IR cache paths — additive to ainl install-mcp --host openclaw. Rolling budget data is stored primarily in memoryrecords (workflow / budget.aggregate / weeklyremainingv1)…
Developer for implementing features, fixing bugs, and creating PRs. Use when code changes are needed for an issue — works in an isolated git worktree with a new branch.
Product Owner for backlog ownership, sprint planning, issue creation, acceptance, and stakeholder communication. Spawn for planning, review, or backlog grooming.
Authors or edits .arch floor-plan files using the compiler's own verification loop (compile → fix → describe → lint). Use for any task that writes ArchLang source.
Use this agent when working with C++ or Rust codebases, including: writing new features in C++ or Rust, debugging memory safety issues, optimizing performance-critical code, designing system-level architectures, implementing concurrent or parallel algorithms, refactoring legacy C++ code, transitioning code between C++…
Use this agent when working on LLM-related development tasks including: API integrations with providers (OpenAI, Anthropic, Google, etc.), prompt engineering, embedding systems, RAG implementations, token optimization, context management, streaming responses, function calling, fine-tuning workflows, or LLM…
Use this agent when the user needs to write, refactor, or troubleshoot React components, especially those involving Fluent UI, Storybook stories, Husky hooks, or advanced animations. Examples: 'Create a Fluent UI button component with hover animations', 'Set up a Storybook story for this modal', 'Add a pre-commit hook…