Using Linters To Direct Agents

A coding agent can receive precise architectural feedback from the same automated checks that enforce a team's conventions. This engineering guide from Factory proposes translating written rules into linters, programs that detect prohibited code patterns. For example, a rule can reject an import that crosses a forbidden module boundary and identify the location that needs correction.

Written guidance explains the reason for a convention; executable checks make violations visible during editing and before changes are accepted. Feeding those results back to the agent gives it a concrete correction target. The guide presents this as a way to reduce repeated human reminders, rather than reporting a controlled productivity measurement.