I Built a Legal & Wellness AI Assistant with Django + Groq (Llama 3.3) — Here's How

Hafsa Noor Muhammad — Mon, 13 Jul 2026 10:41:13 +0000

Introduction

A few weeks ago, I started building something I had been thinking about for a while. Legal advice is expensive, and mental wellness resources aren't always easy to access. I wondered if I could combine both in one tool.

So I built a dual-mode AI assistant. One mode handles legal questions like contracts and intellectual property. The other mode focuses on wellness topics like stress and anxiety.

It is not a replacement for professionals. But it can be a helpful starting point for people who need basic information.

What It Does

The assistant has two modes.

Legal mode answers questions about contracts, intellectual property, court procedures, and laws. It explains things in simple language and always reminds users to consult a lawyer.

Wellness mode offers guidance on stress, anxiety, sleep, motivation, and mental health. It provides practical tips and encourages users to seek professional help when needed.

Users can switch between modes with one click. The bot also detects if a question matches the current mode and suggests switching if it does not.

The Tech Stack

I used Django for the web framework. It handles routing, sessions, and the backend logic.

For AI, I used Groq's API with the Llama 3.3 70B model. The responses are fast and accurate.

The frontend is built with HTML, CSS, and JavaScript. It is simple and works well on both desktop and mobile.

For deployment, I used Streamlit. It made the process straightforward.

How I Built It

Let me walk through the key parts of the code.

The first thing I did was define system prompts for each mode. These prompts tell the AI how to behave and what to avoid.

For legal mode, I instructed the AI to only answer legal questions and to always add a disclaimer about consulting a lawyer.

For wellness mode, I focused on empathy and practical advice, with a disclaimer about consulting a healthcare provider.

Then I built a domain detection system. It uses keyword scoring to figure out if a question is legal, wellness, or unknown. If the question does not match the current mode, the bot politely asks the user to switch.

This is how the detection works. I created two lists of keywords. Legal keywords include words like contract, patent, lawsuit, and copyright. Wellness keywords include stress, anxiety, sleep, and meditation. The system compares the scores and decides which domain the question belongs to.

For storing conversations, I used Django sessions. Each user gets their own session, and the bot remembers the last twenty messages. This keeps the context natural without hitting token limits.

Here is how the session storage works. When a user sends a message, the bot checks the session history. It generates a response using the current mode and the conversation context. Then it saves the new message and response to the session. If the history exceeds twenty messages, it keeps only the most recent ones.

The Groq API integration is simple. I send the system prompt, the conversation history, and the user's message. The API returns a response, which I send back to the frontend.

I also added error handling. If something goes wrong, the bot shows a friendly error message instead of breaking.

Challenges I Faced

The hardest part was prompt engineering. I had to test many different prompts to get accurate and safe responses. The tone had to be professional in legal mode and empathetic in wellness mode. Finding the right balance took time.

Domain detection was tricky too. Some words appear in both domains. For example, the word stress can appear in legal contexts like emotional distress. I had to refine the keyword lists to reduce false positives.

Session management was another challenge. Django sessions work well, but they have size limits. Storing too much history could cause problems. I decided to keep only the last twenty messages. This is enough for context and stays within the limits.

Security was important. I used environment variables to store the API key. This keeps it out of the code and safe from accidental exposure.

What I Learned

This project taught me a lot about working with AI APIs. Groq is incredibly fast. Responses come back in under two seconds, which makes the bot feel responsive and natural.

I also learned about prompt engineering. The way you structure a prompt has a huge impact on the quality of the response. Small changes can make a big difference.

Django sessions are simple to use but have limitations. For production, I would consider Redis or a database for better scalability.

Domain detection with keyword scoring works surprisingly well. It is not perfect, but it is good enough for this use case.

Deploying on Streamlit was easy, but session persistence can be tricky. In-memory storage resets when the server restarts. For a production app, I would use a more persistent solution.

What I Plan to Add Next

I have a few features in mind for the future.

I want to add PDF upload so users can upload legal documents for analysis. That would be a useful feature for people reviewing contracts.

User authentication would allow people to save their chat history and access it later.

I also want to add dark mode for better usability at night.

Chat export would let users download their conversations as PDF or text files.

Multi-language support could make the tool accessible to more people.

Voice input is another feature I am considering. It would make the bot easier to use on mobile.

Try It Yourself

You can test the bot with a legal question, like What is intellectual property?, or ask for wellness advice, such as _How can I reduce stress? _To try it for yourself, visit the live demo: https://django-groq-ai-assistant-mdog3pri4eef5lusavapkg.streamlit.app/

Final Thoughts

Building this project was a great learning experience. I started with a simple idea and turned it into something functional and useful.

It is not perfect, and there is always room for improvement. But I am happy with how it turned out.

If you are building something similar, I would love to hear about it. Feel free to share your experience in the comments.

Thank you for reading.

Disclaimer

This tool provides general information only. It is not a substitute for professional legal or medical advice. Always consult a qualified professional for your specific situation.

DEV Community: Hafsa Noor Muhammad