Categories › Software Development › Code search, analysis, refactoring & languages
Practices for building software with coding agents, each with a test you check on your repo.
Remote server: your requests and data go to ase.academy. Claude Code: claude mcp add --transport http agentic-engineering-periodic-system https://ase.academy/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
overview — The Agentic Engineering Periodic System: what it is, how to read it (rows, columns, judging and reading rules), the roles. Call this first.find_elements — Find elements of the table by words in their name, problem or test, by role (dev, lead, plat, qa, ...), by group (security, verification, ..get_element — One element in full: problem, observable test with its clauses and evidence kinds, when it applies, when it adds work without helping, activrepository_checklist — What a repository can show for each test, clause by clause, what it cannot, and the judging rules. Use it to check the current project; readNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.