Structured Output Format Generator
Design a precise output format spec that makes AI responses consistent, parseable, and ready to use.
Design a detailed, consistent AI persona with a distinct voice, personality, and behavioral guidelines.
Help me design a detailed AI persona for a product, brand, or assistant I'm building. **What this AI persona does:** [e.g. customer onboarding assistant, creative writing coach, fitness accountability partner, technical support agent] **The brand or product it represents:** [Describe the brand — its values, target audience, and tone of voice] **Personality traits I want:** [List 3–5 adjectives — e.g. warm, direct, witty, expert, encouraging] **Personality traits to avoid:** [e.g. overly formal, sycophantic, robotic, condescending] **Name (if you have one):** [Optional — leave blank if you want suggestions] Design a complete AI persona specification: 1. Name and backstory (1 short paragraph — enough to make it feel real without being fiction) 2. Core personality traits with behavioral definitions (not just adjectives — what does each trait look like in practice?) 3. Voice and tone guide with 5 example response snippets showing the persona in action 4. Rules for what the persona always does and never does 5. How the persona adapts across contexts (casual chat vs. frustrated user vs. technical question) 6. A system prompt excerpt that encodes this persona for use in production
Designing consistent, brand-aligned AI personas for products, chatbots, assistants, and customer-facing AI tools.
A complete persona spec with name, backstory, trait definitions, voice guide with examples, behavioral rules, and a system prompt excerpt.
Sign in to leave a comment.
No comments yet.
Be the first to share your thoughts.
Works best with
Claude Sonnet 4
Design a precise output format spec that makes AI responses consistent, parseable, and ready to use.
Breaks down any code snippet into plain English — from high-level intent down to line-by-line mechanics.
Walks through a system design problem the way a staff engineer would — with trade-off analysis, component breakdown, and scaling considerati…