944건 · 관련도순
Review JavaScript error handling in source code and browser behavior. Find unhandled asynchronous failures, improve logs with useful context, and add React Error Boundaries, components that handle rendering errors, so failures are handled explicitly and are easier to investigate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze business concepts in a codebase to map business areas and suggest service boundaries. Use Domain-Driven Design, an approach organized around business meaning, to classify responsibilities, assess how closely they belong together, and recommend clearer integration points.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and review how a system is divided into modules, cohesive parts with clear responsibilities. Evaluate data ownership, communication rules, dependencies, and failure handling, and decide when to split or merge parts without assuming a particular technology.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Detects TAD boundaries from balanced Hi-C contact matrices via the diamond-window insulation score (cooltools insulation) and HiCExplorer hicFindTADs, returning a continuous log2 insulation track, valley-prominence boundary_strength, and Li/Otsu-thresholded is_boundary flags across a list of window sizes. Covers the multi-scale window sweep (sub-TAD to compartment-domain), why the boundary is reproducible but the domain partition is not, cross-condition comparison via differential SCORE not differential partition, and the insulation-vs-compartment orthogonality. Use when calling TADs or domain boundaries, computing insulation scores, choosing a window size, ranking boundary strength, comparing boundaries across conditions, or annotating CTCF-backed boundaries; route domain rendering to hic-visualization and boundary-feature overlap to genome-intervals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects TAD boundaries from balanced Hi-C contact matrices via the diamond-window insulation score (cooltools insulation) and HiCExplorer hicFindTADs, returning a continuous log2 insulation track, valley-prominence boundary_strength, and Li/Otsu-thresholded is_boundary flags across a list of window sizes. Covers the multi-scale window sweep (sub-TAD to compartment-domain), why the boundary is reproducible but the domain partition is not, cross-condition comparison via differential SCORE not differential partition, and the insulation-vs-compartment orthogonality. Use when calling TADs or domain boundaries, computing insulation scores, choosing a window size, ranking boundary strength, comparing boundaries across conditions, or annotating CTCF-backed boundaries; route domain rendering to hic-visualization and boundary-feature overlap to genome-intervals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects TAD boundaries from balanced Hi-C contact matrices via the diamond-window insulation score (cooltools insulation) and HiCExplorer hicFindTADs, returning a continuous log2 insulation track, valley-prominence boundary_strength, and Li/Otsu-thresholded is_boundary flags across a list of window sizes. Covers the multi-scale window sweep (sub-TAD to compartment-domain), why the boundary is reproducible but the domain partition is not, cross-condition comparison via differential SCORE not differential partition, and the insulation-vs-compartment orthogonality. Use when calling TADs or domain boundaries, computing insulation scores, choosing a window size, ranking boundary strength, comparing boundaries across conditions, or annotating CTCF-backed boundaries; route domain rendering to hic-visualization and boundary-feature overlap to genome-intervals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review existing DeerFlow skill packages for publication readiness, activation rules, safety boundaries, supporting files, and evaluation evidence. Receive concrete findings and suggested replacement text, with a clear distinction between inspection results and verified runtime behavior.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a repository’s architecture using Ontoly Software Graph, a map of code relationships. Explain module boundaries, package structure, dependencies, and architectural risks, with graph evidence and a stated confidence level.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design APIs and interfaces between parts of an application with clear input and output types, consistent errors, and predictable names. The guidance helps you extend existing interfaces while preserving compatibility for the code that uses them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage TanStack Table v9 state in Octane, including controlled pagination and subscriptions that keep the UI updated. It explains component subscription boundaries, stable external atoms for shared state, and how controlled updates reach the store.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Sort out other people's expectations from actual commitments, reflect on anger, and review living costs against income. This skill helps you examine personal boundaries and the financial room needed to turn down unwanted work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn “today” into explicit local dates and exact UTC time boundaries for daily logs, metrics, or event queries. The bundled script returns readable text and JSON without writing files or accessing the network.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a graph of functions and calls across multiple programming languages to investigate entry points, paths to sensitive operations, and potential impact. Use the results to prioritize security reviews and connect external findings with source code.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore and configure an Nx monorepo, where multiple projects share one repository. Inspect resolved project settings, identify projects affected by changes, and improve project boundaries, build caching, and CI/CD pipelines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and implement a NestJS backend organized into business modules within one deployable application. The skill defines module boundaries, separates data ownership, builds layered code and event communication, and validates isolation through checks and tests.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify responsibilities in a TeamHarness team, including planning, task execution, result acceptance, and runtime administration. Use the role boundaries to identify who owns each action and how participants should handle sensitive information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure Python backends with explicit dependency direction, ports/adapters, and runtime boundaries. Use when shaping project layout, clean architecture, service boundaries, dependency injection, report rendering boundaries, or transport separation in Python.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need framework-agnostic Hexagonal architecture guidance for Java projects - ports and adapters boundaries, application core independence, driving and driven adapters, dependency direction, infrastructure leakage detection, optional architecture tests, and evidence-backed remediation. This should trigger for requests such as Review Hexagonal architecture; Review ports and adapters boundaries; Enforce dependency direction; Add ArchUnit architecture tests; Detect infrastructure leakage in domain code; Improve ports and adapters boundaries. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / API 边界 / 可扩展性 / 演进式架构 — 不含 硬件架构 / 纯企业架构 / 纯 DevOps / 纯安全架构) (software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).) Master OS — automated mastery of software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.