Custom instructions

Note: Custom instructions feature is available exclusively on Bito's Enterprise plan. To use this feature, provide your custom instructions in markdown document (.md file) to the Bito team at [email protected], and we'll integrate it into your knowledge graph.

Custom Instructions allows you to enrich AI Architect's knowledge graph with additional context that's relevant to your engineering workflow. By providing supplementary documentation, you help AI Architect develop a more complete understanding of your project ecosystem.

By default, AI Architect builds a knowledge graph using multiple inputs such as your codebase, issue tracking systems, documentation tools, and observability data. While this provides strong coverage, there is often still important context that lives outside these systems or is not easily discoverable.

Custom instructions allow you to fill that gap by providing documents that describe your system in a more complete way.

Refer to the Knowledge graph documentation for details on how AI Architect builds and maintains its knowledge.

Table of contents

1. Why use custom instructions?

2. What to include in custom instructions?

3. How it works?

4. Impact on AI Architect's capabilities

5. Best practices

6. Getting started

Why use custom instructions?

Use Custom Instructions to add important context that enhances AI Architect's understanding of your projects and systems:

• Fill knowledge gaps: Add context that doesn't exist in your existing systems

• Synthesize information: Consolidate knowledge that spans multiple sources

• Capture tribal knowledge: Document institutional understanding that lives in people's heads

• Provide domain expertise: Include specialized knowledge, business rules, or industry-specific context

What to include in custom instructions?

Custom Instructions can contain any context that helps AI Architect better understand and assist with your projects. Consider including:

Domain knowledge

• Industry-specific terminology and concepts

• Business rules and constraints

• Regulatory or compliance requirements

• User personas and use cases

Operational context

• Service ownership and team structures

• Communication channels and escalation paths

• Deployment processes and environments

• Access patterns and security considerations

Architecture decisions

• Design principles and patterns used

• Technology choices and rationale

• Cross-service dependencies not visible in code

• Integration points with external systems

Standards and guidelines

• Coding conventions specific to your team

• Testing strategies and requirements

• Review and approval processes

• Performance benchmarks and targets

Tribal knowledge

• Historical context for major decisions

• Common pitfalls and how to avoid them

• Undocumented workarounds or solutions

• Best practices learned from experience

How it works?

When you provide a custom instructions document:

1. Bito processes your document and extracts relevant information

2. The extracted context is intelligently integrated into the knowledge graph

3. AI Architect uses this enriched knowledge to provide more accurate and contextual assistance

Impact on AI Architect's capabilities

With custom instructions, AI Architect can:

• Avoid known issues and apply documented best practices

• Answer questions using your project-specific context

• Generate code that follows your team's conventions and standards

• Understand terminology, patterns, and concepts unique to your domain

• Provide recommendations that account for your constraints and requirements

Best practices

Start with high-impact information

Focus on context that significantly affects how AI Architect should understand your systems and processes:

• Critical constraints or requirements

• Frequently misunderstood concepts

• Context that connects different parts of your architecture

Organize for clarity

Structure your document logically:

• Use clear headings and sections

• Group related information together

• Include examples where helpful

• Keep explanations concise but complete

Be specific and actionable

Provide concrete information rather than vague statements:

• ✅ "Use library X for date handling to ensure timezone consistency"

• ❌ "Be careful with dates"

Document the "Why"

Explain reasoning and context behind decisions:

• Why certain approaches are preferred

• Why specific constraints exist

• Why particular patterns are used

Getting started

1

Create your document

Prepare a markdown document (.md file) containing custom instructions:

• Start with your most important information

• Organize content with clear structure

• Use plain language and specific examples

2

Submit to Bito Team

Send your custom instructions document to [email protected]:

• The Bito team will integrate the document into your workspace's knowledge graph

• You'll be notified once the integration is complete