'esp' 검색 결과

Identifies super-enhancers from H3K27ac, MED1, or BRD4 ChIP-seq using ROSE, ROSE2, LILY, HOMER -style super, and ENCODE dELS cross-referencing. Handles peak stitching parameters, ranking choices, hockey-stick inflection, marker choice (H3K27ac vs MED1/BRD4), and cross-condition comparison with spike-in normalization. Constructs core regulatory circuitry (Saint-Andre 2016) from SE-encoded TFs. Use when identifying cell-identity / cancer-associated regulatory domains, comparing super-enhancers between conditions, identifying master transcription factor networks, or predicting BET-inhibitor responsiveness.

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

Designs adaptive clinical trials including group-sequential (O'Brien-Fleming, Pocock, Lan-DeMets spending), sample-size re-estimation (blinded Friede-Kieser, unblinded Cui-Hung-Wang, Mehta-Pocock promising zone), seamless Phase 2/3 with treatment-arm selection, population enrichment, and response-adaptive randomisation. Covers FDA 2019 Final Adaptive Designs Guidance, FDA 2022 Master Protocols, and ICH E20 Step 2b/3 draft (June 2025, NOT final). Use when planning interim analyses, sample-size re-estimation, or master/platform-trial designs.

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

Performs 3D shape-based similarity searching using ROCS (OpenEye), USRCAT (ultra-fast), Open3DAlign (RDKit), ESPSim (electrostatic), and ShaEP with explicit handling of Tanimoto-Combo (shape + color), shape vs ECFP4 complementarity, conformer-ensemble searching, alignment optimization, and scaffold hopping. Use when searching for shape-mimicking compounds with different scaffolds, identifying bioisosteric replacements, prospective scaffold hopping, or expanding hit series beyond 2D similarity.

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

Use when users need bioinformatics analysis on the NCPGR cluster, especially when converting analysis requests into local software choices, resource plans, and LSF job scripts.

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

Use when a driver has been involved in a crash — regardless of preventability or injury — and the carrier needs to handle the immediate, post-investigation, and return-to-work phases. Covers trauma response, post-accident testing under 49 CFR 382.303, paid time off, retraining, light duty, and re-entry planning.

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

Use this skill when a driver receives an out-of-service (OOS) violation. Covers the immediate compliance, paperwork retention, and CSA impact.

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

Use this skill when the user asks about logging / log hauling operations — short-haul exemption specifics for logging, log truck securement, axle weights, state-by-state logging permits (especially OR, WA, ID, BC), bunk + stake configurations, and how logging fits into FMCSA + state rules. Reference 49 CFR 393 for cargo securement of logs.

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

Use this skill to understand the 6 levels of FMCSA roadside inspections and what each covers. Helps drivers know what to expect and helps carriers respond to inspection types.

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

Use this skill when the user asks about hazardous materials (hazmat) transportation under 49 CFR 171-180 — placarding requirements, segregation tables, hazmat employee training (49 CFR 172 Subpart H), Hazmat Safety Permit (HMSP), shipping papers, packaging groups, emergency response phone, security plans, hazmat endorsement on CDL, and bulk vs non-bulk distinctions. Cite specific 49 CFR section.

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

Use this skill when the user asks about Environmental Health & Safety (EHS) for trucking — fuel spill response, hazmat release reporting, EPA + state environmental reporting, emergency contact information (CHEMTREC), environmental impairment liability insurance, and how to handle a CMV-related environmental incident. Cite 40 CFR + 49 CFR 174.6.

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

Use this skill to respond to an FMCSA audit document request efficiently. Covers organization, file labeling, secure transmission.

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

Use this skill when the user asks about cybersecurity for a trucking carrier — protecting ELD data, customer information, financial systems, EDI integrations, fleet telematics, ransomware risk, vendor / shipper data sharing, incident response, and FMCSA cyber-recommendations. Reference NIST + CISA cybersecurity frameworks.

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

Drafting and iterating sections of The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor (local identity) and Bonded Commons (local coordination), extending coordination across machines and administrative domains. Use when authoring a section, rewriting a section after a redteam/whitehat round, or composing a new chapter. NOT for marketing copy, NOT for the other two papers, NOT for production threat response.

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

Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).

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

Architecture-level decisions for putting a CDN in front of a web app's static assets, API responses, and file/media delivery: provider selection (hyperscaler vs. specialist $/GB), signed-URL / tokenized access for gating private content at the edge, cache invalidation strategy (versioned URLs vs. purge APIs), origin shield / tiered caching for high-miss-rate content, and CDN-layer geo-restriction. Use when deciding which CDN to put in front of a new or growing service, when private/paywalled files need edge delivery without an origin round-trip per request, or when purge/invalidation behavior is being designed rather than debugged. NOT for HTTP cache-control header syntax, Vary, stale-while-revalidate, or surrogate-key purge mechanics (see `cdn-cache-control-headers`); NOT for Cloudflare-specific product configuration once Cloudflare is already chosen (see `cloudflare`); NOT for video-specific transcoding, adaptive bitrate ladders, or streaming-protocol packaging (see `managed-video-streaming-pipeline`).

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

Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs. NOT for service-worker or browser-only caching, Redis/memcached application caching, or edge-function compute.

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

Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).

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

Automatically intercepts and optimizes prompts using the prompt-learning MCP server. Learns from performance over time via embedding-indexed history. Uses APE, OPRO, DSPy patterns. Activate on "optimize prompt", "improve this prompt", "prompt engineering", or ANY complex task request. Requires prompt-learning MCP server. NOT for simple questions (just answer them), NOT for direct commands (just execute them), NOT for conversational responses (no optimization needed).

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

Design and build beautiful, accessible graphical interfaces — web, desktop (Electron/Tauri), and native (iOS/macOS/Android). Use for visual hierarchy and layout, color and theming (light/dark, semantic tokens, WCAG contrast), typography systems, motion and micro-interactions, accessibility, component systems and design tokens, responsive/adaptive layout, and platform-native idioms. The GUI counterpart to beautiful-cli-design. NOT for terminal/CLI output (use beautiful-cli-design) or API/data schemas.

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

Design roadside signs and large-format ads for businesses, especially automotive dealers. Use for pylon signs, monument signs, lot banners, highway billboards, digital roadside boards, service-lane signage, used-car event signs, lease or finance campaign concepts, and other driver-at-speed messaging where legibility, offer hierarchy, and dealer ad compliance matter. Activate on "road sign", "billboard", "dealership sign", "car dealer ad", "pylon sign", "monument sign", "service lane signage", "automotive billboard", "roadside ad", "dealer lease offer", or "drive-by signage". NOT for fabrication drawings, permitting or local sign-code review, web or social ad campaigns, or full brand identity systems.

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

Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Multi-page Lighthouse audit via the MIT-licensed Unlighthouse CLI. Free-tier alternative to running PageSpeed against every URL on a site, no API quota burn, runs locally.

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

Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, CLS prevention, image SERP rankings (via DataForSEO), and image file optimization (WebP/AVIF conversion, IPTC/XMP metadata injection). Use when user says "image optimization", "alt text", "image SEO", "image size", "image audit", "optimize images", "image metadata", "image SERP", "convert to webp", or "image file optimize".

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