shesha-plugins

Use as the ENTRY POINT when the user wants a Shesha app/page/form to MATCH a design they have — a wireframe, an HTML/JSX prototype, a runnable app, a Figma-style kit, or a screenshot set — and asks to realise it in Shesha. Triggers like "build this design in Shesha", "make Requirements Studio look like the Claude design", "turn this prototype into Shesha forms", "implement this mockup across the app". It is the conductor across one or more screens, it comprehends the design into measured layout blueprints, then orchestrates shesha-design-comprehension, shesha-form-edit and shesha-design-system, and verifies the result by measurement. For a single isolated form with no design source, go straight to shesha-form-edit; to style an already-working form, go straight to shesha-design-system.

Use whenever a Shesha form or page needs to LOOK like a specific design or brand — "make it match the design", "apply our branding", "style this form", "it doesn't look good", "match Requirements Studio / the Figma / the Claude design", or any request for a polished, consistent visual result rather than just working fields. Maps design tokens (colour, type, spacing, radius, shadow, status lifecycle) onto Shesha's app-level Ant Design theme and per-component v7 style blocks. Themeable, ships the requirements-studio theme and accepts new brand token files. Pairs with shesha-form-edit (which builds structure) and is orchestrated by shesha-claude-designer. Do NOT use it to author structure/components, wire CRUD, or fix runtime errors — that is shesha-form-edit's job.

Creates and modifies domain entities, reference lists, and database migrations in Shesha framework .NET applications. IMPORTANT — This skill MUST be invoked BEFORE any manual exploration or planning when the task involves creating, modifying, or implementing domain entities, entity properties, relationships, reference lists, or database migrations. Use when the user asks to create, scaffold, implement, or update the domain layer, domain model, entities, reference lists, or migrations in a Shesha project. Also use when the user asks to create, add, update, or modify a database migration, FluentMigrator migration, schema change, or table alteration — even without mentioning entities. Also use when implementing features from a PRD, specification, or API design that require new or modified entities or database schema changes.

Use when a Shesha form must match a specific visual design and container/component placement keeps drifting — columns, nesting, tabs, or grouping landing in the wrong place versus the design. Also use to diagnose why an already-built form doesn't match its design. Turns a design source (readable HTML/JSX, a runnable prototype, or screenshots/PDF) into a measured, annotated layout blueprint, and verifies a built Shesha form against it by measurement. Invoked by shesha-claude-designer; pairs with shesha-form-edit (structure) and shesha-design-system (style).

Create and edit Shesha form configurations directly via the API. Authenticates as admin, fetches existing markup with Get/GetByName/GetJson, applies the user's requirements (adding, removing, modifying, or restructuring components — or building a brand-new form from scratch), validates against the bundled component-properties index and embedded-script rules, and pushes via Create / UpdateMarkup / ImportJson. Use when the user provides a form id (or module + name) and a set of requirements like "add a sector dropdown above the email field", "make the address tab conditional on AccountType=PBF", "wire the Save button to call /api/.../Submit", or "create a new branded login page using the auth-login pattern". Always prefer this skill over the Shesha MCP `create_form_configuration` tool — the MCP regularly fails with `'dict' object has no attribute 'lower'` and JSON-RPC `-32602` errors, and the direct-API path is more reliable.

Set up a Shesha-based project development environment aligned to Boxfusion development standards and best practices. Run this when a new Shesha project has just been created to verify and configure the dev environment.

Analyzes a Shesha form configuration JSON and removes dead/obsolete component properties, strips console.log calls from JS code strings, validates property value types, validates the shape of dropdown values items, detects scripts referencing component labels instead of propertyNames, runs layout validations (container dimension overflow, labelCol+wrapperCol span checks, device-specific style path conflicts), validates JavaScript syntax of embedded code strings, auto-fixes API calls missing try-catch by wrapping the function body in try/catch, and auto-fixes API calls in async-context properties that are missing async/await by adding the async keyword and awaiting calls. Falls back to manual review when function structure is ambiguous. Also detects API calls using .then() chaining and flags them for conversion to async/await + try-catch. Use when a form has been migrated, components have been refactored, or you want to clean up stale properties and debug statements.

Finds all Shesha form configurations that reference a specified API endpoint. Fetches every form from the Shesha backend, scans each form's raw markup string and structured component tree, and returns a table of matching forms. Triggers: "find this api", "where this api used", "form with this api".

Use this skill when creating new designer components in Shesha framework applications. This skill guides you through implementing custom form components with proper interfaces, settings forms, component definitions, and toolbox registration following Shesha best practices.

