「dependencies」の検索結果

Validate shard load/dependencies, create deep-dive skeletons, update ledger assignments, and generate pipeline tracker

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

Decompose approved architecture design into IA shards and layered spec structure, then validate dependencies and tracking outputs

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

Deploy Azure resources with ARM templates and Bicep. Create modular deployments and manage dependencies. Use when deploying Azure-native IaC.

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

Turns data/commitments.jsonl (flat list) into a who-owes-what-to-whom graph. Surfaces overdue chains and cross-PA dependencies that the flat list hides. Triggers: "what's overdue", "what did X promise", "commitment graph", "who's blocking whom".

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

Use when working with Device42 — device42 IT infrastructure management covering data center infrastructure management (DCIM), application dependency mapping, IP address management, and asset lifecycle tracking. Use when documenting data center rack layouts and power chains, mapping application dependencies and communication flows, managing IP address allocation and subnets, or tracking hardware assets from procurement through decommission.

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

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.

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

Use when working with Cloudformation Deep — aWS CloudFormation deep stack management. Covers stack operations, change sets, drift detection, nested stacks, stack sets, resource imports, template analysis, and rollback troubleshooting. Use when managing complex CloudFormation deployments, debugging stack failures, detecting drift, operating stack sets, or analyzing template dependencies.

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

Use when working with Aws Cdk — aWS CDK infrastructure-as-code management. Covers synth, diff, deploy, bootstrap, context values, construct inspection, and stack dependencies. Use when managing CDK applications, reviewing synthesized templates, comparing deployments, or debugging construct issues.

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

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

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

Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.

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

Review Jupyter notebooks for side effects, dependencies, and safe execution strategy before running or editing them.

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

Scope the real change surface before editing. Use when planning a feature, bugfix, refactor, or review and you need a concrete map of likely touch points, dependencies, tests, and nearby risks.

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

Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602/CS8618/CS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.

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

Performs architectural code reviews focusing on design patterns, duplication, circular dependencies, and refactoring impact. Is the design consistent with the codebase? Use when reviewing code changes for architectural concerns, code smells, or structural issues.

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

Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".

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

Use when facing 2+ independent tasks — "in parallel", "independent tasks", "multiple unrelated failures", "different test files or subsystems" — that can be worked on without shared state or sequential dependencies. Dispatch one agent per independent slice, each with only the context it needs, even when the user did not ask for subagents explicitly.

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

Use when working on any Java or JVM project: plain Java, libraries, CLI tools, Maven/Gradle builds, Spring Boot, Jakarta EE, MyBatis/MyBatis-Plus, JPA/Hibernate, Lombok, Java tests, Java code review, API design, exception handling, security review, refactoring, dependencies, Java version upgrades, javax/jakarta migrations, or JVM runtime troubleshooting such as GC, OOM, thread dumps, deadlocks, high CPU, and performance issues.

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

Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.

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

Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.

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

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

Guide developers through setting up development environments with proper tools, dependencies, and configurations

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

Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.

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

Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.

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