Custom Instructions

Specific rules and guidelines that work alongside other instructions to fine-tune your Twyn's behavior. These are explicit directives that always take priority.

What are Custom Instructions?

Custom instructions are specific rules that override general behavior patterns. Think of them as the "always" and "never" rules for your Twyn.

Example Instructions

Content Boundaries

Set clear limits on what your Twyn will and won't discuss:

"Never provide financial advice or investment recommendations. Always direct users to consult with a financial professional."

Response Format

Control how your Twyn structures its responses:

"When explaining technical concepts, always include a simple analogy and a practical example."

Personality Quirks

Add unique elements that make your Twyn memorable:

"Use cooking metaphors when explaining complex processes. Reference my love for coffee in casual conversations."

Industry-Specific Guidelines

Ensure domain expertise is properly applied:

"Always mention relevant design principles when discussing UI/UX topics. Include accessibility considerations in web development advice."

Writing Effective Instructions

Be Specific Rather Than Vague

Clear, actionable instructions work better than general guidelines.

Examples:

• ❌ "Be helpful with coding questions"
• ✅ "When helping with code, always provide working examples and explain why the solution works"

Include Both Dos and Don'ts

Tell your Twyn what to do AND what to avoid:

"Always ask clarifying questions before providing solutions. Never assume you understand the full context without asking."

Use Step-by-Step Instructions

Break down complex behaviors into clear steps:

Example (Habit Formation):

1. Ask what habit they want to build
2. Identify potential obstacles
3. Provide a science-backed technique
4. Encourage them to track progress

Structure for Clarity

Use headers, bullet points, and formatting to make instructions digestible:

### WHEN USERS ASK ABOUT PRICING ###
- Always mention the free tier first
- Explain value before mentioning cost
- Offer to schedule a demo for complex needs

### NEVER DO ###
- Don't provide exact pricing without context
- Don't pressure users to upgrade immediately

Common Use Cases

Professional Boundaries

"I'm a marketing consultant, not a legal advisor. For any legal questions about marketing compliance, always recommend consulting with a qualified attorney."

Quality Standards

"Always provide at least 3 specific, actionable recommendations. Avoid generic advice like 'it depends' without explaining what it depends on."

Brand Voice

"Use 'we' language when referring to the company. Never say 'I think' - instead say 'we recommend' or 'our experience shows.'"

Safety Guidelines

"If users ask about sensitive topics like mental health crises, provide supportive language and direct them to professional resources. Never attempt to provide medical advice."

Advanced Patterns

Conditional Instructions

Create rules that apply in specific situations:

"IF the user mentions they're a beginner, THEN always define technical terms and provide additional context."

Priority Instructions

Establish hierarchy when instructions might conflict:

"Priority 1: User safety and wellbeing. Priority 2: Accuracy of information. Priority 3: Engagement and personality."

Context-Aware Rules

Adapt behavior based on the conversation context:

"In technical discussions, be precise and detailed. In casual conversations, be more relaxed and personable."

Best Practices

Start Small

Begin with 3-5 core instructions. You can always add more later.

Test with Edge Cases

Try unusual questions to see how your instructions hold up.

Keep Instructions Updated

Regularly review and refine based on real conversations.

Be Consistent

Make sure instructions don't contradict each other or your other settings.

Use Plain Language

Write instructions as if you're explaining to a human assistant.

Testing Your Instructions

After adding custom instructions:

1. Test Boundary Cases - Try questions that should trigger specific instructions
2. Check for Conflicts - Ensure instructions work well together
3. Validate Priorities - Confirm important rules take precedence
4. Review Real Conversations - See how instructions perform in practice

Examples by Role

Customer Support

### ALWAYS ###
- Ask for order number or account info before troubleshooting
- Escalate to human agent if issue involves billing disputes
- End each response with "Is there anything else I can help you with?"

### NEVER ###
- Promise refunds or changes to billing
- Share other customers' information
- Make assumptions about user's technical skill level

Content Creator

### WRITING STYLE ###
- Use short paragraphs (2-3 sentences max)
- Include relevant examples or case studies
- End posts with a question to encourage engagement

### CONTENT GUIDELINES ###
- Always fact-check statistics before sharing
- Cite sources when making claims
- Keep content appropriate for all audiences

Next Steps

Customize your visual appearance with Appearance Settings.