Starts the Shesha backend (.NET) on Mac using Docker SQL Server and dotnet run. Use when the user wants to run, start, or launch the Shesha backend API server locally.

Use this skill to add essential code quality analyzers to .NET projects, including AsyncFixer, IDisposableAnalyzers, and Microsoft.VisualStudio.Threading.Analyzers with best-practice configurations.

Analyzes Shesha BPMN workflow ProcessState XML logs to identify execution issues — failed gateways, suspended processes, missing flows, variable problems, and timing anomalies. Use when the user asks to interpret, debug, diagnose, or analyze workflow state XML files, BPMN execution logs, or ProcessState documents. Also use when the user provides a workflow instance ID and asks to check why it failed or what went wrong.

Use this skill when creating new designer components in Shesha framework applications. This skill guides you through implementing custom form components with proper interfaces, settings forms, component definitions, and toolbox registration following Shesha best practices.

Use this skill when creating new designer components in Shesha package projects (e.g., enterprise, reporting, workflow). This skill guides you through implementing custom form components with proper interfaces, settings forms, component definitions, and toolbox registration following Shesha package-level patterns.

Creates and scaffolds integration test projects for Shesha framework .NET applications. Sets up xUnit test infrastructure with NHibernate, database fixtures, test modules, and base classes. Detects whether Shesha.Testing NuGet package is available and adapts accordingly — using the package when present, or scaffolding local infrastructure when not. Use when the user asks to create, add, scaffold, implement, or set up integration tests, test projects, or test infrastructure for a Shesha project.

Creates properly structured Shesha framework module projects (Domain and Application) following existing codebase conventions.

Scaffolds and registers a new custom screen in a Shesha application. Creates the screen component in src/screens/, registers it in the screen registry, and wires up the Next.js route under /dynamic/ so it renders within the Shesha app layout. Supports both authenticated (default) and public screens.

Documents Shesha .shaconfig configuration packages by extracting their contents and generating a CSV inventory report. Use when asked to document, inventory, audit, list, or report on .shaconfig files, Shesha configuration packages, or Shesha configuration items (forms, permission definitions, reference lists, etc.).

Creates and modifies domain entities, reference lists, and database migrations in Shesha framework .NET applications. IMPORTANT — This skill MUST be invoked BEFORE any manual exploration or planning when the task involves creating, modifying, or implementing domain entities, entity properties, relationships, reference lists, or database migrations. Use when the user asks to create, scaffold, implement, or update the domain layer, domain model, entities, reference lists, or migrations in a Shesha project. Also use when the user asks to create, add, update, or modify a database migration, FluentMigrator migration, schema change, or table alteration — even without mentioning entities. Also use when implementing features from a PRD, specification, or API design that require new or modified entities or database schema changes.

Uses Playwright to set permissions on unsecured Shesha API endpoints via the permissioned-objects admin UI. Restricts write operations to app:Configurator. Use when the user wants to harden, secure, or lock down API endpoints, fix permissioned-objects, restrict access to admin-only services, or add authorization to unprotected app services in a Shesha application.

Links a Shesha backend module as a local project reference for debugging, or unlinks it back to NuGet. Reads Directory.Build.props to detect available modules, creates or updates a Debug solution file, toggles UseLocal* flags, and wraps PackageReference entries in MSBuild Choose/When/Otherwise conditional blocks. Use when asked to "link module for debug", "debug shesha locally", "add project reference for debugging", "switch to local project reference", or "unlink module".

Runs integration tests against a dedicated test database. Handles database provisioning, fast resets, config updates, and test execution. Use when the user wants to run integration tests, test against a real database, or mentions "run integration tests", "run tests", "integration test", or "test database".

Generates Shesha application layer code artifacts for .NET applications using ABP framework with NHibernate. Creates application services, DTOs, AutoMapper profiles, domain entities, modules, and scheduled jobs. IMPORTANT — This skill MUST be invoked BEFORE any manual exploration or planning when the task involves creating or modifying Shesha application services, DTOs, or AutoMapper profiles. Use when the user asks to create, scaffold, implement, or update the application layer, application services, entities, DTOs, jobs, or modules in a Shesha project. Also use when the user references a PRD, specification, or API design for backend implementation.

Creates and updates custom configuration items in Shesha framework .NET applications. Scaffolds domain entities extending ConfigurationItemBase, FluentMigrator joined-table migrations, managers, and import/export distribution classes in the Domain layer, plus IoC registration in the Application layer. Use when the user asks to create, scaffold, implement, or update configuration items, configuration types, or configurable settings in a Shesha project. Also use when implementing features from a PRD or specification that require new configuration item types with admin UI, versioning, or import/export support.

