elsa-workflows/elsa-foundation-studio

speckit-plan

Execute the implementation planning workflow using the plan template to generate design artifacts.

studio-architecture-tour

Give a concise architecture tour of elsa-foundation-studio (the ASP.NET Core/CShells host and React/Vite Elsa Studio). Use when a user asks what the repository is, how to orient, where to start, or how the shell, modules, routing, API, and authentication fit…

designer-create-module

Plan or scaffold a new Elsa Studio (designer) module: manifest, registry + route-manifest registration, routes, i18n, and the Settings toggle. Use when adding, porting, or scaffolding a studio module/feature in elsa-foundation-designer.

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.

designer-extension-points

Locate the right extension point in elsa-foundation-designer: where to plug in nav, routes, the module gate, API/data hooks, i18n, or shared UI. Use when a user asks 'where do I add/change X?' in the studio.

designer-glossary-lookup

Define an elsa-foundation-designer project term (module, manifest, registry, route manifest, owned path, tint, engine, resource hook, …). Use when a user asks what a studio-specific term means.

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.

designer-verify

Verify a change to elsa-foundation-designer is sound: typecheck, lint, build (which catches module registry/route-manifest drift), and a runtime sanity check for module work. Use before handing off or pushing studio changes.