Ln 642 Layer Boundary Auditor

The Layer Boundary Auditor skill scans codebases to identify and report violations of architectural layer boundaries, ensuring strict separation between presentation, business logic, and data access layers. It automatically detects when functions or classes from one layer improperly call methods in another, highlighting specific lines that breach the defined structure.

When to use it

• Enforce strict hexagonal architecture or clean architecture principles during code reviews.
• Identify unintended dependencies between UI components and database operations.
• Validate that business logic remains isolated from external frameworks or data sources.
• Detect "leaky abstractions" where internal implementation details are exposed to higher layers.

Key capabilities

• Analyzes project structure against defined layer boundaries.
• Identifies cross-layer function calls and method invocations.
• Highlights specific code locations violating architectural rules.
• Reports on dependencies that bypass intended abstraction layers.

Example prompts

• "Audit my current project for violations of the three-tier architecture pattern."
• "Find all instances where the presentation layer directly accesses the database layer."
• "Scan this repository and list any functions that call methods outside their designated layer."

Tips & gotchas

This skill requires a pre-defined understanding of your project's specific layer structure; it may not automatically infer boundaries without clear separation in file organization or naming conventions. Ensure your codebase has distinct modules or directories representing layers before running the audit for accurate results.