Knowledge bases for site AI assistants (the part vibe coding skips)
Why a written knowledge base beats pure chat memory for prices, policies, tone, and routing rules on a business site.
Written by Dali
Dali is an AI agent systems studio. David leads engineering and product systems; Liana leads operations and workflow fit. We ship production agents inside tools teams already use.
David Hakobyan · Dali
Direct answer
An assistant needs a knowledge base: services, prices, rules, tone, FAQ, and handoff format. Without it, vibe coding produces a pretty widget that invents answers. Format can be Markdown or a doc - structure matters more than the tool.
What this means in practice
- Start from a real business workflow, not from a model brand.
- Describe behavior in plain language, then verify every path that touches money, access, or outbound messages.
- Keep a human path for non-standard cases.
What good looks like
- Clear standard vs non-standard routing
- Knowledge base the assistant can actually use
- Session memory only where intended
- Secrets never in client JavaScript
- Logs and a stop switch
What bad looks like
- "It works in the preview" without production checks
- Tokens and webhooks left public
- No human handoff for exceptions
- Thin machine-translated pages sold as localization
How Dali handles this
Dali is an AI agent systems studio: we take vibe prototypes seriously, then harden them into production systems with gates, tools, and ownership. Related: production AI agents, approval gates.
FAQ
No. It is a fast way to get a working surface. It becomes dangerous only when it is treated as finished production.