clean-form-configAnalyzes a Shesha 0.46 form configuration JSON and cleans it. Removes dead/obsolete component properties using a valid-property index generated from the 0.46 component KB (never touching keys a migrator still reads on components stored below the current version), strips console.log calls, validates
create-crud-formBuild canonical Shesha 0.46 CRUD forms (table / create / details / row-template mini-card / list-of-cards) by COPYING one of six sample-* seed markups (stored at the current 0.46 component versions) and swapping only the entity-specific bits. Use when the user asks for a "table", "list view", "detai
shesha-claude-designerTHE ENTRY POINT for building a multi-screen Shesha 0.46 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
shesha-design-comprehensionUse 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-systemUse whenever a Shesha 0.46 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", "it looks different after the upgrade", or any request for a polished, consistent visual result rather than just workin
shesha-form-editCreate and edit Shesha 0.46 form configurations directly via the API. Authenticates once, resolves a form by module + name with ConfigurationItem/GetCurrent, backs up the markup, applies the user's requirements (adding, removing, modifying or restructuring components - or building a brand-new form f