Use case · Help center
Your help center writes itself as you code.
Ship a feature, and its help article is live minutes later: written, with a screenshot for each step, in English and French. Nobody on your team has to remember.
- Add a bar to change or delete several tasks at once
- Feature built and tested
- Opened the app, took 3 screenshots
- Wrote the help article, published
- Translated it to French
Set it up once.
Two minutes, then it runs every time you code.
- 01
Connect Claude Code
Add Alori to Claude Code with one command and click Allow. It can now read and write your help center.
- 02
Add one rule
Paste a short rule in your CLAUDE.md. Claude reads it before every task.
- 03
Code as usual
Each feature you ship gets its article: new, updated or taken down, in the same change as the code.
The whole setup is one rule.
Paste it in the CLAUDE.md at the root of your code. It works for a web app, a mobile app or an API.
See the setup →## Keep the help center up to date Our help center lives in Alori. When a change touches something customers see, update its help article in the same change, with Alori's MCP: - New feature: write an article with saveHelpArticle (published), with one screenshot per step uploaded with uploadHelpImage. Then translateHelpArticle. - Changed feature: find it with helpArticles, update it with saveHelpArticle, retake the screenshots of the steps that changed, then translateHelpArticle with refresh: true. - Removed feature: unpublish its article (saveHelpArticle with publish: false).
Docs that never fall behind.
- 01
Always current
The article changes when the code changes, not three sprints later.
- 02
Real screenshots
Claude opens your app and takes a picture of each step, so the pictures match what customers see.
- 03
Every language
Each article is translated as it's published, and refreshed when the original changes.
- 04
Your bot knows it
Your website chat answers from published articles, so it can explain a feature the day it ships.