Skip to main content

guide

Entrypoint to the mahou plugin when unsure which skill fits. Give it your goal in plain words and it identifies the matching skill and activates it with your request as context.

Datos de origen

Repositorio
asermax/claude-plugins
Última actividad en el origen
5 de octubre de 2026 a las 02:44
Idioma detectado de SKILL.md
inglés
Estrellas
1
Forks
1

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
guide
description
Entrypoint to the mahou plugin when unsure which skill fits. Give it your goal in plain words and it identifies the matching skill and activates it with your request as context.
argument-hint
<goal in plain words>
Load mahou:basics first. Then read `.mahou/guide.md` if present. Routes a goal to the skill that handles it. Performs no work of its own. ## Procedure 1. Restate the user's goal in one line, in your own words. If the restatement is wrong, the user corrects it now rather than after a skill has run. 2. Look at every skill whose name starts with `mahou:` and match the goal against their descriptions. Skip the ones that are loaded by other skills rather than run (`basics`, `docs`, `design-tree`, `changeset`, `prototype`, `report`) and the ones marked typed-only; neither is a goal to route toward. - Exactly one fits. Say which one and why in one line, then run it with the original request as context. - Several could fit. List them with one line each and ask the user to choose. Never pick for them. - None fits. Say so plainly. If the gap is worth filling, mention mahou:learn. 3. Hand off. Do not do the work yourself, do not summarize what the skill is about to do, and do not run a second skill afterwards unless the user asks. ## The usual order When the goal is a piece of work rather than a single task, the skills form a line. mahou:explore builds the understanding, mahou:shape settles the decisions, mahou:design settles the system and mahou:program-design settles the program that implements it. A question that reading and asking cannot settle goes to mahou:spike, which answers it with throwaway code that never merges. A question about which parts a system has and how they connect, or how options for changing them compare, goes to mahou:architecture-exploration, which draws them on a canvas the user edits. mahou:test-design turns the settled design into the rows that prove it, and mahou:implement gets the code written by one subagent per repository, running mahou:agentic-review and mahou:validate on it as it lands; the code can also be written by hand or by another tool, in which case those two run when asked. Then mahou:code-blast-radius and mahou:human-review look at it, and mahou:write-documentation records what got built. Say where in that line the goal sits when it helps the user pick, and route to that one stage only.
Ver en GitHub