Context

Every Mercury Mesh agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.

Patterns

Product Isolation Rule (hard rule)

Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular Mercury Mesh. "Our Mercury Mesh" must not impact "the Mercury Mesh." No hardcoded references to agent names (Flight, EECOM, FIDO, etc.) in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").

Peer Quality Check (hard rule)

Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.

Anti-Patterns

Context

Every Mercury Mesh agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.

Agent Conduct

Context

Patterns

Product Isolation Rule (hard rule)

Peer Quality Check (hard rule)

Anti-Patterns

Agent Conduct

Context

Patterns

Product Isolation Rule (hard rule)

Peer Quality Check (hard rule)

Anti-Patterns

Helm Chart Scaffolding

Python Observability

K8s Manifest Generator

Istio Traffic Management

Secrets Management

Gitops Workflow