generating-zoom-sql

Generates and validates Divalto Zoom SQL .dhsp files with 27 CRUD lifecycle procedures.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill generating-zoom-sql-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-zoom-sql
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/generating-zoom-sql
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill generating-zoom-sql-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Jinja2, and includes scripts (resource) and references (resource) components.

What problem does it solve? Writing a Divalto ERP Zoom SQL screen file (.dhsp) by hand requires reproducing 27 mandatory CRUD lifecycle procedures, correct domain prefixes, framework calls, and strict ISO-8859-1/CRLF encoding, which is error-prone and slow. ## Core Features & Use Cases - Template-based generation: Renders a complete .dhsp file from a Jinja2 template using naming tokens computed from domain, entity, table, and key field parameters. - Rule-based validation: Checks generated or existing files against 11 rule categories (Z01-Z10, M04, ENC, naming conventions) and reports errors and warnings as JSON. - Use Case: You need the user interface file for a new Retail business entity FamRglt. Provide the domain, entity, table, key field, and description, and receive a validated rttzfamrglt_sql.dhsp file ready for the Divalto ERP. ## Quick Start Ask the assistant to generate the Zoom SQL file for the entity FamRglt in the Retail domain with table RtlFamRglt, key field RgltFam, and description Famille de reglement.

Frequently Asked Questions about generating-zoom-sql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Divalto Zoom SQL .dhsp file?

Run generate_zoom.py with --params and provide the domain, entity, SQL table, key field, and description. The script computes all naming tokens, renders the Jinja2 template, and writes the .dhsp file in ISO-8859-1 with CRLF line endings.

How do I validate an existing Zoom SQL .dhsp file?

Run validate_zoom.py with --path pointing to the file, optionally adding --tokens with a JSON token file for cross-checks. It returns a JSON report listing errors and warnings across 11 rule categories including missing procedures, encoding, and domain prefix mixing.

What are the 27 mandatory procedures in a Divalto zoom?

They cover the full CRUD screen lifecycle: ZoomDebut, ZoomCreation, ZoomAvantWrite, ZoomAvantRewrite, ZoomAvantDelete, ZoomConsult, ZoomArret, Construire_Condition_Selection, and related reservation and post-operation hooks. The full list with typical content is documented in reference/zoom-procedures.md.

Why does my Divalto zoom file fail with encoding errors?

Divalto .dhsp files must be encoded in ISO-8859-1 with CRLF line endings and no UTF-8 BOM. The validator's ENC rule detects LF-only endings, UTF-8 BOMs, and multi-byte UTF-8 sequences; regenerate the file or convert it with the writing-diva-files skill.

What Python dependencies does the zoom generator need?

The generation script requires Jinja2 for template rendering, installed via pip. The validation script uses only the Python standard library (argparse, json, re, os, sys).