Episteme

Software engineering knowledge graph — patterns, laws, refactorings, smells. Activates on any code quality concern, design decision, architecture review, or engineering question — even when the user describes problems informally. Uses Episteme HTTP API (resolved via `epis api env`) via curl.

Use this agent when you need to evaluate a system architecture or technology decision — identifying scalability risks, structural smells, law violations (Conway, Amdahl, Gall), and design pattern misuse using the Episteme knowledge graph.

Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations.

Use this agent when the user faces an engineering decision, trade-off, or architecture question — choosing between patterns, resolving design conflicts, or applying refactorings. Grounds every recommendation in the Episteme knowledge graph.

Use this agent when you need to explore or research software engineering knowledge — finding design patterns, refactorings, laws, and code smells, or mapping relationships between concepts in the Episteme knowledge graph.