Meta Rules
Layer 1: Foundational
Purpose
Section titled “Purpose”- Captures repo-wide stylistic and behavioral guardrails in one block
- Lets requesters dial tone, caution level, and explanation depth without rewriting prompts
When to Use
Section titled “When to Use”- Whenever the requester wants explicit control over style or risk posture
- Before running orchestration workflows so all personas inherit the same “house style”
- During QA to confirm outputs match agreed meta preferences
Structure / Template
Section titled “Structure / Template”[META-RULES]- Voice & Tone: (e.g., calm, technical, encouraging)- Caution Level: (e.g., emphasize risks first)- Conciseness: (e.g., 4 bullets max per section)- Evidence Style: (e.g., cite sources, mention trade-offs)- Prohibited Behaviors: (e.g., no speculation on prices)- Custom Preferences: (slots for audience, formatting, analogies, etc.)
[APPLICATION]- Each persona acknowledges the rules.- Restate any conflicts before proceeding.Examples
Section titled “Examples”Technical (governance memo)
Section titled “Technical (governance memo)”[META-RULES]Voice: formal and audit-ready.Caution: highlight compliance risks first.Conciseness: sections ≤5 sentences.Evidence: cite config files or RFCs.Prohibited: no TODO language.Creative (storytelling brief)
Section titled “Creative (storytelling brief)”[META-RULES]Voice: hopeful but grounded.Caution: avoid overpromising AI capabilities.Conciseness: allow short scenes, max 300 words.Evidence: weave in real user anecdotes.Prohibited: jargon, unexplained acronyms.Custom: include one reflective question at the end.Combination Guidance
Section titled “Combination Guidance”| Pair With | When |
|---|---|
| Orchestration | Broadcast house style to every role |
| Recursive Self-Eval | Explicitly check compliance during QA |
| Planning Phase | Declare alongside planner section |