Infrastructurepattern
Skills as composable hubs over rules + integrations
Baking MCP wiring into every skill means every skill breaks when the MCP changes. Point skills at external rule files; one update fixes all of them.
What
A "skill" is a small Claude/Codex package that combines rules + contexts + MCPs + prompts, invoked by /skill-name. Architectural rule: point the skill at an external rule file rather than baking everything inside — when an MCP changes, only the rule needs updating, not every skill that uses it.
← All casesC-056