# Designer Migrate Feature

> Port a feature from the original Blazor Elsa Studio (elsa-workflows/elsa-studio) into a module in elsa-foundation-designer. Use when migrating, porting, or rebuilding an existing Elsa Studio feature here — behaviour parity, not MudBlazor markup.

- Skill: `elsa-workflows/designer-migrate-feature` (Agent Skill)
- Install (CLI): `npx skillmds@latest add elsa-workflows/designer-migrate-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/elsa-workflows/designer-migrate-feature/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-migrate-feature

---


## User Input

```text
$ARGUMENTS
```

## Outline

1. Read `docs/skills/catalog.md#migrate-feature`.
2. Read `docs/migrating.md` (the Blazor → module playbook) and
   `docs/modules.md` (the destination module shape).
3. Locate the source feature in `elsa-workflows/elsa-studio` and **read the
   actual source** before porting — do not assume API names. Inventory its nav,
   pages/routes, `Elsa.Api.Client` calls, dialogs, localized strings, and
   authorization.
4. Map each piece onto this repo using the table in `docs/migrating.md`, then
   build it as a module via the 5 touchpoints in `docs/modules.md`.
5. Reuse generated DTOs (`lib/api/generated/elsa.d.ts`; `pnpm gen:api` if an
   endpoint is missing) and the `elsa` client; rebuild UI with shadcn/ui, not
   MudBlazor markup.

Produce the port plan + file list first. If the user hasn't approved
implementation, stop there. After approval, implement, verify behaviour parity
against the source, run the `designer-verify` routine, and flag anything
deferred (e.g. permission checks).