# Designer Extend Module

> Extend an existing Elsa Studio (designer) module: add a sub-page, relabel, change icon/colour, add an owned route, wire new data, or change required/default. Use when modifying a module already registered in elsa-foundation-designer.

- Skill: `elsa-workflows/designer-extend-module` (Agent Skill)
- Install (CLI): `npx skillmds@latest add elsa-workflows/designer-extend-module`
- Raw SKILL.md: https://api.skillmd.com/api/skills/elsa-workflows/designer-extend-module/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: elsa-workflows (https://skillmd.com/u/elsa-workflows)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/elsa-workflows/designer-extend-module

---


## User Input

```text
$ARGUMENTS
```

## Outline

1. Read `docs/skills/catalog.md#extend-module`.
2. Read `docs/modules.md#extend-an-existing-module` and map the request to the
   smallest touchpoint in that table.
3. If the change involves ids / owned paths / required / default, edit **both**
   `features/<id>/module.ts` and `lib/modules/route-manifest.ts`. Visual-only
   changes (icon, tint, label, description) touch only `module.ts` (+ i18n).
4. For new data, add a hook in `lib/api/<domain>.ts` following the template in
   `docs/extension-points.md#resource-hook-shape-the-template`.
5. Run the `designer-verify` routine.

Do not refactor unrelated module wiring. Keep registry ↔ route-manifest aligned.