'boundary' 검색 결과

Normative sufficiency conditions for Initial Boundary Conditions (IBCs) and the SOP for the cheap-tier boundary refinement loop (/boundary). Trigger when: - Crafting, auditing, or refining a prompt/IBC destined for an expensive (architect-class) model or an autonomous worker dispatch. - Evaluating whether a task frame is sufficient to bound an agent walk. - Prompt contains: /boundary, IBC, initial boundary condition, boundary contract, sufficiency conditions, worker prompt, prompt refinement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set a boundary with someone — a friend, family member, coworker, or partner — clearly and kindly, with the actual words and a plan for the pushback. Use when asked how do I set a boundary with, I need to say no to, someone keeps overstepping, or help me set limits with. Produces a read on the boundary you actually need, a warm-but-firm script to state it (without over-explaining or apologizing it away), how to hold it when they push back or guilt-trip, and what to do if they don't respect it — because a boundary you can't state and hold isn't a boundary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Remove the directory editing boundary set by `/freeze` so work can continue across all directories without ending the session. The existing freeze hooks remain registered, and `/freeze` can be used again to restore a boundary.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Continue editing beyond the current directory boundary
• Remove a freeze restriction during a session
• Restore editing access across all directories

Reviews Remix v2 error-handling code for the unified ErrorBoundary, isRouteErrorResponse narrowing, throw-vs-return, root boundary scaffolding, and v1 holdovers (CatchBoundary, useCatch). Use when reviewing routes that throw or define ErrorBoundary in a Remix v2 codebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React Server Components vs Client Components in Next.js: the boundary discipline, "use client" / "use server" directives, Server Actions, what serializes across the boundary, common pitfalls. Use this skill to: - Decide whether a component should be RSC or Client. - Push the "use client" boundary as deep as possible. - Implement Server Actions correctly (auth, validation, revalidation). - Compose RSC and Client components without breaking the model. - Pass data across the boundary safely. Do NOT use this skill for: - General Next.js conventions (see nextjs-conventions). - Specific data-fetching APIs and caching (see nextjs-data-fetching). - Routing (see nextjs-routing).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess existing Google Cloud folders and projects through read-only discovery. Compare resource locations, service usage, and customer-managed encryption requirements with Assured Workloads frameworks, then report suitable options and policy readiness findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess an existing folder or project's policy readiness
• Compare EU or US data boundary frameworks
• Review location, service, and encryption readiness

Use when asked to check whether a figure is audited, which headline numbers sit outside the audited accounts, what 'adjusted' or 'underlying' means in this report, or who is vouching for the numbers in the highlights. For every headline figure in the highlights, chairman's statement and CEO review of an uploaded annual report, states whether it sits inside or outside the audited statements and what was added or removed versus the nearest audited number. Produces a boundary table, the list of figures outside the boundary, and a plain-English summary of who is vouching for what. Educational, not financial advice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and enforce the core/client boundary in multi-client projects. Detects where shared platform code is tangled with client-specific code, finds hardcoded client checks, config files that replace instead of merge, scattered client code, migration conflicts, and missing extension points. Produces a boundary map, violation report, and refactoring plan. Optionally generates FORK.md documentation and restructuring scripts. Triggers: 'fork discipline', 'check the boundary', 'is this core or client', 'platform audit', 'client separation', 'fork test', 'refactor for multi-client', 'clean up the fork'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Examine container isolation in a CTF sandbox, a controlled security challenge environment. The skill checks kernel and runtime conditions, verifies whether an exploit crosses into host context, and preserves a minimal reproducible chain with evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review container isolation settings in a CTF environment
• Check kernel exploit prerequisites
• Verify whether a trigger crosses the container boundary

Investigate prompt injection in sandboxed security challenges by tracing how untrusted text changes an agent’s decisions or tool calls. Build a minimal reproduction and preserve evidence showing where external content crosses into trusted instructions or actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace instructions hidden in retrieved documents
• Investigate agent behavior changed by stored memory
• Reproduce altered tool arguments or secret exposure

Analyze Android apps in a CTF sandbox using static inspection and Frida hooks, which observe or alter running code. Trace request signing, local storage, and Java-to-native boundaries to reproduce a request accepted by the server.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing request-signing inputs and outputs
• Inspecting Java-to-native calls with runtime hooks
• Examining app settings, databases, and token storage

Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing test cases from user stories
• Preparing acceptance test scenarios
• Checking invalid inputs and boundary cases

Provides a reference for reviewing DeFi smart contracts, programs that manage blockchain transactions. It organizes vulnerability types with causes, code examples, search patterns, and fixes to help investigate accounting, permissions, boundary conditions, and pricing logic.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking for accounting inconsistencies and missing permission checks
• Comparing normal and alternative code paths
• Reviewing deadline and array boundary conditions

Design systems made of independently deployable services, or plan how to split an existing application. The skill produces service boundary diagrams and recommendations for communication, data ownership, failure handling, monitoring, and deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning how to split a monolithic application
• Choosing REST, gRPC, or event-based communication
• Defining data ownership and cross-service consistency

Write and review Gradio demos for Hugging Face ZeroGPU. Configure GPU time limits and dependencies, and troubleshoot errors caused by separate worker processes, shared state, concurrent requests, or CUDA package installation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review GPU handlers in a Gradio demo
• Tune GPU duration and quota usage
• Fix PicklingError and stale state across worker processes

Problem-solving strategies for boundary value problems in odes pdes

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identifies non-coding RNAs (tRNA, rRNA, snoRNA, snRNA, riboswitches, sRNAs) using Infernal covariance-model search against Rfam, tRNAscan-SE 2.0 for tRNA, barrnap for rRNA, and ARAGORN for tmRNA, plus the small-RNA-seq boundary for miRNA and the transcript-assembly boundary for lncRNA. Covers the structure-conserved-not-sequence-conserved principle (why BLAST fails), GA-threshold and clan-competition correctness, tRNAscan-SE domain modes and pseudogene flags, rDNA copy-number collapse, and why homology annotation is a recall floor. Use when performing genome-wide ncRNA annotation, choosing the right tool for an RNA class, or interpreting ncRNA counts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React error boundary hierarchy, fallback UI patterns, offline-first fallback, retry mechanisms, and graceful degradation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI integration, reproducible failures, and local execution guidance. This should trigger for requests such as Add fuzz testing to a Java project; Use CATS for API negative testing; Review CI quality gates for API contract robustness; Improve boundary and malformed input test coverage; Run CATS fuzz tests against an OpenAPI contract. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code; Apply A-TRIP testing strategies in Java code; Apply CORRECT boundary condition verification in Java code. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.