Agent Claude Code
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.
Agent Claude Code
Investigates bugs using scientific method, manages debug sessions with persistent state. Spawned by /ariadna:debug or diagnose-issues workflow.
Agent Claude Code
Executes a plan by implementing tasks with atomic commits.
Agent Claude Code
Creates executable PLAN.md files from phase goals. Absorbs research and self-checking. Spawned by /ariadna:plan-phase orchestrator.
Agent Claude Code
Creates ROADMAP.md, STATE.md, and requirement traceability from project context and domain research. Absorbs research and synthesis. Spawned by /ariadna:new-project orchestrator.
Agent Claude Code
Verifies phase goal achievement through goal-backward analysis. Absorbs integration checking — cross-phase wiring, E2E flows, and machine checks via ariadna-tools. Creates VERIFICATION.md.
Skill Claude CodeCodex
Ruby on Rails backend conventions — models, controllers, jobs, API design. Use when implementing Rails backend code, creating models, writing controllers, or designing APIs.
Skill Claude CodeCodex
Ruby on Rails frontend conventions — Hotwire, Turbo, Stimulus, views, components, assets. Use when implementing frontend features, building views, or working with JavaScript/CSS.
Skill Claude CodeCodex
Ruby on Rails performance conventions — N+1 prevention, caching, database tuning, benchmarking. Use when optimizing queries, adding caching, or profiling performance.
Skill Claude CodeCodex
Ruby on Rails security conventions — authentication, authorization, OWASP protections, CSRF, input validation. Use when implementing auth, handling sensitive data, or reviewing security.
Skill Claude CodeCodex
Ruby on Rails testing conventions — Minitest strategy, fixtures, system tests. Use when writing tests, setting up test data, or running test suites.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: