https://harmstyler.me/tags/claude-code/Recent content in Claude Code on Tyler HarmsHugoen-ustyler.harms@gmail.com (Tyler Harms)tyler.harms@gmail.com (Tyler Harms)Thu, 22 Oct 2026 19:49:37 -0500https://harmstyler.me/posts/2026/claude-code-at-imports-vs-path-rules/Thu, 22 Oct 2026 19:42:52 -0500tyler.harms@gmail.com (Tyler Harms)https://harmstyler.me/posts/2026/claude-code-at-imports-vs-path-rules/<p>Claude Code gives you two different ways to pull extra context into a session automatically, and I assumed they composed. They don&rsquo;t.</p> <h2 id="the-setup">The Setup</h2> <ol> <li><strong><code>@</code> imports</strong> - reference a file with <code>@path/to/file.md</code>, and Claude auto-loads the full contents of that file into context.</li> <li><strong>Path-scoped rules</strong> - a rule file with frontmatter that targets specific paths, so the rule only applies when you&rsquo;re actually working in a file covered by that path.</li> </ol> <p>Combine the two and you&rsquo;d expect to get the best of both: a rule that&rsquo;s conditionally loaded based on where you&rsquo;re working, that also pulls in a full reference doc via <code>@</code> when it fires. That&rsquo;s exactly what I wanted - a way to attach a complete doc to context, but only when it&rsquo;s relevant.</p>