Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/hyperlink-academy/leaflet --skill specEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Keep the three custom-domain surfaces in sync — profile domain settings, publication domain settings, and the leaflet share-menu domain picker. Use whenever you change how domains are listed, verified, assigned, unassigned, or deleted in any one of them, since each surface hand-rolls its own row UI over the same data and drifts silently.
Keep every render surface of a block in sync with the editor. Use whenever you create a new block type or change an existing block in components/Blocks/ — styling (margins, padding, font size/weight, line-height, color, alignment) or structure — so the published post and the email newsletter keep matching the editor, and copy/paste keeps working. Unless the user says otherwise, block work isn't done until all surfaces are checked.
Wire a setting in the General tab of publication settings end to end, so the change marks the form dirty, survives the Save button, and actually applies. Use whenever you add a new setting or change an existing one under dashboard/settings — the value passes through several hand-maintained field lists and silently drops out of any one you forget.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | spec |
| description | Draft design documents and specs with research-informed questioning |
| disable-model-invocation | true |
Use this skill when the user explicitly requests a spec, design document, or similar planning artifact. Do not auto-trigger for routine tasks.
When starting a spec:
Conduct open-ended questioning until the designer signals completion:
Research-informed questions: Before asking about an area, do just-in-time codebase research. Find relevant files, understand current patterns, identify constraints. Reference specific files and functions in questions when it adds clarity.
Adaptive scope: When the designer marks something as out of scope, update your mental model and don't revisit. However, flag when you believe there are gaps that could cause problems:
src/foo.ts:42 handles Z differently. Should we align or diverge?"Question style:
When the designer indicates readiness, produce the spec document.
Save to: /specs/YYYY-MM-DD-short-name.md
Title and status (draft | approved | implemented)
Goal: What this achieves and why. 1-3 sentences.
Design: The substance of what will be built/changed. For each significant component or concern:
Implementation: Ordered steps that an agent or developer can execute. Each step should:
Add other sections if the problem demands it.
file/path.ts:lineNumber or functionName in backticksUpdate status in the document as it progresses. Specs are point-in-time snapshots—do not update content after implementation begins except to change status.