'circular dependency' 검색 결과

TypeScript 패키지 내부 파일의 직접 참조와 순환 의존성을 감지합니다. 공개 파일만 진입점으로 쓰도록 설정하고 예제, 검증, 문서까지 마련합니다.

• 패키지 내부 파일의 직접 참조를 막을 때
• 타입 검사와 함께 패키지 경계를 확인할 때
• 복사해서 쓸 패키지 틀을 만들 때

Dependency graph visualization, circular dependency detection, CVE scanning, and license compliance

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review GEODE dependency direction, composition boundaries, circular imports, and optional-dependency loading when changing package or subsystem dependencies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design or refactor backend services with clear layers and dependency rules. Using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design, it separates business logic from databases and frameworks and defines interfaces that support testing without external services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing the structure of a new backend service
• Separating business logic from database and HTTP code
• Resolving circular dependencies between layers

Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and review system architecture, compare databases and structural approaches, and document technical decisions. Included tools generate architecture diagrams, inspect dependencies, and assess project structure to identify circular relationships, excessive coupling, and opportunities for improvement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing monolith and microservices approaches
• Choosing a database for project requirements
• Generating diagrams from an existing project

Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug and fix infinite widget rebuild loops in Flutter apps using Riverpod state management. Use when: (1) Logs show "RAPID REBUILD" warnings or 50+ rebuilds in seconds, (2) UI becomes unresponsive or shows same content repeatedly, (3) Bug only affects slower devices or poor network conditions, (4) Provider watching creates circular dependencies with router/URL state. Covers ref.watch() overuse, watch+listener redundancy, and transitive dependency chains.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug Spring Boot issues systematically. Use when encountering bean errors like NoSuchBeanDefinitionException, circular dependency issues, application startup failures, JPA/Hibernate problems including LazyInitializationException and N+1 queries, security misconfigurations causing 403 Forbidden errors, property binding failures, CSRF token issues, or any Spring Boot application requiring diagnosis with Actuator endpoints and JVM debugging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.