Familiarity / style Engine

Enforce house style with style_scan / style_enforce so agents match repo conventions.

What you will learn

• style_get
• style_enforce
• Reduce style thrash

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Familiarity Engine captures naming, file layout, and stylistic invariants. style_enforce blocks alien patterns that pass tests but fight the codebase.

How to call it

Call these MCP tools through your AGS / tower-gov host — style_scan, style_get, style_validate, style_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. style_scan
2. style_get
3. Align change
4. style_enforce

{
  /* Example MCP call — fill args from schema_get / docs */
  "tool": "style_scan",
  "arguments": {}
}

What success looks like

style_enforce ok

No foreign layout markers

Common failure modes

New folder taxonomy without style update

Copy-paste from another repo’s patterns

Validate skipped

Related reference

• Architecture