Synthetic Datasets for Prompt Compiler. Feel free to mix and expand! by Frank Brsrk / Agentarium 


### 1) Tone policy (voice behavior)
**File:** `tone_policy_prompt_compiler_gardenier.csv`  
**Purpose:** A tone/voice registry for how responses should sound.  
**Typical fields:** tone id/name, voice keywords, do/don’t rules, formatting cues, verbosity, certainty calibration, risk baseline.

### 2) Domain policy (domain defaults)
**File:** `domain_policy_prompt_compiler.csv`  
**Purpose:** Defines domain-level requirements and defaults (what sections are required, default template, risk baseline).

### 3) Expansion policy (missing-input handling)
**File:** `expand_policy_prompt_compiler_gardenier.csv`  
**Purpose:** Rules for what to do when user input is incomplete (assume defaults, ask follow-ups, apply fallback values), with tags to support routing.

### 4) Prompt template catalogue (templates library)
**File:** `prompt_template_catalogue_prompt_compiler_gardenier_agent.csv`  
**Purpose:** The template library used by the compiler.  
**Includes:** required sections, directives, constraints, output format, tone policy reference, risk baseline.

### 5) Command/mode registry (runtime command catalog)
**File:** `command_mode_prompt compiler.csv`  
**Purpose:** Lists supported command modes and how they behave at runtime.  
**Includes:** command names, mode name, output type, phase/category, aliases, safety notes, RAG keywords.

### 6) Latent constraints (trigger → action signals)
**File:** `latent_costraints_prompt_compiler_gardenier.csv`  
**Purpose:** Signals that detect cues in input and recommend constraint injections (trigger hints, recommended action, severity, domain/type).

### 7) Output patterns (format skeletons)
**File:** `output_patterns_gardenier_prompt_compiler_agent.csv`  
**Purpose:** Reusable output structures (skeletons) per output type, plus notes + risk baseline.

### 8) Validation rules (enforcement view)
**File:** `validation_rules_prompt_compiler_gardenier.csv`  
**Purpose:** Validator-style policies (what to enforce / reject).  
**Overlaps with tone policy, but framed as “checks” and “constraints” for output.