shesha-developer

Plugin shesha-developer from marketplace shesha-plugins in shesha-io/shesha-plugins. Commands read from the repo's manifest — 10 days ago.

Skills (26)

• shesha-public-portal

  Add a new public portal (public-facing / unauthenticated front-end app) to an existing Shesha framework project. Trigger for "add/create a public portal", "spin up a customer/vendor/citizen portal", "add another front-end", or "duplicate publicportal/adminportal" on a Shesha (Boxfusion, SmartGov) pr

• clean-form-config

  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 va

• create-crud-form

  Build canonical Shesha CRUD forms (table / create / details / row-template mini-card / list-of-cards) by COPYING one of six sample-* seed markups and swapping only the entity-specific bits. Use when the user asks for a "table", "list view", "details view", "create form", "edit form", "list of cards"

• create-custom-component

  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-

• create-custom-page

  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.

• create-mobile-app

  Scaffolds a new Shesha mobile application by running `npx sheshamobile-create`. Use when the user asks to create, scaffold, or generate a new mobile app using the Shesha mobile framework. Collects all required parameters via conversation with validation before running the command.

• create-module

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

• domain-model

  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, relat

• release-notes-generator

  Generates the release notes for an Azure DevOps product version in one run, for any project in the organisation. Works out the release's exact commits, pull requests and work items from the package feeds (falling back to pipeline builds, then git), combines them with the developers' vNext entries th

• shesha-app-layer

  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 th

• shesha-claude-designer

  THE ENTRY POINT for building a multi-screen Shesha app that has to look designed — with or without a design source. Use when the user hands over a design to MATCH (wireframe, HTML/JSX prototype, Figma kit, screenshots) or describes screens in prose (\"build a 3-page flight booking system\", \"a list

• shesha-configuration-items

  Creates and updates custom configuration items in Shesha framework .NET applications. Scaffolds domain entities extending ConfigurationItem, FluentMigrator joined-table migrations, managers, and import/export distribution classes in the Domain layer, plus IoC registration in the Application layer. U

• shesha-design-comprehension

  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. Also use to diagnose why an already-built form doesn't match its design. Turns a design source (readable HTML/JSX, a runnable

• 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

• shesha-domain-events

  Implements domain events and event handling in Shesha/.NET/ABP applications. Creates event data classes, event handlers, and integrates event triggering into services and entities. Covers custom domain events, predefined entity change events (EntityCreated, EntityUpdated, EntityDeleted), and backgro

• shesha-fluent-validators

  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

• shesha-form-edit

  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 b

• shesha-forms

  DEPRECATED — use shesha-developer:shesha-form-edit instead. Legacy wrapper around the Shesha MCP server's form tools, kept only for the MCP setup notes. Do NOT select this skill for creating, updating or modifying forms: the MCP path it wraps fails regularly ('dict' object has no attribute 'lower',

• shesha-get-started

  Gets a freshly downloaded Shesha starter project running locally for the first time, fully automatically and seamlessly. Expands the downloaded .zip if it has not been unzipped yet, detects the OS, reads the required .NET and Node versions from the project itself, and auto-installs any missing prere

• shesha-notifications

  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

• shesha-settings

  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-speci

• shesha-sms-gateway

  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 integrat

• shesha-specifications

  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 manage

• shesha-upgrade-reconciler

  Reconciles Shesha form configuration after a framework upgrade (e.g. 0.43 -> 0.46, or a patch release such as 0.46.0 -> 0.46.1) so forms look and behave as they did on the pre-upgrade reference site. Measures both sites page by page, applies version-aware, idempotent rule packs with mandatory backup

• test-entity-crud-api

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

• upgrade-to-0-46

  Upgrades a Shesha application from the 0.43 line or an internal 0.0.0-build line to Shesha 0.46.0. Covers NuGet and npm version pinning, the Configuration Items rewrite, Abp 10.3 and removed framework APIs, the Next 16 frontend stack, Configuration Studio, and the migration failures that only appear

Subagents (6)

• design-critic

  Fresh-context visual judge for a built Shesha form. Input via dispatch prompt — a screenshot of the rendered form, the layout-probe measurements, the placement-gate outcome, the resolved theme tokens, and any captured console warnings. Returns a STRICT JSON verdict — excellent | acceptable | generic

• fleet-transformer

  Applies one scripted Node.js transform across many Shesha forms with pilot-first discipline — writes the transform with embedded safety assertions, proves it on one pilot form, then rolls out and reports. Dispatch exactly ONE for any bulk mutation (never one agent per form).

• form-auditor

  Adversarially audits ONE Shesha form (a markup file, or live module+name) against the component index, the canon checklist, and a supplied audit spec. Read-only — returns a strict JSON verdict. Dispatch in parallel fan-outs (one per form) before bulk pushes and after fleet rollouts.

• form-author

  Drafts complete Shesha form markup from a canonical seed plus requirements. Dispatch one per form when authoring 2+ new forms in parallel (table / create / details / link-add dialog). Input via dispatch prompt — skill root path, seed file, target entity modelType, entity metadata (path or backend UR

• fullstack-prereq-checker

  Verifies backend prerequisites before Shesha form work — entity registered, exact modelType string, dynamic CRUD endpoints respond, reference lists exist with items, junction DTOs correctly typed, permissions allow the operations. Read-only diagnosis; returns a structured readiness verdict naming wh

• reconciliation-assessor

  Compares the same Shesha pages rendered on a reference environment (e.g. the pre-upgrade version) and on a target environment (e.g. the upgraded framework version) and reports what a user would see as worse on the target - missing or empty status tags, misaligned fields, phantom gaps, inner scrollba