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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。