Tommkruix/archprint
by Various
Infers architecture rules from your TypeScript repo's real import graph, gates each on statistical evidence, and emits them into the tools you already use (ESLint, dependency-cruis
MCP
Tommkruix/archprint
Added 8 Oct 2026
Overview
Tommkruix/archprint analyzes a TypeScript repository's actual import graph and infers architecture rules, weighting each candidate rule by statistical evidence. It then generates configuration for ESLint, dependency-cruiser, and ts-arch so existing boundaries become enforceable. The tool aims to catch architecture drift automatically rather than relying on documentation.
Best for
Best for
TypeScript teams that want existing code boundaries enforced without writing rules by hand
Use cases
- Generate ESLint rules from existing import patterns
- Convert current module boundaries into dependency-cruiser configs
- Detect architecture drift by enforcing inferred rules
How to use
Install
npx archprint scan . Tools exposed
dependency-cruisereslint-plugin-boundariests-arch
Tested with
Claude Desktop, Claude Code, Cursor
Notes
Tommkruix/archprint analyzes a TypeScript repository’s actual import graph and infers architecture rules, weighting each candidate rule by statistical evidence. It then generates configuration for ESLint, dependency-cruiser, and ts-arch so existing boundaries become enforceable. The tool aims to catch architecture drift automatically rather than relying on documentation.
7 stars on GitHub. Last updated 2026-10-07. Licensed MIT.
Use cases
- Generate ESLint rules from existing import patterns
- Convert current module boundaries into dependency-cruiser configs
- Detect architecture drift by enforcing inferred rules
Pros
- Grounds rules in real code, not aspirational docs
- Exports to multiple familiar linting and architecture tools
- Pure TypeScript implementation
Cons
- Low project maturity at 7 GitHub stars
- Requires a sufficiently large or consistent codebase for statistical inference
- Limited to TypeScript repositories
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Grounds rules in real code, not aspirational docs
- Exports to multiple familiar linting and architecture tools
- Pure TypeScript implementation
Cons
- Low project maturity at 7 GitHub stars
- Requires a sufficiently large or consistent codebase for statistical inference
- Limited to TypeScript repositories
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.
