What Goes in Reference Files
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 3 · Section 3 of 5
What Goes in Reference Files
Think in categories:
Tools and services — what you use, how you access it, any quirks or conventions. Especially useful if you have CLIs, APIs, or MCP servers that Claude should prefer over alternatives.
Canonical URLs — every project, every platform, every relevant link. Claude will hallucinate URLs if you don’t give it the real ones. A LINKS.md eliminates that failure mode.
Platforms and accounts — where you’re active, what you publish there, the relevant handles or IDs. Useful when you’re asking Claude to draft content for specific channels.
Contacts — email addresses, communication preferences, priority order. Useful for anything that involves sending or responding.