Decides which Claude Code extension type to use for a given capability — skill, hook, MCP server, subagent, or slash command — and designs the plugin.json manifest around that decision. Use when designing a plugin, planning plugin structure, choosing between skill vs hook vs mcp, setting up plugin composition, laying out plugin components, or refactoring an existing plugin whose decomposition feel
El comando exacto puede variar según el repositorio. Consulta el README en GitHub.
Para el autor de la skill
Pega en el README de tu repo
Muestra que tu skill está catalogada en Skillteca, genera backlink y tráfico rastreable.
[](https://www.skillteca.com.br/skills/plugin-architecture?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Recibe nuevas skills de Design e Frontend todos los lunes
Un email corto con solo las skills nuevas de Design e Frontend. 4 minutos de lectura, sin spam, te das de baja con un clic.
Confirmas tu email en el primer envío. Sin spam. Te das de baja con un clic.
Plugin Architecture
The decomposition matters more than any single component. A plugin that puts the wrong capability in the wrong component fails silently — the skill never triggers, the hook blocks everything, the MCP tool is unreachable. This skill is the first decision you make, before writing any content.
When to use this skill
You have a plugin idea and don't know how to split it across components
You're about to write a SKILL.md but wonder if it should be a hook ins
[Description truncada. Veja o README completo no GitHub.]
