yifanfeng97/hyper-extract/template-optimizer

Template Optimizer

Automatically analyze and optimize YAML templates by applying best practices and fixing common issues.

Workflow

1. Parse YAML → 2. Analyze Issues → 3. Apply Fixes → 4. Generate Report

Step 1: Parse YAML

Load the YAML template and validate basic structure.

Step 2: Analyze Issues

Check against these rules:

Step 3: Apply Fixes

Apply fixes based on optimization level:

Step 4: Generate Report

Output changes with explanations for learning.

Detection Rules

Rule 1: Multi-language Consistency

❌ Pattern: [a-zA-Z]+\([^)]+\) in zh fields
❌ Pattern: Chinese chars in en fields

Fix: Separate language content, use pure Chinese in zh, pure English in en.

Rule 2: Field Naming

❌ relation_type → type
❌ event_date → time
❌ entity_type → type

Fix: Standardize to concise names.

Rule 3: Field Count

⚠️ entities.fields > 5 → Flag for review
⚠️ relations.fields > 5 → Flag for review

Fix: Simplify to essential fields, use priority: Essential → Important → Optional.

Rule 4: Schema-Guideline Separation

❌ Repetition of field definitions in guideline
❌ Schema descriptions in rules

Fix: Schema defines WHAT, Guideline defines HOW TO DO WELL.

Rule 5: Hypergraph Grouping

❌ relation_members: participants (string) + role field exists
❌ relation_id contains participant field

Fix: Use nested grouping relation_members: [group_a, group_b] when entities partition by roles.

Design Principles

Schema vs Guideline

❌ Wrong: Guideline repeats schema definitions ✅ Correct: Guideline explains how to extract well

Information Density

For entities and relations:

Max: 5 fields per component

Naming Conventions

Reference Files

Output Format

# Optimization Report
 
## Changes Made
 
| File | Issue | Fix | Level |
|------|-------|-----|-------|
| template.yaml | `relation_type` | renamed to `type` | Auto-fix |
| template.yaml | Mixed language | Fixed zh/en separation | Auto-fix |
| template.yaml | 7 relation fields | Suggested simplification | Suggest |
 
## Summary
 
-Auto-fix: 2
-Suggestions: 1
-Manual review: 0

Integration

Full workflow: brainstorm → designer → optimizer → validator
                           ↓
                    Apply best practices
                    Auto-fix common issues

When to use:

• After creating new templates
• Before validator
• During template review
• Batch optimization of existing templates