component-boundary-identifier
From the author
Identifies boundaries between modules or components in software systems through static code analysis and dependency detection. Use when Claude needs to analyze software architecture, identify module boundaries, detect boundary violations, find circular dependencies, or assess component coupling. Supports Python (packages and imports) and Java (packages and dependencies). Trigger when users ask to "identify boundaries", "find component boundaries", "detect boundary violations", "analyze module structure", "check architecture", or "find circular dependencies".
Install
npx skills add ArabelaTso/Skills-4-SE --skill component-boundary-identifier -a claude-code
Installs to .claude/skills/component-boundary-identifier/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- code-communitiesathola/claude-night-marketDetects architectural clusters and coupling boundaries via community detection on the code graph. Use when identifying module groupings or refactoring targets.Engineering★ 348
- dependency-resolverArabelaTso/Skills-4-SEIdentify, analyze, and manage software dependencies before deployment. Use this skill when preparing applications for deployment, resolving dependency conflicts, updating dependencies, auditing security vulnerabilities, managing package versions, or troubleshooting dependency-related issues. Supports multiple package managers (npm, pip, maven, cargo, go mod, composer) and provides actionable recommendations for dependency management.Security★ 260
- cxc-dev-architecturelidge-jun/codexclawUse for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.Planning★ 52
- architectureboshu2/agentopsCompare interface designs and find structural friction. Use when: a change spreads across modules or a boundary is unclear. For code changes, use Refactor.Planning★ 452
- code-understandAr9av/obsidian-wikiMap the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.Engineering★ 3.7K
- component-inventorykostja94/bricksInspect an existing project to discover pages, components, inline UI, real content, and conditional consumers, then create or refresh its component system document. Use before component governance or when asked which pages use which components.Design★ 192
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in