Readable Troubleshooting Notes
I created my first three-file folder system for troubleshooting technical issues in IT.
My CLAUDE.md included my position as a level one technician. My CONTEXT.md explained how exactly I want the output to be formatted so I can read it quickly. My REFERENCES.md provided Claude with the MSP tools we have and use.
When I asked Claude to troubleshoot a printer issue as an example, the response was different because it gave me brief titles with bullet points underneath so I can read them quickly and execute as fast as possible.
Before, I had to explain the exact format I wanted every time. Now Claude already has that information.
Key takeaway: I shouldn't be explaining how I want my output to look.
14
5 comments
John Smith
4
Readable Troubleshooting Notes
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by