This skill should be used when the user asks "monolith vs microservices", how to "split into services", set "service boundaries", find the right "service granularity", design an "API gateway / BFF", do "service discovery" or add a "service mesh", or worries that services are "too chatty" / "too fine-grained". It gives the recipe for carving a system into services (or deciding not to) and wiring how they find and call each other. Use it whenever a design has more than one service — or someone is tempted to add more — even if the user doesn't say "microservices".
$npx -y skills add proyecto26/system-design-skills --skill service-decompositionInstalls into the current project.
Run `npx skills use "https://github.com/proyecto26/system-design-skills" --skill "proyecto26/system-design-skills/service-decomposition"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/proyecto26/system-design-skills" that are relevant to the current task. Run `npx skills add "https://github.com/proyecto26/system-design-skills"` and select the relevant skills, then follow their instructions.