Examples

Start from a project shape that resembles yours.

Assura’s examples move from a broad repository contract into specific software, documentation, migration, CI, and agent workflows. Each example points to the exact technical guide behind it.

example index
software/       agent-ready baselinemonorepo/       package and app boundariesmarkdown/       sections and content modelsmigration/      LS-Lint configurationci/             hooks and required checksintelligence/   facts, references, context

Software projects

Start with structure, naming, generated output, agent guidance, hooks, and CI.

Document projects

Validate Markdown, frontmatter, source custody, references, and traceability.

Existing policy

Migrate LS-Lint naming rules or connect current custom constraints without replacing specialized linters.

01

Agent-ready software project

A broad baseline with AGENTS.md guidance, project-local skills, advisory feedback, and a merge gate.

02

Monorepo structure

Separate shared policy from app, package, docs, and generated-output boundaries.

03

Markdown-heavy repository

Treat headings, frontmatter, links, and content models as deterministic project policy.

04

Requirements and evidence

Connect documents and references so missing traceability is visible instead of inferred during review.

Agent setup

Set up this project with Assura.

Copy one instruction to the coding agent already working in your project. It will establish the baseline, define the expected shape, and verify it.

One command assura agent onboard .
Agent goal Inspect, constrain, verify
  1. Inspect manifests, tooling, generated output, and the intentional layout.
  2. Define project-owned rules for the expected stack. Close stable scopes so unexpected paths fail; preserve legitimate paths and ask only where evidence is ambiguous.
  3. Verify with assura review and assura check --format agent.
Installation details public release
curl -fsSL https://assura.dev/install.sh | sh

The copied setup instruction includes this command.