agentsop-conventions-pinning

To make coder-agents follow your project's style guide, you write and pin a conventions file using a tool-agnostic SOP, ensuring reliable loading across repeated sessions. This prevents agents from silently ignoring your coding standards.

Multi-tool interoperability for conventions files is maintained by using a blueprint that defines what belongs in CONVENTIONS.md or .cursor rules, satisfying tool-specific loading requirements and conflict precedence without causing context bloat.

You load a conventions file across these tools by following a multi-tool SOP that covers explicit read-only attachment, Claude Code ancestor-walk auto-load, glob-scoped rules, and CrewAI backstory injection mechanics for consistent guidance.

Yes, writing a CONVENTIONS.md file works with Aider and Cline. A tool-agnostic SOP ensures these coder-agents load a consistent conventions source for guidance, satisfying their specific file persistence and loading requirements.

Your coder-agent ignores existing repository patterns because of unspecified conflict precedence. You need conflict resolution guidance that specifies how to handle precedence when pinned conventions contradict existing patterns, preventing arbitrary tool behavior.

To verify if a coder-agent applies a specific coding rule, you run a concrete A/B behavior test with controlled rule specificity. This evidence-based evolution loop checks whether the agent passes a targeted test, like using httpx instead of requests.