architecture-testing

Validates TypeScript layer boundaries, dependency directions, and folder placement against configured rules.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/thomassloboda/ai-stuff --skill architecture-testing-thomassloboda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-testing
Source: https://github.com/thomassloboda/ai-stuff/tree/main/skills/architecture-testing
Command: npx skills add https://github.com/thomassloboda/ai-stuff --skill architecture-testing-thomassloboda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps enforce architectural guardrails in a TypeScript codebase by validating layer boundaries, dependency directions, and placement policies.

Core Features & Use Cases

  • Dependency direction checks to prevent domain -> infrastructure violations
  • Forbidden import checks and barrel-file policies
  • Placement checks to ensure architecture drift is minimized

Quick Start

Run a repository-wide architecture check to validate your TS project against configured rules.

Frequently Asked Questions about architecture-testing

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

FAQPage Schema
How do I enforce layer boundaries and dependency directions in a TypeScript app?▼

You can enforce layer boundaries by running a repository-wide architecture check that validates dependency directions, preventing domain to infrastructure violations and detecting misplaced modules.

What are architecture tests and how do they prevent architecture drift?▼

Architecture tests validate folder placement and dependency rules to minimize architecture drift, ensuring modules stay within designated layers and forbidden imports are flagged.

Can I apply DDD and hexagonal architecture guardrails to an existing codebase?▼

Yes, you can validate domain-driven design and hexagonal projects by loading a configurable rule set and repository structure model to check infrastructure and domain dependencies.

How do I check for forbidden imports and enforce barrel-file policies in TypeScript?▼

You can configure rules to check for forbidden imports and enforce barrel-file policies by validating the repository structure model against the defined architectural guardrails.

Do I need a specific testing harness to validate TypeScript architecture rules?▼

Yes, validating architectural guardrails requires a testing harness to load the configurable rule set and repository structure model into context during activation.

What is the best way to stop domain layers from importing infrastructure code?▼

The best way is to configure dependency direction checks that specifically prevent domain to infrastructure violations by validating import paths against your layered architecture rules.