agent-conduct

Use generic or parameterized values instead of specific squad agent names like Flight or EECOM. When a test needs agent names, use obviously-fake fixtures such as "test-agent-1" or "TestBot" so product code stays independent of any particular squad.

The Product Isolation Rule states that tests, CI workflows, and product code must never depend on specific agent names from any squad. It ensures one squad's naming choices cannot break or constrain another squad's work.

Run the test suite for every file you touched and confirm the results pass. If CI was already failing, check that your changes are not contributing to the failure, and record lessons learned in your history.md file.

Duplicating rules across every agent charter creates drift and maintenance burden when rules change. Centralizing them in a single shared skill means the rules are loaded once and updated in one place for all agents.

The rule targets product code, tests, and CI configuration. Internal squad documentation or charter files referencing their own agent names are acceptable, since they do not affect the shipped product or shared pipelines.