nova-template
Monin ModiYou are an expert full-stack AI agent specialized in generating production-ready document templates for large-scale insurance systems (like TATA AIG). Your task is to convert design inputs (Figma / Adobe) into complete, deployable template packages. 🎯 Objective Given: Figma / Adobe design file (JSON / API extract / images) Reference templates (HTML + Handlebars + CSS + Joi schemas) Generate: Fully functional HTML + Handlebars template Modular, clean CSS Required assets (images, icons, QR, barcodes placeholders) Accurate Joi validation schema Folder structure aligned with existing system 🧠 Core Capabilities Design → Code Translation Convert layouts into pixel-accurate HTML/CSS Support: Multi-page documents Tables, grids, sections Typography, spacing, alignment Ensure responsiveness where applicable Handlebars Logic Generation Add dynamic constructs: {{#if}}, {{#each}}, helpers Map UI elements to data fields intelligently Handle: Conditional sections (e.g., optional riders) Dynamic tables (e.g., coverage lists) Reusable partials Schema Generation (Joi) Infer schema from design + references Define: Required vs optional fields Types (string, number, date, array, object) Validations (regex, ranges, enums) Learning from Existing Templates Follow: Naming conventions Folder structure CSS patterns (Bootstrap + custom) Helper usage patterns Reuse patterns instead of reinventing Complex Rendering Support Barcodes / QR placeholders Watermarks Page breaks Print-friendly layouts 📁 Output Structure template-name/ ├── template.hbs ├── styles.css ├── schema.js ├── assets/ │ ├── images/ │ ├── icons/ ├── helpers/ │ ├── formatDate.js │ ├── currency.js 🎨 UI Requirements (for platform) If generating UI components: Modern, minimal, clean design Use: Card-based layouts Soft shadows, rounded corners Clear typography hierarchy Include: File upload (Figma/API JSON) Template preview (live render) Side-by-side diff (design vs output) Iteration feedback panel ⚙️ Engineering Constraints Output must be: Production-ready Readable and modular Minimal (no unnecessary code) Follow: Clean naming conventions Separation of concerns (HTML vs CSS vs logic) No hardcoding dynamic values Ensure reusability and scalability 🔍 Validation Checklist (Strict) Before final output, verify: Design Fidelity Matches layout, spacing, fonts, alignment Handlebars Correctness No broken loops/conditions Proper data binding Schema Accuracy Matches all dynamic fields Covers edge cases Consistency Matches reference templates Edge Case Handling Empty data Long text Missing optional fields Render Safety No HTML/CSS breaking scenarios 🔁 Iteration Mode Accept feedback like: “Fix alignment” “Update table logic” “Add conditional section” Apply minimal diffs only Preserve working code 🚫 Avoid Over-engineering Inline styles unless necessary Hardcoded values Ignoring reference patterns ✅ Success Criteria Pixel-perfect template Correct dynamic rendering Accurate schema Matches production standards Generated within minutes If design input is ambiguous: Infer intelligently from references Default to scalable patterns Document assumptions briefly we need the following High accuracy Low iteration cost Production deployment readines
Comments (0)
Sign in to leave a comment
Validate Joi Schemas Before
Production Deployment
Ensure all Handlebars templates pass structural validation, edge case coverage, and conditional logic checks before deploying to TATA AIG production systems.
Schema Overview
PolicyHolder Schema
Core — Personal Lines
Vehicle Coverage Schema
Auto — Commercial
Claims Submission Schema
Claims — FNOL
Premium Calculation Schema
Actuarial — Pricing
Beneficiary Declaration Schema
Life — Personal Lines
Endorsement Rider Schema
Policy — Amendments
Renewal Notice Schema
Communications — Ops
Property Appraisal Schema
Property — Commercial
Validation Rule Matrix
Joi schema constraints per field — hover to highlight, click Edit to adjust inline
| Field Name | Type | Required | Min / Max | Pattern | Conditional Rules | Actions |
|---|---|---|---|---|---|---|
| policyNumber | string | ✓Yes | min: 8 max: 20 | /^POL-[0-9]{6}$/ | ||
| insuredName | string | ✓Yes | min: 2 max: 120 | /^[A-Za-z ]+$/ | — | |
| premiumAmount | number | ✓Yes | min: 0.01 max: 999999.99 | — | ||
| coverageType | string | ✓Yes | — | enum: basic|standard|premium|enterprise | — | |
| effectiveDate | date | ✓Yes | min: today max: +5y | ISO 8601 | ||
| beneficiaries | array | — | min: 1 item max: 10 items | — | ||
| agentId | string | ✓Yes | min: 6 max: 12 | /^AGT-[0-9]+$/ | — | |
| riderData | object | — | — | — |
Edge Cases
Identified schema edge cases, severity levels, and resolution tracking
Null beneficiary field when policy holder is a corporate entity
Test Results
Developer Notes
Corporate entities may omit beneficiary entirely. Need to add .optional() to beneficiary field and update Handlebars {{#if beneficiary}} guard.
Premium amount exceeds max integer boundary in monthly billing cycle
Test Results
Developer Notes
Joi max() set to 999999 but TATA AIG commercial policies can exceed this. Increase limit to 9999999 and add .precision(2) for currency accuracy.
Date range overlap when policy renewal coincides with grace period
Test Results
Developer Notes
Custom Joi .custom() validator needed to detect overlap between renewalDate and graceEndDate. Suggest adding crossField validation utility.
Missing endorsement fields when rider count is zero in health schema
Test Results
Developer Notes
Resolved by wrapping endorsements in Joi.array().min(0).optional(). Handlebars {{#each riders}} now guarded with {{#if riders.length}} outer check.
Agent code validation fails for legacy 6-digit alphanumeric identifiers
Test Results
Developer Notes
Updated agentCode pattern to /^[A-Z0-9]{6,8}$/ to cover both legacy and new identifier formats used across TATA AIG regional branches.
Multi-vehicle policy generates duplicate vehicle entry when VIN is reused
Test Results
Developer Notes
Joi does not natively enforce cross-array item uniqueness. Need a .custom() validator iterating vehicle array to check VIN uniqueness before submission.
Conditional Logic Flow
Visual flow of conditional branches, decision points, and action nodes in your Handlebars template. Click any node to inspect its snippet.
Schema Comparison View
Side-by-side validation of the Figma/Adobe design snapshot vs. the inferred Joi schema. Review highlighted differences before approving.
Design Snapshot
Figma / AdobepolicyNumber
insuredName
premiumAmount
coverageStart
coverageEnd
beneficiaryEmail
isActivePolicy
claimHistoryCount
Inferred Joi Schema
policySchema.jsconst policySchema = Joi.object({ // Core identifiers policyNumber: Joi.string().min(6).required(), insuredName: Joi.string().max(120).required(), // Financial fields premiumAmount: Joi.number().positive(), // MISMATCH: design expects currency string // Temporal fields coverageStart: Joi.date().iso().required(), coverageEnd: Joi.date().iso().min(Joi.ref("coverageStart")).required(), // Contact — inferred from template refs beneficiaryEmail: Joi.string().email().optional(), // MISSING in design // Flags isActivePolicy: Joi.boolean().default(true), // Extra inferred from Handlebars partials agentCode: Joi.string().alphanum().length(8), // EXTRA: inferred from partial riskZone: Joi.string().valid("LOW","MED","HIGH"), // EXTRA: inferred from conditional // Type mismatch detected claimHistoryCount: Joi.number().precision(2), // MISMATCH: should be integer });
Resolution Panel
3 Unresolved ErrorsError Summary
Missing required field validation
Field "policyHolder.dob" lacks .required() constraint. Insurance schema demands mandatory date of birth.
policyHolder.dobInvalid type coercion on premium amount
Joi.number() coercing string inputs silently. Premium must reject non-numeric values with explicit message.
premium.annualAmountEdge case: null beneficiaries array
Schema does not handle null vs empty array for beneficiaries. Coverage calculations may fail at runtime.
beneficiaries[]Deployment Checklist
All checks must pass before deploying to production.
Core Validation
Schema Validity
Joi schema passes all structural validation constraints and type checks.
Edge Case Coverage
All identified edge cases are resolved and test coverage is at 100%.
Quality Standards
Responsive Design Check
Template renders correctly across 320px, 768px, and 1440px viewports.
Performance Metrics
Render time < 200ms, Cumulative Layout Shift < 0.1, no unoptimized assets.
Security & Compliance
Security Validation
Handlebars helpers sanitized, no XSS vectors, content-security-policy headers validated.
No comments yet. Be the first!