katla-architecture-validator

Enforce Katla module dependency boundaries and prevent ash::vk type leaks.

4|Updated Dec 26, 2019

Search Tags:#architecture #validation #rust #code-review #dependency #module-boundaries #vk-wrappers

Ready to run

npx skills add https://github.com/Mik-pe/Katla --skill katla-architecture-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: katla-architecture-validator
Source: https://github.com/Mik-pe/Katla/tree/main/.claude/skills/katla-architecture-validator
Command: npx skills add https://github.com/Mik-pe/Katla --skill katla-architecture-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates and enforces Katla's architectural boundaries by checking module dependencies, preventing forbidden couplings, and ensuring clean module interfaces.

Core Features & Use Cases

Dependency boundary checks across katla_vulkan, katla_ecs, katla_math, and katla_app to prevent forbidden couplings.
Ash type exposure rules enforcement to ensure public APIs do not leak ash::vk types.
Guidance for code reviews and automated validations during architectural changes.

Quick Start

Run the validator against the Katla workspace to enforce architecture rules.

Frequently Asked Questions about katla-architecture-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce module boundaries and prevent forbidden dependencies in a Rust workspace?▼

You validate architectural boundaries by checking module dependencies and public API usage to prevent forbidden couplings. This mechanism ensures clean interfaces and reports actionable failures during code reviews.

Why does my public API leak ash::vk types through vk-wrappers?▼

Ash type exposure rules enforce that public APIs do not leak ash::vk types through wrappers. This validation prevents forbidden couplings and maintains clean module interfaces across your Rust codebase.

Can I use architecture validation for code reviews across katla_vulkan, katla_ecs, katla_math, and katla_app?▼

Yes, architecture validation is applicable to code reviews and automated validations across katla_vulkan, katla_ecs, katla_math, and katla_app. It guides teams on dependency rules and type exposure to enforce boundaries.

What is the best way to check dependency restrictions and type exposure in a Rust project?▼

The best way to check dependency restrictions is to validate dependency rules and ensure no public ash::vk types leak through wrappers. This prevents forbidden couplings and reports actionable architectural failures.

How do I validate architectural changes and prevent forbidden couplings in Rust?▼

You validate architectural changes by checking module dependencies and public API usage to prevent forbidden couplings. This process provides guidance for code reviews and reports actionable failures when boundaries are violated.