Integrations

Integrations carry the same repository-owned architecture context into agent harnesses, CI, and visualization tools.

Coding-agent skill

npx skills add yarrasys/yarramate --skill yarramate-architecture

In Claude Code, the product repository is its own plugin marketplace instead:

/plugin marketplace add yarrasys/yarramate
/plugin install yarramate-architecture@yarramate

The maintained skill guides supported agents to orient, author native documents, validate changes, and avoid editing generated output. Durable context stays in the repository, not in a chat session.

GitHub Actions

The product repository ships a composite action that runs check and reconcile — read-only, so it is safe as a required check:

name: architecture
on: pull_request
jobs:
  drift:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - uses: yarrasys/yarramate@main
        with:
          workspace: .yarramate/workspace.yaml

By default the job fails on deterministic correctness errors and on contradicted reconciliation findings; unknown and not-observed findings are reported in the job summary without failing. Pin the version your repository has evaluated.

MCP

yarramate-mcp exposes four read-only tools over stdio — yarramate_ask, yarramate_design, yarramate_check, yarramate_reconcile — each running the same stable CLI in the server's working directory. It is an access layer over the same workspace, not a separate architecture database, and nothing it calls mutates native documents.

LikeC4

The LikeC4 adapter projects selected model subjects into diagrams. Mapping files connect stable native identities to external identifiers; diagram output remains derived.

Graphify

Graphify can gather code evidence for discovery and reconciliation. Treat its output as evidence to review, not as an unquestionable architecture model.

Integration boundary

Harnesses and tools may change. Keep the canonical model in .yarramate/, validate it with the CLI, and regenerate tool-specific views from that source.

Return to documentation home →

These adoption guides are maintained by the website team. Read the normative product documentation →