crisp-tc

Category Knowledge Base (CKB) database schema reference — table structure, database creation/upgrade, account management, configuration, Space Planning and Floor Planning data storage, SQL Server and Oracle support

Convert, write, explain, and debug JDA Space Automation scripts — both legacy AutoPilot (.sas) scripts and modern SA Pro C# scripts. Use this skill whenever the user is working with JDA Space Automation, AutoPilot scripting, Space Planning (.psa), Floor Planning (.pfa), or SA Pro automation. This includes converting legacy _PS_/_PF_/_GN_ prefix scripts into C# SA Pro code, writing new Pro scripts from scratch, explaining what a script does, or debugging syntax errors in either format. Trigger any time the user pastes or references an AutoPilot script, asks about SA commands, mentions planogram automation, or wants C# equivalents for legacy Space Automation.

Generate, review, and debug C# code following the Crisp/Blue Yonder JDA Space Automation coding conventions. Use this skill whenever writing new C# scripts or class libraries for JDA Space Automation Pro, CKB (Category Knowledge Base), or related tooling. Covers project structure, Dapper database access, Serilog RollingFileAlternate logging, and the exact method/class patterns established in the ProductExport and SampleSpaceBRV template projects. Trigger any time the user asks to write, scaffold, or review C# code for these systems.

Analyze a Data Manager .fsf form file and convert it to an equivalent OpenAccess (OA) UserControlBase control. Use this skill whenever the user provides an .fsf file or describes a Data Manager form and asks to recreate, migrate, or build the equivalent OA control. Also use when the user mentions Data Manager, DM forms, ProfusionHierarchyCtrl1, VBScript event handlers, .fsf files, or legacy Profusion forms.

Convert a legacy Data Manager .fsf form file into a Mission Control PDK plugin. Use this skill whenever the user provides an .fsf file or describes a Data Manager form and asks to recreate or migrate it as a PDK plugin (not an OpenAccess control). Also use when the user mentions converting DM buttons to a PDK Run button, or asks to "create a PDK for this DM form".