Skip to content
Agentmart
Submit a tool

dependency-architecture

Map module dependencies and enforce architectural boundaries with dependency-cruiser or a language-specific provider.

Skill by Anders-planck

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/anders-planck-dependency-architecture

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Map module dependencies and enforce architectural boundaries with dependency-cruiser or a language-specific provider. Use when reviewing coupling, detecting cycles, designing layers, validating import rules, or explaining how modules depend on one another.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/dependency-architecture

What's inside

Skill name
dependency-architecture
Description
Map module dependencies and enforce architectural boundaries with dependency-cruiser or a language-specific provider. Use when reviewing coupling, detecting cycles, designing layers, validating import rules, or explaining how modules depend on one another.
License
MIT
Instructions
19 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Dependency Architecture

## Workflow

1. Identify the language, module system, generated paths, aliases, and intended boundaries.
2. Use dependency-cruiser for JavaScript and TypeScript; select a profile-specific provider for other languages.
3. Generate a graph before proposing rules.
4. Distinguish existing violations from newly introduced ones.
5. Add the smallest enforceable rule and a regression test.
6. Report cycles, forbidden edges, orphan modules, and high fan-in/fan-out nodes.

## Guardrails

- Do not infer semantic symbol references from an import graph alone.
- Do not ban dependencies without documenting the intended boundary.
- Exclude generated and vendored code.
- Prefer incremental ratchets when a legacy repository has many violations.

From Anders-planck/orditra, MIT.

More from Anders-planck/orditra

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 12, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Anders-planck

Cite this page

dependency-architecture skill. Agent Mart. https://agentmart.dev/skills/anders-planck-dependency-architecture (last updated 2026-10-24)