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.

Start with your agent Read structure validation docs

assura check

Assura structure check======================Project root: .Config: ./.assura/config.ymlChecked path: .Files checked: 21Directories checked: 11Violations: 1Violations----------apps/web/src/BadName.tsx [medium:file_naming] File 'BadName.tsx' does not match naming convention 'kebab-case'  Blocking: true  Fix: Rename the file to match the effective naming rule, or update files.naming/naming_patterns when the policy is stale.

Filesystem shape

File and directory naming, allowed and required paths, forbidden entries, child counts, and generated-output boundaries.

Inside 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