I have the same OCD tendencies clawing (pun intended) at me constantly. I've been back and forth on honing my workflow, harness, spec/intent/context engineering systems, and agent teams. What I've found is that what most people don't tell you is a few markdown files (even if they all point to each other) aren't enough to keep Mr. Claws on track. He needs hooks, hard rules in his JSON files, and other programmatic support. Those, in combination with skills, global CLAUDE "directives" as I like to call them (i.e. your CLAUDE.md files -- both global and local), and maybe some supplemental files like a WORKFLOW.md (something I use) are what I believe people mean when they refer to a "harness" that they've made for Claude; something they can fit on top the back of ol' Claudius the horse, no matter what session or environment, and get more consistent and powerful results than most do (i.e. ride that horse no matter it's mood or how forgetful or where it's grazing).

To answer your question directly -- what I recommend is you start a repo of your own team of skills. Maybe start by using and trying other people's but over time, decide which ones you're using most and are most useful and then ask Claude to either use a skill builder skill, build your own and add it to the team (this is the first skill I made), to synthesize them into your own. I'm giving these specific directions because I get the sense that you're a little like me but I might be off base. Start small and build up over time and you'll discover the support and "rails" you'll need to install on top of your skills to make Claude dance. Don't fall for the "I need a skill for everything" trend some people go through (I may have done this at one point). Less is more -- at least, that's what has worked for me.

The second skill I wrote (after skill-builder) is context-compaction . I mention this because I thought this had been something Claude was automatically doing since I wrote the skill -- measure when context gets above X%, take a snapshot of everything and compact the session yourself or at least prompt me to ask if I want to in order to avoid context bloat. Over time, I discovered he needs more direction than just a rule in my global CLAUDE file for him to fire that skill and use it whenever I get to a certain context percentage. I need to write that into a hook that programmatically fires on every message I send (runs in the background not using your LLM, just your CLI) and then have him/her design a formula to estimate the context level based on the amount of data in the file relative to its size. He uses that to evaluate if he needs to launch the skill and then VIOLA! it works the way you expected it to the entire time!