Template Syntax

Templates are source code files with embedded placeholders that get replaced during skill execution. This page covers the full syntax and processing pipeline.

Variables

Variables are wrapped in single curly braces and get replaced with values from skill arguments and architecture configuration.

namespace {ServiceName}.{DomainLayer}.Entities;

public class {EntityName} : AggregateRoot<{IdType}>
{
    public string Name { get; private set; }
}

namespace Orders.Domain.Entities;

public class Order : AggregateRoot<Guid>
{
    public string Name { get; private set; }
}

Conditionals

Conditional blocks include or exclude sections of a template based on configuration flags.

// {{#if typed-id}}
public record OrderId(Guid Value);
// {{/if}}

// {{#if guid}}
// Using standard Guid for entity IDs
// {{/if}}

public record OrderId(Guid Value);

Endpoint filtering

Templates can be prefixed to target specific endpoint styles. Only templates matching the selected style are included.

add-endpoint/
  skill definition
  controller.Endpoint.cs
  minimal-api.Endpoint.cs
  fast-endpoints.Endpoint.cs
  EndpointDto.cs          # always included

Processing pipeline

Templates go through a three-step processing pipeline:

1. Filter by endpoint style

Templates with an endpoint prefix that doesn't match the selected style are excluded entirely. The prefix is stripped from the filename.

2. Replace variables

All variable placeholders are replaced with their values from skill arguments, layer variables, and ID strategy configuration.

3. Process conditionals

Conditional blocks are evaluated. True conditions keep their content (markers removed). False conditions are removed entirely.

Template file
    |
    v
 1. Filter endpoints
    |
    v
 2. Replace variables
    |
    v
 3. Process conditionals
    |
    v
Final source code

Built-in variables

These variables are always available from the architecture configuration: