Filesystem shape
File and directory naming, allowed and required paths, forbidden entries, child counts, and generated-output boundaries.
Repository validation
Validate the project from the top down.
Assura starts with stable, language-agnostic repository policy: where files belong, how paths are named, what must exist, how large structures can grow, and which content-level rules apply across file types.
$ assura check
files checked 28
dirs checked 20
violations 6
! apps/web/src/BadName.tsx file_naming
! AGENTS.md agent_guidance:agent_project_guidance
! AGENTS.md agent_guidance:agent_project_guidanceInside every file type
Language-agnostic line limits, Markdown sections, frontmatter, references, and content rules beyond filesystem operations.
Reusable policy
Shared rules and inherited structure reduce duplicated configuration across packages, apps, docs, and monorepo areas.
Start broad
Establish project-level health and safety before attaching runtime or framework-specific tools.
Return repair context
Findings identify the path, rule, severity, blocking state, and configured expectation so agents can choose a focused repair.
Use the same contract everywhere
Run the configured policy locally, in hooks, in CI, and through bounded agent reports.
Extend by layer
Specialized language, content, release, or domain constraints attach after the broad repository contract is stable.
Continue