“dependency”的搜索结果

Opt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, and service layers. Only activates when ProjectConfig.yaml -> architecture_pattern is "di-first". For simpler projects, use uw-scriptable-object-arch instead.

中文简介正在准备中。当前显示原文说明。

用于规划、实现或审查前端依赖升级、包迁移、lockfile 变更、框架大版本升级、CVE 修复、peer dependency 冲突、ESM/CJS 切换、构建工具兼容性或 CI 验证矩阵；中文触发词包括 依赖升级、版本升级、lockfile、peer dependency、CVE 修复、大版本迁移。

中文简介正在准备中。当前显示原文说明。

Surface and visualize hidden dependencies blocking delivery. Use when the user says "map our dependencies", "what's blocking what", "dependency audit", "why are teams blocked", "we have a bottleneck", "draw out the dependencies", or asks to identify cross-team blockers - even if they don't explicitly say "dependency mapping". Based on "Making Work Visible" by Dominica DeGrandis (time theft, invisible work, flow blockers).

中文简介正在准备中。当前显示原文说明。

Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues.

中文简介正在准备中。当前显示原文说明。

Validates DAG structures, performs topological sorting, detects cycles, and resolves dependency conflicts. Uses Kahn's algorithm for optimal execution ordering. Activate on 'resolve dependencies', 'topological sort', 'cycle detection', 'dependency order', 'validate dag'. NOT for building DAGs (use dag-graph-builder) or scheduling execution (use dag-task-scheduler).

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.

中文简介正在准备中。当前显示原文说明。

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

中文简介正在准备中。当前显示原文说明。

Dependency and license audit: production-level SBOM, lockfile, trust, copy restrictions. Use when implementing, reviewing or testing dependency and license audit for React, Vite, Next.js or Perfect_AI projects.

中文简介正在准备中。当前显示原文说明。

Use when working with Cocoapods — cocoaPods dependency management for iOS/macOS. Covers Podfile configuration, pod publishing, dependency resolution, spec repositories, and pod analysis. Use when managing CocoaPods dependencies, publishing pod specs, resolving version conflicts, or analyzing pod dependency trees.

中文简介正在准备中。当前显示原文说明。

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

中文简介正在准备中。当前显示原文说明。

依存パッケージ（Go modules / npm / Terraform provider / GitHub Actions / pre-commit 等）の アップグレードを、outdated 検出 → CHANGELOG・破壊的変更の確認 → 更新 → lint/test 検証 → コミットまで一連の手順で安全に適用する。「依存更新」「パッケージを上げて」「dependency update」 「go get -u」「npm update」「provider を上げる」等に言及されたときに使用する。

中文简介正在准备中。当前显示原文说明。

Validates typed DAG dependency declarations, returns Kahn linear extensions or generations and residual cycle witnesses, and identifies changed consumers for revalidation. NOT for constructing graphs, scheduling resource capacity, granting effects, or executing nodes.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

中文简介正在准备中。当前显示原文说明。

Audits project dependencies for outdated packages, duplicates, heavy/problematic libraries, security vulnerabilities, and risky version combinations. Generates prioritized reports with security, performance, and maintainability insights, upgrade paths, and safe pinning recommendations. Use when users request dependency audits, package updates, security checks, or dependency optimization.

中文简介正在准备中。当前显示原文说明。

读取MCP配置，在不运行服务器的情况下检查批准后仍可能获取不同代码的包引用，分类npm、Python和Docker版本指定，并建议固定到团队已审阅的版本。

• 批准前检查MCP配置
• 检查latest标签和版本范围
• 向CI添加可重复的配置检查

通过构建、静态分析、测试和安全检查验证Spring Boot改动，并审查代码差异，汇总发布或部署前各项检查是否通过及需要修复的问题。

• 提交Spring Boot拉取请求前检查
• 重构或更新依赖后验证
• 检查测试覆盖率是否达标

帮助配置和排查 Vite 项目，整理配置文件、环境变量、API 转发、插件与构建产物，调查开发服务器和依赖问题，并准备库的发布输出。

• 配置环境变量与开发 API 转发
• 排查开发服务器缓慢或更新失效
• 优化并检查生产构建产物

在实现新功能前，调查项目现有代码、npm与PyPI软件包、MCP servers等方案，比较功能、维护、许可和依赖，帮助决定直接采用、扩展、组合还是自行开发。

• 新增功能前调查现有方案
• 引入依赖前比较软件包
• 寻找外部服务集成工具

为 Quarkus 应用实现并检查身份认证、访问权限和输入验证，同时涵盖机密信息管理、密码哈希、请求限制、审计日志及依赖项已知漏洞检查。

• 为 Quarkus API 添加 JWT 或 OIDC 认证
• 检查角色权限与数据归属验证
• 审查输入验证与数据库查询

在合并或部署Laravel项目前，依次检查环境、代码、测试覆盖率、依赖漏洞、数据库变更、缓存、队列及定时任务；前置检查失败时停止后续操作。

• 创建Laravel拉取请求前检查
• 重大重构或依赖更新后验证
• 部署至预发布或生产环境前检查