mcpField
T
template-design

template-design

github.com/owl-listenerAgent workflows191298 installsUpdated 20w ago
Repository

About template-design

A design skill for creating reusable prompt templates with fixed instructions, variables, conditional sections, and defaults. It covers variable specifications, template patterns, composition, quality criteria, and supporting documentation and tests.

Key features

  1. 01Reusable prompt structures
  2. 02Typed and bounded variables
  3. 03Conditional sections and defaults
  4. 04Task, persona, format, and escalation patterns
  5. 05Composable template layers
  6. 06Documentation and test artefacts

Use cases

  1. 01Standardize prompts for recurring tasks
  2. 02Compose base instructions with task-specific context
  3. 03Test and maintain a library of prompt templates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/ai-design-skills --skill template-design

After installing, type/template-designin Claude Code to confirm it loaded.

Details

From the project README

Template Design

A prompt template is a reusable prompt structure with variable slots that get filled at runtime. Templates create consistency across similar tasks and make prompt management scalable.

Template Anatomy

A template has:

  • Fixed text: The parts that stay the same every time (instructions, format, role)
  • Variables: Slots that get filled with specific content (user input, retrieved data, configuration)
  • Conditional sections: Parts that appear or disappear based on context
  • Default values: What fills a variable if no specific value is provided

Designing Variables

Each variable should be:

  • Named clearly: {user_query} not {input1}
  • Typed: Is it free text, a selection from options, a number, a boolean?
  • Bounded: What are valid values? What's the maximum length?
  • Documented: What is this variable for? Where does its value come from?
  • Defaulted: What happens if the value is missing?

Template Patterns

  • Task template: A template for a specific type of task. Variables capture the task-specific details while instructions remain constant.
  • Persona template: A template where the persona is variable but the task structure is fixed. Useful for multi-persona products.
  • Format template: A template where the output format is variable but the analysis approach is fixed.
  • Escalation template: A base template with additional sections that activate at higher complexity levels.

Template Composition

Complex prompts can be built from smaller templates:

  • Base template: Core instructions that apply to everything
  • Task overlay: Task-specific instructions layered on top
  • Context injection: Retrieved information inserted at a specific point
  • User preferences: Personal settings that modify behavior

Template Quality Criteria

  • Consistency: The template produces reliably similar outputs for similar inputs
  • Flexibility: The variables allow enough variation for diverse use cases
  • Clarity: The template is easy to read, maintain, and modify
  • Testability: You can verify the template works with a standard set of test inputs
  • Maintainability: Changes to one part don't break other parts

Design Artefacts

  • Template library with documentation
  • Variable specifications per template
  • Test input sets for each template
  • Template versioning and change log
  • Composition rules for combining templates

Comments

Markdown supported