Skill("custom-plugin-prompt-engineering:prompt-templates")

parameters:
  template_category:
    type: enum
    values: [code, writing, analysis, extraction, generation]
    required: true

  customization_level:
    type: enum
    values: [minimal, standard, full]
    default: standard

  variables:
    type: object
    description: "Key-value pairs for template placeholders"

syntax:
  variable: "{variable_name}"
  optional: "{?optional_variable}"
  conditional: "{#if condition}content{/if}"
  list: "{#each items}{.}{/each}"
  default: "{variable|default_value}"

example: |
  You are a {role|software engineer}.
  {#if context}Context: {context}{/if}
  Task: {task}

# Code Review Template

You are a senior {language|software} engineer performing a code review.

## Review Focus
- Security vulnerabilities
- Performance issues
- Code quality and maintainability
- Best practice violations

## Code to Review
```{language}
{code}

### 2. Technical Documentation Template

```markdown
# Documentation Generator Template

You are a technical writer creating documentation for {project_type}.

## Documentation Type
{doc_type|API reference}

## Source Material
{source}

## Output Format
Generate documentation following this structure:

### Overview
- Purpose and use cases
- Key concepts

### {#if is_api}API Reference
For each endpoint/function:
- Signature
- Parameters (name, type, description, required)
- Return value
- Example usage
- Error handling
{/if}

### Examples
- Basic usage
- Common patterns
- Edge cases

### Troubleshooting
- Common issues and solutions

# Bug Analysis Template

You are a debugging expert analyzing a software issue.

## Bug Report
{bug_description}

## Error Information
{#if error_message}
Error: {error_message}
{/if}
{#if stack_trace}
Stack Trace:

{/if}

## Relevant Code
```{language}
{code}

### 4. Data Extraction Template

```markdown
# Data Extraction Template

You are a data extraction specialist.

## Task
Extract {data_type} from the following {source_type}.

## Source
{source}

## Extraction Schema
{schema}

## Rules
- Extract only explicitly stated information
- Use null for missing fields
- Maintain original formatting for text fields
- {#each additional_rules}{.}{/each}

## Output
Return valid JSON matching the schema above.

# Content Generation Template

You are a {content_role|content writer} creating {content_type}.

## Target Audience
{audience}

## Tone and Style
- Tone: {tone|professional}
- Style: {style|clear and concise}
- Length: {length|medium}

## Topic
{topic}

## Requirements
{#each requirements}
- {.}
{/each}

## Additional Instructions
{#if instructions}{instructions}{/if}

## Output
Generate the {content_type} following all requirements above.

template_lifecycle:
  creation:
    - Define variables and placeholders
    - Set defaults for optional params
    - Add validation rules
    - Document usage

  usage:
    - Load template
    - Validate variables
    - Substitute placeholders
    - Return final prompt

  maintenance:
    - Version templates
    - Track usage metrics
    - A/B test variants
    - Deprecate outdated

optimization:
  remove_redundancy:
    before: "Please kindly ensure that you carefully..."
    after: "Ensure you..."

  use_lists:
    before: "Check for security issues. Also check for performance. And check for quality."
    after: |
      Check for:
      - Security issues
      - Performance
      - Quality

  template_variables:
    before: "You are a Python expert reviewing Python code for Python best practices"
    after: "You are a {language} expert reviewing code for best practices"

validation_checklist:
  structure:
    - [ ] All variables are documented
    - [ ] Defaults provided for optional vars
    - [ ] Clear output format specified

  quality:
    - [ ] Tested with real data
    - [ ] Edge cases handled
    - [ ] Error messages helpful

  maintenance:
    - [ ] Version tracked
    - [ ] Usage documented
    - [ ] Examples provided