What are templates?
Templates are a formatting mechanism that allows you to wrap Traycer’s generated content (like plans or verification comments) with your own custom instructions. When you hand off to a coding agent, templates let you include additional context before and after the core content. For example, when Traycer generates a plan, you can use templates to:- Add project-specific setup instructions before the plan.
- Include testing requirements after the plan.
- Specify coding standards and conventions.
- Integrate with MCPs or other tools.
Example template structure
In the following example,{{planMarkdown}} is where Traycer inserts the generated plan content, surrounded by your custom instructions. The frontmatter defines the template’s display name (displayName) and type (applicableFor).
MyTemplate.md
Template types
Plan Templates (applicableFor: plan)
Customize prompts when sending implementation plans to your coding agent.
Available Handlebars:
Contains the generated implementation plan content.
Verification Templates (applicableFor: verification)
Customize prompts when sending verification review comments to your agent for fixes.
Available Handlebars:
Contains the verification review comments and feedback.
Review Templates (applicableFor: review)
Customize prompts when sending review comments to your agent for fixes.
Available Handlebars:
Contains the review comments and feedback.
User Query Templates (applicableFor: user query)
Customize prompts when bypassing the plan and directly sending the generated user query to your agent for fixes.
Available Handlebars:
Contains the generated user query.
Generic Templates (applicableFor: generic)
Create reusable templates for both plan and verification contexts, or any custom agent interactions.
Available Handlebars:
Contains the base prompt content that can be used in any context.
More handlebars will be added in the future.