Your codebase has one architecture. Why does every developer's AI agent build its own private mental model of it?

The last few posts in this series have focused on what goes into an AI agent's context window: why structural code intelligence beats text search, how Code Mode collapses multi-step queries into a single efficient round-trip, and how plugins encode team knowledge as reusable primitives. But most AI coding tooling shares a quiet assumption: code intelligence is a per-developer artifact. Every engineer builds their own snapshot of the codebase and queries it alone.

That model made sense when AI coding tools were still finding their footing. For teams working on serious codebases, it's starting to show its limits.

Your AI coding assistant doesn't know your team's naming conventions, your deploy process, or that one module nobody should touch without running the integration tests. Here's how to teach it.

In our previous posts, we explored why context engineering is the most important skill for developers working with AI tools, and how Code Mode delivers structural code intelligence efficiently at the protocol level. But there's another side to context engineering that we haven't covered yet: the context you bring.

MCP servers give your AI agent better tools. But tools are only half the equation. The other half is knowledge: your team's conventions, your project's architecture, your workflows, your guardrails. The AI tools you use every day have a growing set of extension points designed to inject exactly this kind of knowledge: instructions, skills, rules, commands, and hooks.

In this post, we'll break down each of these primitives, show practical examples of each, and explain how plugins bundle them into shareable packages that give every engineer on your team the same supercharged AI experience.

What if, instead of giving your AI agent a menu of tools to pick from, you gave it an SDK and let it write code?

In our last post on context engineering, we talked about why every token in an LLM's context window needs to earn its spot. We explored how structural code intelligence beats text search, and how purpose-built MCP tools give AI agents a real understanding of your codebase instead of a pile of grep results.

But we glossed over something important: how those MCP tools are delivered to the agent matters just as much as what they do. And the standard approach to MCP tool calling has some fundamental scaling problems.

This post is about how we solved them. It's about Code Mode, a pattern that replaces traditional MCP tool calling with something far more powerful, and why we adopted it as the foundation of Constellation's MCP server.

Your AI coding assistant is only as good as the context you give it. Here's how to stop wasting tokens on grep and start engineering context like a pro.

Every developer who's spent time with an AI coding assistant has hit that wall. You're deep into a refactoring session with Claude Code, Cursor, GitHub Copilot, Windsurf, whatever your tool of choice, and it's humming along. Then suddenly it starts hallucinating function signatures, suggesting imports that don't exist, or confidently pointing you to code that was deleted three sprints ago.

The problem isn't the model. It's the context.

Context engineering is quickly becoming one of the most important skills for developers working with AI tools, and nowhere is it more critical than when navigating source code. In this post I'll break down what context engineering actually means here, why it matters so much for code, and how purpose-built tooling can transform your AI agent from a glorified grep machine into something that actually understands your codebase.

Welcome to the Constellation Blog.

This is where we'll share insights on AI coding agents, codebase analysis and understanding, and developer workflow optimization.