I built Frontmatter because I felt the pain of needing to understand the different configurations across tools when working on AI enablement and developing the right tools and harnesses for coding agents. A big part of the work is figuring out where the tools overlap and where they don't.

Every tool has its own configuration surface, its own terminology, and its own docs. What hooks does each tool support? What are they called? What frontmatter applies for a skill, and how does it affect the way the skill actually triggers and runs? Understanding this matters if you're setting up workflows meant to hold up when the tooling underneath changes.

As model capabilities change, the workflows and harnesses we build around them need to become more tool-agnostic. If you want to swap tools or evaluate a new one, you need to know where you're working in the overlap zones and where you're not. My bet is this problem isn't unique to me, and so I invite you to use Frontmatter.

Please send feedback, bugs, missing info, or suggestions for improvements to wire@frontmatter.news.