A single home for collected skills, MCP servers, plugins, CLI tools, references and specialised subagents — plus the house rules Claude works by. Grouped by what they do and tagged by how they're invoked, so you always know what's available and whether you need to ask for it.
Every resource is tagged with one of five invocation types. The short version: the green and blue ones I reach for on my own — you don't have to ask. The others you trigger explicitly.
I just use it. Always-connected MCP servers. I reach for them automatically when a task needs them — no need to name them.
Auto-triggers, nameable. Fires on its own when your task matches its description. Name it to force or disambiguate when several could apply.
You type it. A command like /caveman. Nothing happens until you invoke it.
Pulled on demand. Subagents I fetch from GitHub when a task needs a specialist. Not installed locally — kept lean.
Run manually. Command-line tools run via the shell — usually to build or mint new assets.
You just don't need to ask. Firecrawl and Magic are Auto MCP servers — always connected. The moment you ask me to search the web, scrape a page, or pull live data, I use Firecrawl on my own.
The same is mostly true for Skill resources: they auto-fire when your request matches what they do. You only need to name one when several overlapping design skills could apply and you want a specific look — e.g. use brutalist-skill or make it minimalist.
You do have to be explicit for two kinds only: Slash commands (you type /caveman) and CLI tools (run from the terminal). Everything else, assume I'll pick it up when it's relevant — and just tell me if you want a different one.