One architecture, one set of guidelines, for all your projects?

说明与用途

公司有多个仓库，架构和文档各不相同。Ohara 将所有规则和文档集中到一个仓库，助手可以实时读取规则并自动更新文档，从而实现统一和减少重复工作。

问题

Multiple repositories in a company maintain separate guidelines and documentation, leading to inconsistent practices, duplicated effort, and stale docs.

结果

Consistent architecture, guidelines, and UI across all projects; automated doc updates; single source of truth; reduced duplication and stale documentation.

工作流

• 1. Connect assistant to Ohara via "claude mcp add --transport http ohara https://your-ohara/mcp".
• 2. Run "/ohara:init" in each project to generate .claude/rules/ohara.md and add MCP server to .mcp.json.
• 3. Assistant reads applicable guidelines and writes them into the rules file.
• 4. When a guideline changes in Ohara, the next task in every repository follows it automatically.
• 5. For existing projects, run "/ohara:review" to report guideline violations.
• 6. Add ".ohara.yml" to a repo to sync its docs to the website on push.
• 7. After code changes, run "/ohara:update" or let the assistant propose doc updates via propose_change.
• 8. Merge code PR; the docs PR is linked and merged, triggering a website rebuild.

证据

Open any three repositories at your company. One uses a service layer, one puts SQL in the route handlers, one has a utils/ folder that does everything.

来源

I built Ohara, an open-source tool that puts every guideline and every doc in one GitHub repository.

来源

Assistants read the guidelines from Ohara when they work, and send doc changes back as pull requests.

来源

On each push to the default branch, Ohara syncs those pages into apps/<repo>/ of the website.

来源