What problem does ArchSteer solve?

AI agents write code faster than any architect can review, document, or govern. Docs rot instantly, the real architecture is invisible, decisions are made silently, and intended architecture drifts. ArchSteer makes architecture continuously observable and governable.

How is ArchSteer different from a linter or a diagram tool?

Linters check single-language rules; diagram tools require manual upkeep. ArchSteer maintains one code-derived model that powers living docs, auto-drafted ADRs, conformance with a net-new ratchet, an evolution feed, and AI-agent steering — all from the same source of truth.

Do I have to set up rules before I get value?

No. The read-only X-ray runs with zero config: point it at any repo and instantly see the current architecture and how it changed. Declaring intent for governance is an incremental, opt-in upgrade.

How does ArchSteer steer AI coding agents?

It injects sharp, file-scoped guardrails into CLAUDE.md / AGENTS.md / .cursor/rules that point at the governing ADR, so agents build toward the target architecture instead of copying adjacent legacy code.

Home › Migrations

Migrations

Migrating raw SQL to the repository pattern

Raw SQL spread across controllers is hard to test and migrate. ArchSteer enforces that queries live in a repository layer and steers agents to the pattern.

Find the scattered SQL

ArchSteer maps every data-access point and flags raw SQL outside the repository layer.

Steer to the pattern

Agents are told to wrap queries in repositories under src/repositories and depend on them, never on a DB driver.

Converge with the ratchet

Net-new raw SQL is blocked while existing queries migrate, with progress tracked per rule.

Try it on your repo

Run `archsteer xray` on your repo to see this in under a minute, then declare intent when you're ready to govern.

▶ Live demo Talk to us

FAQ

Does this assume a specific ORM?

No — the repository layer can wrap raw SQL, an ORM, or a query builder; ArchSteer enforces the boundary.

Can controllers keep their queries temporarily?

Yes — existing ones are baselined; only new violations are blocked.

Migrating raw SQL to the repository pattern

Find the scattered SQL

Steer to the pattern

Converge with the ratchet

Try it on your repo

FAQ

Does this assume a specific ORM?

Can controllers keep their queries temporarily?

Related

Migrating from Express to Next.js route handlers

Migrating a monolith to a modular architecture

Migrating from JavaScript to TypeScript