agent-conduct

To enforce shared rules across multiple AI agents, load a centralized governance skill during charter initialization. This prevents hardcoded squad-specific names in tests and CI configurations by validating compliance at activation.

A single source of truth for agent governance eliminates duplicated rules across charters, reducing maintenance overhead and ensuring consistent quality checks that prevent cross-squad references in CI configs and product code.

Yes, frontmatter-driven governance validates agent charter compliance automatically. It enforces hard rules during charter loading and routine agent interactions, guarding tests, CI configurations, and product logic from squad-specific names.

The best way to standardize code and test quality rules is implementing a shared governance skill. It serves as a single source of truth loaded once, automatically enforcing hard rules to promote test safety and prevent cross-squad references.

To stop squad agents from writing squad-specific names into tests and product logic, load a centralized governance skill. It enforces shared hard rules during charter loading and routine interactions, validating compliance at activation.