Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Sruja — AI coding harness for repo structure

Stop AI from breaking your repo structure. Sruja scans code, reports structural drift, and plugs into Cursor and other agents via MCP — focus before edits, verify-task after. Optional repo.sruja is for reviewed CI intent and exports (Mermaid/Markdown), not day one.

Why Sruja?

The Problem

Most architecture tools make you choose:

  • Visual-only tools (Draw.io) – no code, no version control, hard to maintain
  • Code-only tools (Mermaid, PlantUML) – no validation, manual diagram updates
  • Stale diagrams – architecture drifts from reality, documentation gets outdated

Our Solution

Sruja gives AI assistants and humans evidence-backed architecture context:

FeatureWhat you get
Structural scanCycles, layer violations, god modules — file-level evidence
Agent harnessMCP + focus + verify-task; host keeps the LLM loop
Optional repo.srujaReviewed intent in Git when teams want strict CI
Built-in validationLint, drift, intent — gates after AI edits
Tier-2 exportsMarkdown, Mermaid — derived views, not the product center

Who It's For

  • Engineering teams who need architecture as part of their SDLC
  • Tech leads who want to enforce architectural standards
  • Platform engineers building guardrails for distributed teams
  • AI agents that need to reason about system architecture

How We Work (Tier 1)

  1. Install CLI — curl -fsSL https://sruja.ai/install.sh | bash
  2. Scan — sruja start -r . then sruja drift -r . --structural-only --advisory
  3. Wire MCP — profile coding; focus before edits, verify-task after
  4. Install harness skill — npx skills add … --skill sruja-harness
  5. Optional — sruja-architecture skill + repo.sruja for reviewed CI intent

We're ultra simple – minimal surface area, no unnecessary apps or frameworks – and highly functional – what we ship works reliably for its scope.

Stack

  • Rust – CLI, engine, LSP, WASM (single language for core)
  • VS Code extension – Edit .sruja files with syntax highlighting and diagnostics
  • Docs – This book (mdBook, Rust-based; no TypeScript/Node)

New here? Quick start: install CLI, run structural drift, wire MCP, install sruja-harness, run verify-task after agent edits. Add sruja-architecture only when you want repo.sruja in Git. For docs, tutorials, and courses, use Navigate; press / or S to search.

Sruja "Show diagram" in code blocks: Run just wasm (or make wasm) from the repo root once, then run just book-serve (or make book-serve, or ./serve.sh from the book directory) so the WASM files are copied into the book output.