Generate a complete fm-ux UI area scaffold from repository templates.
npx skills add https://github.com/zeitwert/fm-server --skill migrate-ui-area
Please help me install this Agent Skill. Skill: Migrate UI Area Source: https://github.com/zeitwert/fm-server/tree/main/.cursor/skills/migrate-ui-area Command: npx skills add https://github.com/zeitwert/fm-server --skill migrate-ui-area
This Skill enables teams to migrate or create a new aggregate UI area within the fm-ux application, ensuring a consistent architecture and scaffolding across modules.
Follow the template-driven approach: locate the existing Entity migration skeleton in .cursor/skills/migrate-ui-area, copy the templates for the new entity name, replace placeholders, and register the area in AppConfig.ts and i18n namespaces. Then implement the UI components (Area, Page, Preview, Forms) according to the copied layout.
High-intent search queries and answers about installing and using this skill.
Migrating a UI area in fm-ux uses a template-driven approach to standardize architecture by scaffolding types, schemas, API calls, and UI components. This ensures new domain modules align consistently with existing AppConfig, routing, and i18n configurations.
Template-driven UI area migration works by copying an existing entity migration skeleton, replacing placeholders with your new entity name, and wiring the generated routes and components into the fm-ux layer. This standardizes the architecture across all domain modules.
No, you do not need external dependencies to scaffold an fm-ux UI area. The migration process relies entirely on existing repository templates and standard TypeScript tooling to generate the complete area scaffold without external packages.
When bootstrapping a new fm-ux domain module, the included templates cover types, schemas, API, queries, UI components, routes, and i18n integration. These templates provide a standardized layout for implementing the Area, Page, Preview, and Forms.
To register a new UI area, you update AppConfig.ts with the new domain module and define its corresponding i18n namespaces. After copying the entity migration skeleton and replacing placeholders, you implement the UI components according to the copied layout.
The best way to standardize architecture when adding a new domain module in fm-ux is using a template-driven migration approach. This ensures every new entity area generates a complete scaffold that aligns with existing AppConfig, routing, and i18n patterns.
jamescha-earleyScaffold Drizzle ORM projects with typed schemas, relations, and migration tooling.
jmaglyTransform content to match a specified voice profile.
tx7doCreate and extend Vue3 + Vben scaffold modules with API, routing, and UI templates.
saavy1Scaffold Nexus Elysia API feature domains with typed Eden Treaty patterns.
