Ask great questions

Claudioo understands natural language, so you don't need to speak "engineer". A few simple habits can make your conversations significantly more productive — no matter your role.

For everyone

One task per session

Claudioo works best when focused. Mixing many topics in one long thread leads to summarization, where older details get compressed away. Keeping each session focused on one task gives you higher-quality answers throughout. See One topic per session.

Starting a new session is free and instant. Don't hesitate to start fresh when switching topics.

Let Claudioo read files directly

Instead of copying and pasting code or logs into the chat, just point Claudioo to the source:

Read the sales order model in my project

Claudioo can read files directly from your workspace, which is faster and more memory-efficient than pasting text.

Use skills when they fit

If there's a skill for what you need, use it. Skills are optimized workflows that know what information to gather and how to structure the result.

Instead of explaining step by step what you need, just type the skill command — for example, /jf-prepare for meeting notes or /check-timesheets for timesheet review.

Asking in business terms

You don't need to know model names, field names, or technical details. Describe what you see and what you need in business terms — Claudioo will figure out the rest.

Examples that work:

The discount field on the sales order form isn't calculating correctly — it should apply before taxes

How does the approval workflow work for purchase orders over 10,000€?

We need a report that shows all open invoices grouped by customer with aging buckets

What happens when a sales person confirms a quotation? Walk me through the steps

Claudioo understands Odoo's business processes. You can describe things by their screen names, menu paths, or business rules — it will map them to the right technical components.

Asking in technical terms

The more specific you are, the faster Claudioo finds what you need.

Good:

Look at the sale.order model in my sale_custom module — how does the _compute_margin method work?

Less good:

Check my sales customizations

Mentioning model names, file paths, or method names helps Claudioo skip the guesswork and go straight to the answer.

Question shapes that work well

• What — "What does the action_confirm method do on purchase.order?"
• How — "How does Odoo compute the amount_total on account.move?"
• Why — "Why might the stock.picking cron job be timing out?"
• Show me — "Show me how sale.order handles the discount field"

What Claudioo already knows

When you create a session from a project, Claudioo automatically has:

• Your Odoo version — from the project config
• Your repository and branch — loaded into the workspace
• Your custom instructions — injected at the start of every session

You don't need to repeat this information. Only mention it if you're asking about something different from your project's defaults (e.g., "How does this work in Odoo 17?" when your project is on 18), or if you're not using a project at all.

Learn more

• One topic per session — Why focus matters
• Run a skill — Pre-built workflows you can invoke
• Ask about code — How Claudioo searches your codebase