「coupling」の検索結果

Implement event-driven communication using BlueprintEventBus for cross-module coordination. Use this skill when modules need to communicate without tight coupling, broadcasting domain events (task.created, member.added), subscribing to events with proper lifecycle management, and implementing event-driven workflows. Ensures events follow naming conventions ([module].[action]), include Blueprint context, and use takeUntilDestroyed() for automatic cleanup.

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

Use when designing event-driven workflows, decoupling services, implementing fan-out patterns (one trigger, many downstream handlers), implementing idempotent event handling with IDs (24-hour dedupe window), or handling at-least-once delivery from external sources like Stripe webhooks. Covers Inngest event schema, payload format, naming conventions, IDs for idempotency, the ts param, fan-out patterns, and system events like inngest/function.failed.

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

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

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

Detects architectural clusters and coupling boundaries via community detection on the code graph. Use when identifying module groupings or refactoring targets.

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

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.

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

Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.

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

Plans an architecture-driven change to code that already exists: module boundaries, type responsibilities, layering, coupling, and the public surface a revision moves. Produces a buildable change plan that names the types, modules, and methods involved and records the surface delta each change makes. Use when the user wants to plan, scope, or sequence a restructure, extraction, split, consolidation, responsibility shift, or API revision of existing code, including "these responsibilities are wrong, plan the fix". Does not assess an area and stop at findings — use architectural-analysis. Does not specify new behavior — use plan-a-feature. Does not diagnose a bug — use investigate. Does not write the code — use refactor to restructure it or tdd to build it.

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

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

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

Evaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.

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

Think and work like an expert Limnologist. Use when a task calls for Limnologist judgment. Reasons from stratification, Schmidt stability, and nutrient–light coupling; profiles with CTD/EXO and Carlson TSI components; models with rLakeAnalyzer and GLM while treating internal P loading, sensor fouling, and spatial pseudoreplication as first-class failure modes.

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

Think and work like an expert Heliophysicist. Use when a task calls for Heliophysicist judgment. Reasons from MHD, magnetic topology, reconnection, and IMF Bz coupling through SDO/HMI magnetograms, DEM and NLFFF analysis, coronagraph GCS fitting, and WSA-ENLIL/EUHFORIA ensembles while treating LOS foreshortening, AIA stray light, force-free NLFFF breakdown, and Dst/SYM-H saturation as first-class failure modes.

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

Think and work like an expert Horticulturist. Use when a task calls for Horticulturist judgment. Reasons from plant-environment-cultural coupling, source-sink carbon partitioning, and chilling/photoperiod thresholds through rootstock-scion matching, DLI/VPD and substrate EC/pH targets, Dynamic/Utah chill models, and CA/MA postharvest setpoints while treating blossom-end rot, bitter pit, tipburn, storage scald, and MRL/PHI breaches as first-class failure modes.

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

Think and work like an expert Electronics Engineer. Use when a task calls for Electronics Engineer judgment. Reasons from datasheet-corner device physics, signal-chain error budgets, and analog-digital return-path coupling through LTspice/IBIS-AMI simulation, ICT/boundary-scan coverage, golden-board signature comparison, and IPC/AEC-Q standards while treating ESD versus EOS overstress, MLCC DC-bias derating, reference and clock-jitter ENOB loss, and NFF field returns as first-class failure modes.

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

Think and work like an expert Cosmologist. Use when a task calls for Cosmologist judgment. Reasons from Friedmann/ΛCDM, r_s and transfer functions, and multi-probe inference (Planck CMB, DESI BAO, lensing, Pantheon+ SNe) through CAMB/CLASS, Cobaya, and GetDist while treating photo-z–IA coupling, CMB foreground pipelines, H0/S8 tensions, and emulator extrapolation as first-class failure modes.

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

Think and work like an expert Communications Engineer. Use when a task calls for Communications Engineer judgment. Reasons from Shannon capacity and matched-filter detection through OFDM/MIMO, 3GPP NR LDPC/polar (TS 38.212), TR 38.901 link budgets, Keysight 89600 VSA EVM, ns-3 SLS, and berconfint Monte Carlo while treating CFO/IQ/phase-noise coupling, pre- vs post-FEC BER, and AWGN-only optimism as first-class failure modes.

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

Think and work like an expert Biophysical Chemist. Use when a task calls for Biophysical Chemist judgment. Reasons from free energy landscapes, binding equilibria (K_d, ΔG = ΔH − TΔS), and probe–system coupling through ITC, SPR/BLI, smFRET, AUC, and global fitting (KinTek, SEDFIT) while treating probe perturbation, mass-transport-limited kon, aggregation-driven avidity, and two-state melting violations as first-class failure modes.

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

Think and work like an expert Chronobiologist. Use when a task calls for Chronobiologist judgment. Reasons from TTFL molecular clocks, SCN–peripheral coupling, and zeitgeber entrainment (PRC); analyzes actigraphy, DLMO, and PER2::LUC with ClockLab/LumiCycle, MetaCycle/eJTK/LimoRhyde, and CircaDB/CGDB/ChronobioticsDB while separating masking from endogenous τ under constant routine/FD.

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

Think and work like an expert Biological Oceanographer. Use when a task calls for Biological Oceanographer judgment. Reasons from light-nutrient-grazing coupling, the microbial loop, and size-structured export through CTD/MOCNESS sampling, 14C and O2/Ar production with 234Th export flux, imaging and flow cytometry enumeration, and SILVA/PR2 metabarcoding while treating spatial patchiness, diel-migration tow aliasing, CDOM-biased chlorophyll algorithms, and eDNA-detection-as-abundance as first-class failure modes.

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

Think and work like an expert Chemical Oceanographer. Use when a task calls for Chemical Oceanographer judgment. Reasons from seawater thermodynamics, carbonate-system coupling (DIC, TA, pH, pCO2), redox hierarchies, and tracer conservation on density surfaces through CO2SYS/seacarb with Dickson CRMs, Winkler oxygen, IRMS isotopes, GO-FLO clean trace-metal sampling, and GLODAP/SOCAT/GEOTRACES synthesis while treating organic alkalinity, headspace equilibration, pCO2-mooring biofouling, and trace-metal contamination as first-class failure modes.

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

Think and work like an expert Biogeochemist. Use when a task calls for Biogeochemist judgment. Reasons from coupled C/N/P/S redox cycles through TEAP zonation, porewater Rhizon-peeper sampling, δ13C/δ15N/δ34S tracers, chamber and eddy-covariance fluxes, and Century/DayCent SOM modeling while treating porewater O2 contamination and nitrification-denitrification coupling errors as first-class failure modes.

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

AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Build and maintain digital twins - virtual representations of physical systems that synchronize with real-world counterparts for monitoring, prediction, and optimization. Use when "digital twin, virtual model, real-time synchronization, physical-virtual coupling, predictive maintenance, asset modeling, system replica, live simulation, " mentioned.

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

You are an expert in Amazon EventBridge, the serverless event bus for building event-driven architectures. You help developers route events between AWS services, SaaS applications, and custom microservices using event rules, patterns, transformations, dead-letter queues, and scheduling — decoupling producers from consumers with content-based routing that scales automatically.

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