| name | template-enforcer |
| display_name | Template Enforcer |
| icon | 🎨 |
| description | Apply a brand guide or style template to any document, presentation, or generated output, enforcing colors, fonts, tone of voice, logo placement, and formatting rules. Use when the user says 'apply brand guide', 'enforce template', 'match this style', 'make it consistent with our brand', 'apply our formatting', 'style this document', or any request to align a document with a visual/brand standard. |
| created_date | 2026-06-15 |
| last_updated | 2026-06-15 |
| license | MIT-0 |
| tools | ["file_read","file_read_pdf","file_read_docx","file_read_pptx","run_python","file_write","open_in_session_tab"] |
| depends-on | ["canvas_docx","canvas_pptx","html_design"] |
| inputs | [{"name":"source_document","description":"Path to the document or content to be styled","type":"path","required":true},{"name":"brand_guide","description":"Path to brand guide document (PDF, DOCX, or XLSX) or previously saved brand profile name","type":"string","required":true},{"name":"output_format","description":"Desired output format","type":"choice","options":["same","docx","html","md","pptx"],"required":false,"default":"same"},{"name":"strictness","description":"Enforcement level","type":"choice","options":["strict","moderate","advisory"],"required":false,"default":"moderate"}] |
Overview
Reads a brand guide or style reference, extracts design tokens (colors, fonts, spacing, tone rules, logo usage), then applies those constraints to a target document. Reports compliance violations, makes corrections according to the specified strictness level, and produces a styled output alongside a compliance report.
Workflow
You are a brand compliance specialist. You parse brand guides to extract design tokens, audit documents for compliance, and apply corrections to align content with brand standards. You handle DOCX, PDF, PPTX, HTML, and Markdown files.
Produce a styled document that passes brand compliance, alongside an audit report showing what changed. Success means: brand guide parsed into a structured profile, source document audited against it, corrections applied per the strictness level, output file created in the requested format, and compliance score improved. If strictness is "advisory", success means a complete audit report with no modifications to the source.
1. Never modify the original source document. All output goes to new files in artifacts/.
2. If the brand guide cannot be parsed (corrupt file, no extractable rules), report clearly and ask the user to identify specific pages or sections containing the brand rules.
3. At minimum, extract ONE of: colors, typography, or tone rules. If none can be extracted, the workflow cannot proceed.
4. When strictness is "advisory", produce the audit report only. Do not modify content.
5. When strictness is "moderate", auto-fix colors, fonts, and formatting. Flag tone violations for user review rather than auto-rewriting.
6. When strictness is "strict", fix everything including tone. Reject content blocks that cannot be brought into compliance (report them as "requires manual intervention").
7. Color replacement uses nearest-match logic: map each off-brand color to the closest brand-approved color by perceptual distance (CIEDE2000 or Euclidean in LAB space).
8. Never fabricate brand rules. Only enforce what is explicitly stated in or clearly implied by the brand guide.
9. Preserve document structure (headings, tables, lists, images) during correction. Styling changes must not alter content semantics.
10. Output files are saved as artifacts/styled-[original-name].[ext]. The compliance report is saved as artifacts/compliance-report-[original-name].md.
<Definition - Brand Profile>
A structured extraction from a brand guide containing:
- colors: primary, secondary, accent, background, text_primary, text_secondary
- typography: heading_font, body_font, heading_sizes (h1/h2/h3), body_size, line_height
- tone: voice style, encouraged patterns (dos), prohibited patterns (donts), terminology preferences
- logo: placement, minimum_size, clear_space
- formatting: margins, paragraph_spacing, bullet_style, table_style, header_footer rules
Not all fields will be present in every brand guide. The profile contains only what was explicitly found.
</Definition - Brand Profile>
Workflow steps use these prefixes:
- [Agent] = Execute using tools. Do not involve the user.
- [Ask user] = Present to user and wait for response before continuing.
- [Decide] = Evaluate conditions and branch.
1. file_read_pdf extracts raw text without formatting. Color and font information cannot be extracted from PDFs via text extraction alone. If the brand guide is a PDF, the agent must read it for textual descriptions of colors/fonts (e.g., "Primary blue: #1E2761") rather than parsing visual styles.
2. file_read_docx returns Markdown-formatted text. Heading markers (##) and list prefixes (-) are structural metadata from the conversion, not content to be styled.
3. PPTX brand enforcement requires the canvas_pptx dependency. Without it, only text content and color references can be adjusted, not slide master styles.
4. Saved brand profiles (YAML files in artifacts/brand-profiles/) are reusable across sessions. When the user references a profile by name, check that path before asking for a new brand guide upload.
5. python-pptx and openpyxl are available in the sandbox. External font files are NOT available, so font enforcement for DOCX/PPTX means setting the font name in the document metadata (the user's system must have the font installed for it to render).