Generates Shesha document generation artifacts for producing PDFs or Word documents from Word templates via Aspose mail merge. Creates DTOs, item classes, AutoMapper profiles, application services, controllers, Word template guidance, and sample Word document templates with proper merge fields. Use when the user asks to create, scaffold, or implement document generation, mail merge, Word-to-PDF conversion, Word document generation, document processing, or Word document templates in a Shesha project.

Creates FluentValidation validators for Shesha entity CRUD endpoints. Generates validator classes, module IoC registration, and custom app service integration. Covers conditional validation rules, auto-population of related properties, and cross-property business logic. Use when the user asks to add validation, business rules, conditional required fields, auto-populate properties, or enforce constraints on entity create or update. Also use when the user wants to add logic that runs automatically on CRUD endpoints without modifying the entity or creating a custom app service. Trigger phrases include "validate", "required when", "auto-populate", "auto-fill", "set automatically", "conditional required", "business rule on save", "enforce constraint".

Creates and modifies Shesha UI form configurations using the Shesha MCP server. Use when the user asks to create, update, design, or modify configuration-based forms, form views, table views, or form layouts in a Shesha application.

Implements notifications in Shesha framework .NET applications. Creates notification data models, sender services, custom notification channels, and FluentMigrator migrations for notification types and templates. Also supports API-based creation of notification types and templates against a running backend (no migrations required). Supports Email, SMS, Push, and custom channels with the INotificationSender service. Use when the user asks to create, scaffold, implement, or add notifications, notification senders, notification channels, notification templates, or notification migrations in a Shesha project. Also use when the user asks to create notification types or templates via the API, or when implementing features from a PRD or specification that require sending Email, SMS, Push, or custom channel notifications.

Generates reference number logic for business entities in Shesha framework .NET applications. Creates sequential reference number generator usage code, format strings with date/sequence/financial-year placeholders, reset cycle configuration, and custom generator classes implementing IRefNumberGenerator. Use when the user asks to create, scaffold, implement, add, or generate reference numbers, sequence numbers, auto-numbering, order numbers, invoice numbers, case numbers, ticket numbers, or any auto-incrementing identifiers for business entities in a Shesha project.

Creates and updates application settings in Shesha framework .NET applications. Scaffolds setting accessor interfaces, setting name constants, compound setting classes, module registration with defaults, and editor form references. Supports simple (primitive), compound (custom class), and user-specific settings. Use when the user asks to create, scaffold, implement, add, or update application settings, setting accessors, setting classes, or module settings in a Shesha project. Also use when implementing features from a PRD or specification that require configurable application settings.

Creates new Shesha-specific skills by analyzing existing Shesha application code, documentation, and descriptions. Produces properly structured SKILL.md files with supporting reference files following best practices. Use when the user wants to create a new skill for Shesha code generation, workflow patterns, or any Shesha-specific domain by referencing existing implementations.

Creates and registers a custom ISmsGateway implementation in a Shesha .NET application. Scaffolds all required artifacts as a standalone integration project: gateway class, settings DTO, setting name constants, settings accessor interface, marker interface, module registration, and an xUnit integration test project. Use when the user asks to add, create, implement, register, or scaffold a new SMS gateway, SMS provider, SMS integration, or ISmsGateway in a Shesha project.

Creates specification classes for reusable, combinable entity filters in Shesha framework .NET applications. Scaffolds ShaSpecification<T> implementations, global specifications for security/access control, action-level specification attributes, parameterized specifications, and specification manager usage. Use when the user asks to create, scaffold, implement, add, or update specifications, entity filters, query filters, reusable filters, data access policies, global filters, or row-level security in a Shesha project. Also use when implementing features from a PRD or specification that require named, reusable filtering logic for entities.

Generates Shesha workflow artifacts for .NET applications using ABP framework with NHibernate. Creates workflow instances, definitions, managers, service tasks, extension methods, and FluentMigrator database migrations. Use when the user asks to create, scaffold, or update workflow-related classes, workflow steps, workflow conditions, or workflow database tables in a Shesha project.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Test all domain entity CRUD GET endpoints and optionally auto-fix failures

Upgrades Shesha framework dependencies in both frontend and backend projects to a specified BoxStack version. Handles monorepo and standard project structures. Use when user wants to upgrade, update, or migrate Shesha/BoxStack versions.

Scaffolds and registers a new custom screen in a Shesha application. Creates the screen component in src/screens/, registers it in the screen registry, and wires up the Next.js route under /dynamic/ so it renders within the Shesha app layout. Supports both authenticated (default) and public screens.