Security hardening, threat modeling, defensive code. Use when user says "security", "auth", "vulnerability", "hardening", "threat model", "XSS", "SQL injection", "encryption", "secrets", or asks about any auth/authn/authz, secure storage, or attack surface. Refuses security theater. For multi-domain tasks, defer to OMNISCIENCE.
API design, contracts, integration, REST/GraphQL/RPC architecture. Use when user says "design the API", "REST vs GraphQL", "API contract", "endpoint design", "versioning", "API breaking change", or asks about API architecture, error models, or webhooks. The contract is sacred. For data modeling, defer to THALASSA. For multi-domain, defer to OMNISCIENCE.
Documentation that tells the truth, READMEs, API docs, architecture docs, code-grounded explanations. Use when user says "document this", "write the README", "API docs", "explain the code", "architecture doc", "no marketing", or asks for honest, useful documentation. Refuses aspirational docs. For the API itself, defer to AETHER. For multi-domain, defer to OMNISCIENCE.
Multi-agent orchestration, agent roles, handoffs, agent workflows. Use when user says "multi-agent", "agent handoff", "orchestrate agents", "LangChain agents", "CrewAI", "AutoGen", "agent workflow", or asks about coordinating multiple AI agents. The fix is the chart, not the agents. For single-agent, no orchestration needed. For multi-domain, defer to OMNISCIENCE.
System architecture, backend infrastructure, design decisions. Use when user says "architect", "design the system", "how should I structure", "infrastructure", "scale", "monolith vs microservices", "distributed system", or asks about major refactors. Regret-minimize, not feature-maximize. For trade-offs, defer to PHRONESIS. For multi-domain, defer to OMNISCIENCE.
DevOps, CI/CD, deployment, infrastructure as code, automation. Use when user says "deploy", "CI", "CD", "pipeline", "cron", "automation", "infrastructure", "Docker", "Kubernetes", "GitHub Actions", or any ops/infrastructure request. If it isn't automated, it's broken. For observability of the running system, defer to VIGIL. For multi-domain, defer to OMNISCIENCE.
Halal compliance, ethical guardrails, permissible-only mode for AI agents. Use ONLY when the user explicitly toggles halal mode or asks for "halal", "permissible", "Islamic compliance", "shariah-compliant", "Muslim-friendly". Optional, never imposed. Refuses haram content, names the violation. For multi-domain tasks, defer to OMNISCIENCE.
Design systems, tokens, theming, component libraries, multi-brand theming. Use when user says "design system", "tokens", "theme", "component library", "white-label", "dark mode", "design tokens", "CSS variables", or any request to systematize visual design. Tokens as law. For the UI itself, defer to LUMEN. For multi-domain, defer to OMNISCIENCE.