Add Template

load-plain-reference

{% include %}

.plain

import

requires

When to Use Templates

• The exact same spec structure is needed in more than one

  .plain

  file.
• The reused content differs only in specific values (names, paths, config) that can be parameterized.
• You want a single source of truth for a pattern that appears in multiple modules.

Format

Including a Template

{% include %}

{% include "console_app_template.plain", main_file_name: "app.py", app_name: "MyApp" %}

{{ main_file_name }}

Writing a Template

template/

{{ variable_name }}

***definitions***
- :{{ app_name }}MainFile: is the entry point file for :{{ app_name }}:.

***implementation reqs***
- :{{ app_name }}MainFile: should be called "{{ main_file_name }}".

Workflow: Including an Existing Template

1. Check the

   template/

   directory to see what templates are available.
2. Read the template to understand what parameters it expects and what content it produces.
3. Add the

   {% include %}

   statement to the target

   .plain

   file with the correct parameters.
4. Verify that the expanded content does not introduce concept name collisions or duplicate sections.

Workflow: Creating a New Template

1. Identify the repeated pattern — find spec content that is duplicated (or will be duplicated) across multiple

   .plain

   files.
2. Extract the common content into a new

   .plain

   file in the

   template/

   directory.
3. Parameterize the differences — replace the varying parts with Liquid variables.
4. Update the original files to use

   {% include %}

   instead of the duplicated content.

Validation Checklist

• Template file is in the

  template/

  directory
• All varying parts are parameterized with Liquid variables
• All required parameters are passed at each

  {% include %}

  call site
• Expanded content does not introduce concept name collisions
• Template is used by more than one

  .plain

  file (otherwise, inline the content)