Tips for Getting Great Answers

Practical tips to help you get the most out of Figorit, no technical background needed.

Figorit is designed for everyone on your team, not just engineers. You don't need to know code or use technical jargon. These tips will help you get clearer, more useful answers.

Say What You Want to Know, Not How

Don't try to sound technical. The system is built to translate plain language into code exploration. Guessing at technical terms can actually give you worse results. Instead of 'show me the auth middleware chain', try 'how do users log in?'. Instead of 'what's the DB schema for orders?', try 'what information do we store about an order?'.

Investigating a Bug? Describe the Symptom

Figorit has a dedicated bug investigation mode that activates automatically when you describe a problem. It pulls recent code changes from the last two weeks and correlates them with your report. Just describe what's broken and when it started. For example: 'Users are seeing a timeout when they try to log in since yesterday' or 'The billing page is showing the wrong amount for some customers'. You don't need to guess the cause.

One Focused Question Gets a Better Answer

You can ask multiple things at once, but focused questions get deeper, more thorough answers. If you have several things to ask, ask them one at a time and use follow-ups in the same session. Figorit remembers your full conversation, so each follow-up builds on what came before. Note: prompts with multiple distinct questions may count as more than one question against your monthly allowance.

Great Follow-Up Prompts

After an initial answer, try: 'Can you go deeper on [specific part]?', 'Which team member should I talk to about this?', 'When did this last change?', or 'Could this be related to [symptom a customer reported]?'. Follow-up questions are especially powerful because the system already has context from your earlier questions.

Find the Right Person to Talk To

Figorit can tell you who knows the most about any part of your codebase. Try 'Who should I talk to about payments?' or 'Who last changed the email notifications?'. This is especially useful for routing support tickets or finding the right engineer during an incident.

Narrow Down to a Specific Repository

If your organisation has multiple repositories connected and you know which product or service your question is about, select just that repository before asking. This speeds up answers and avoids pulling in results from unrelated codebases.

What Figorit Won't Do

Figorit answers from your actual committed code, not from general programming knowledge. If something isn't in your repositories, it will tell you rather than guess. It also can't make changes, deploy, or interact with production systems.