empire-dev

These agents are adapted from upstream open-source projects under the MIT

Build production-ready LLM applications, advanced RAG systems, and intelligent agents. Implements vector search, multimodal AI, agent orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM features, chatbots, AI agents, or AI-powered applications.

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations. Use PROACTIVELY for smart contracts, Web3 apps, DeFi protocols, or blockchain infrastructure.

Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.

Find parallelism bugs that other agents miss — race conditions, deadlocks, atomicity violations, async/await correctness issues. Use when reviewing code that touches shared state, threads, async tasks, message passing, or database transactions.

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Reviews code through a functional-programming lens — purity, immutability, composition, algebraic data modeling, total functions. Language-agnostic; specializes in Haskell, Scala, OCaml, F#, Elm, Elixir, Clojure, plus FP-style TypeScript / JavaScript / Python / Rust / Kotlin / Swift. Use when reviewing FP-heavy code, refactoring imperative code toward FP, or evaluating effect / type discipline.

Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits, DevSecOps, or compliance implementation.

Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.

Reviews type design and type-system usage for encapsulation, invariant expression, and enforcement quality. Covers TypeScript, Rust, Haskell, Scala, OCaml. Handles advanced patterns: generics, conditional/mapped types, phantom types, branded types, GADTs, HKTs, traits. Use when introducing new types, reviewing PRs with type changes, or refactoring existing types. Pragmatic focus.

Diagnose requirements problems and guide discovery of real needs vs. stated wants. Use before any implementation to distinguish problem from solution, surface hidden constraints, and bound scope to a viable V1. Trigger phrases: "requirements analysis", "what should I build", "clarify requirements", "is this the right problem", "define scope", "what does the user need", "distill requirements", "/empire-dev:distill". Findings stay local — never post to GitHub.

Diagnose thinking failures and audit whether reasoning serves inquiry or defense. Use when reasoning feels stuck or circular, a conclusion feels defended rather than discovered, confidence is high but evidence is thin, analysis grows more elaborate without becoming more accurate, or same approach keeps failing. Trigger phrases: "check my thinking", "am I reasoning well", "why am I stuck", "reasoning feels circular", "probe my logic", "/empire-dev:probe". Two modes: self-monitoring (agent audits own process) and user coaching (diagnose user's thinking pattern with questions, not declarations).

Diagnose system design problems and guide architecture decisions — prevents over-engineering and under-engineering, surfaces missing integration points, and drives toward a walking skeleton before full build-out. Use when designing a system, when architecture feels either too complex or too vague, or when integration points are unclear. Trigger phrases: "system design", "how should I structure this", "too much abstraction", "under-engineered", "where do I start building", "design this system", "walking skeleton", "/empire-dev:shape". Findings stay local — never post to GitHub.

Transform overwhelming development tasks into manageable units — diagnoses why tasks fail to complete and applies decomposition patterns to create right-sized, independently deliverable work. Use when a task feels too big to estimate, when unsure where to start, when blocked by dependencies, or when scope keeps growing. Trigger phrases: "task too big", "can't estimate", "overwhelmed by scope", "where do I start", "break this down", "epic needs breakdown", "slice this up", "/empire-dev:slice".

Trigger when user says: "team review", "have specialists review", "review my changes", "re-review", "review again", "another pass", "ask the team", "specialist review", "/empire-dev:team-review", "have the team look at this", "get specialists to review", "run a team review", "do a specialist review". Spawns parallel specialist subagents to review diffs and consolidates findings. Never posts to GitHub.

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns for context. Use when making technology choices, evaluating architectural patterns, creating Architecture Decision Records, assessing technical debt, or comparing design alternatives. Trigger phrases: "architecture decision", "ADR", "which pattern should I use", "evaluate trade-offs", "technology choice", "design pattern selection", "weigh the options", "/empire-dev:weigh". Findings stay local — never post to GitHub.