grunty-templates

You can enforce consistent PHP template authoring rules by codifying conventions for directives, layouts, and components in templates/ and grunt-ui/ directories. This ensures standardized output conventions and reduces template errors across Grunty-powered projects.

g:if and g:foreach are Grunty PHP template directives used for control flow and iteration. They are part of a directive system that also includes g:extends, g:block, and g:slot for structuring layouts and components within templates.

To create a Grunty template extending a base layout, you apply g directives like g:extends and g:block according to defined rules. The template requires YAML frontmatter with name and description in SKILL.md, and supports optional resources folders.

Yes, Grunty template rules require YAML frontmatter containing name and description fields in SKILL.md files. This metadata codifies template conventions and supports optional resources folders including scripts, references, and assets for organized template management.

The best way to standardize layouts and slots in Grunty-powered projects is documenting layout, component, and slot patterns using g:extends, g:block, and g:slot directives. This provides safe, predictable template authoring workflows for PHP-based applications.

Grunty template components may not render correctly if directive rules for g:if, g:foreach, g:extends, g:block, or g:slot are misapplied. Enforcing output conventions and safety rules across templates/ and grunt-ui/ directories ensures correct rendering.