Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for software architects

Architecture Conformance Check Agent

New code follows agreed module and layering rules

Quality controlIT and developmentProduct development
See how it worksGet access
Architecture Conformance Check Agent: what goes in, what the agent does and what you get

What it does

Architects set rules like 'the UI layer never calls the database' or 'billing is reached only through its API', but code drifts a little with every sprint. On each merge to main, this agent builds the dependency graph and compares it with the allowed dependencies and the last baseline. It reports only new violations, with file, line and the rule broken, and suggests a fix such as using an existing interface. Test code is excluded from layering rules by default. After the developer fixes it, the agent reruns the analysis. If the same violation keeps coming back, it proposes either a refactor ticket or a rule change for the architect to decide. The architect approves all exceptions and rule changes. It sends a weekly conformance summary. Edge case: a violation inside generated code is traced to the generator settings instead of the generated file.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Merge to main 2 USES A TOOL Build dependency graph 3 DOES Compare with rules and the last baseline 4 DOES Comment new violations with suggested fixes 5 USES A TOOL Rerun analysis after fixes 6 CHECKS THE RESULT Are new violations resolved? If not: propose a refactor ticket or rule change for thearchitect. Back to step 4. 7 YOU APPROVE Architect approves exceptions or rule changes 8 RESULT Weekly conformance summary
Read the steps as a list
  1. Merge to main
  2. Build dependency graph
  3. Compare with rules and the last baseline
  4. Comment new violations with suggested fixes
  5. Rerun analysis after fixes
  6. Are new violations resolved?If not: propose a refactor ticket or rule change for the architect. Back to step 4.
  7. Architect approves exceptions or rule changesThe agent waits here for your OK.
  8. Weekly conformance summary

How it decides

It compares the dependency graph with allowed dependencies and flags only new violations compared to the last baseline.

  • Only new violations are reported per merge
  • Tests are excluded from layering rules
  • Repeated violations prompt a rule discussion

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Rules file location
  • Blocking or advisory mode
  • Excluded paths
  • Summary schedule

What keeps you in control

It always asks you first

  • Exceptions
  • Rule changes

Hard limits

  • Never blocks merges unless configured to
  • Never edits code

It stops when

  • Done: no new violations
  • Stop: rule disputed, schedule architecture review

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensOn October 2 a merge added a direct import from the web module to the billing database package. The agent commented with the existing billing client to use, and the fix landed the same day. On October 9 the check failed again: another team had copied the same pattern. The agent proposed a shared helper and a refactor ticket. The architect approved the ticket and declined a rule exception.

More agents for software architects

Decisions · IT and development

Blockchain Use Case Feasibility Screen Agent

A fair, documented screen of a blockchain proposal with a clear recommendation

10 steps2 checks6 jobs
Decisions · Risk management

Static Analysis Findings Triage Agent

Turn a long findings list into confirmed fixes and justified suppressions

10 steps2 checks3 jobs
Coding · Quality control

Test Coverage Gap Closing Agent

Add tests to the riskiest untested code and prove that they catch real bugs

10 steps2 checks11 jobs
Decisions · IT and development

Model Selection Bake-Off Agent

Choose a model with evidence on quality, cost and speed for the real task

11 steps2 checks7 jobs