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

Description and use

Multiple repositories with disparate guidelines lead to inconsistency. Ohara centralizes all rules and docs, enabling assistants to read live guidelines and auto‑update documentation, ensuring uniformity and reducing duplication.

Problem

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

Outcome

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

Workflow

• 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.

Evidence

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.

Source

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

Source

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

Source

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

Source