'helpers' 검색 결과

Use the DataSciencePython tutorial/example collection through modern self-contained helpers for Python data-science resources, statsmodels logistic regression, scikit-learn Kaggle-style tabular classifiers, and Twitter JSONL extraction.

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

Guides Attention-Gated Networks PyTorch medical imaging workflows for ultrasound classification, attention-gated U-Net segmentation, data layout, CUDA setup, and visualization helpers.

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

Routes Alibi users to the right explanation, confidence, prototype, or optional-backend workflow and points them to the bundled helpers needed to run it.

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

Create, scaffold, or generate Helm charts, Chart.yaml, values.yaml, templates, helpers.

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

Main app Jetpack Compose UI patterns (WooTheme, Fragment hosting, composeView/legacyComposeView helpers, preview annotations, WC components). Use when writing, editing, exploring, debugging, or reviewing Compose UI in the store management app. NOT for POS (WooPos*) code — use the `pos` skill instead.

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

CUMCM 国赛、MCM/ICM 美赛与电工杯数学建模竞赛的端到端协作工作流。Use when a user explicitly works on one of these modeling contests or asks to run/review a modeling-competition paper from problem selection through modeling, solving, robustness, writing, compliance, and final submission review. Provides 10 stages, persistent decision state, competition-specific rules/templates, deterministic scoring helpers, numbered decisions, and Codex/Claude Code handoff. Do not trigger for generic model selection, ordinary data analysis, or non-competition paper review.

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

Structured diagnostic code library for JavaScript/TypeScript. Turns errors and other conditions into typed, machine-readable `Diagnostic` instances with stable codes, docs URLs, and actionable fields. Use this skill whenever the project imports `nostics`, or works with `defineDiagnostics`/`defineProdDiagnostics`, the `Diagnostic` class, diagnostic code registries, or structured error handling. Also covers reporters (`createConsoleReporter`, `createFetchReporter` from nostics/reporters/fetch, `createFileReporter` from nostics/reporters/node, `createDevReporter` from nostics/reporters/dev), formatters (`formatDiagnostic`, `ansiFormatter`, `jsonFormatter`), and Vite plugins (`nosticsStrip` from @nostics/unplugin/strip-transform, `nosticsCollector` from @nostics/unplugin/dev-server-collector). Also use when migrating a library's existing `console.warn`/`console.error`/`warn()` helpers or thrown `Error`s to diagnostics: follow `references/migration.md`.

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

Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.

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

CesiumJS viewer setup - Viewer, CesiumWidget, widgets, Ion token, Scene configuration, SceneMode, factory helpers, geocoders, platform services. Use when initializing a CesiumJS application, configuring viewer widgets, setting Ion access tokens, creating default terrain or imagery, or bootstrapping a 3D globe.

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

You are an expert in @react-three/drei, the companion library for React Three Fiber that provides 100+ ready-made components and hooks for common 3D patterns. You help developers add orbit controls, environment maps, text rendering, HTML overlays, loaders, performance utilities, shaders, and abstractions — eliminating boilerplate and letting teams focus on creative work instead of Three.js plumbing.

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

Use when building game UI (menus, HUD, dialogue box, settings/save screens) on top of Pixi'VN with an external JS framework (React, Vue) or with plain PixiJS components — mounting HTML or PixiJS UI layers over the canvas, navigating between UI screens/routes, theming a shadcn/ui-based template, and connecting UI components to game storage/settings. Covers `canvas.htmlLayers.add`/`get`/`remove` and the PixiJS-only layer helpers `canvas.layers.add`/`get`/`remove`.

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

Complete reference for DTG Base module utilities and helpers. DTGBase is an abstract model providing common utility methods for date/time handling, barcode generation, timezone conversion, file operations, and more.

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

Phase B of a WinForms-to-Avalonia migration: extract UI-independent application behavior, state rules, use cases, and boundary contracts with TDD and no WinForms/Avalonia references. Use only when an explicit migration still has business behavior in Forms or UI helpers, or when the orchestrator routes here. Do not build Avalonia XAML in this phase.

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

Home Assistant YAML configuration and automation. The most common skill for general HA questions. Covers automations, blueprints, scripts, scenes, template sensors, Lovelace dashboards, Mushroom cards, packages, helpers, presence detection, voice Assist, calendar automation, Jinja2 templates, notification patterns, energy monitoring, Matter devices, automation debugging and traces, dashboard sections view, and trigger-based template entities.

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

Creates or improves an Agent Skill by defining a precise trigger boundary, concise procedural instructions, progressive-disclosure references, deterministic helpers, routing evals, and validation evidence. Use when authoring or reviewing SKILL.md, skill metadata, bundled references, or skill packaging. Not for ordinary project documentation or application code.

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

Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace control ({%- trimming, NOT {%- minify -%}), include isolation (always use 'only'), Craft Twig helpers ({% tag %}, tag(), attr(), |attr filter, |parseAttr, |append, svg()), collect() for props and class collections, .implode(), comment headers with ========= separators on component files, and common pitfalls (snake_case, macros as components, hardcoded colors).

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

Reviews Remix v2 loaders and actions for mutations-in-loader, missing validation, leaked server fields, wrong return helpers, v1 useTransition holdovers, and revalidation traps. Use when reviewing loader/action code in a Remix v2 codebase.

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

Configures integration tests with WebApplicationFactory and Testcontainers. Provides test database setup, authentication helpers, and utilities for testing API endpoints with real dependencies.

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

Review touched tests and test-adjacent code for style, Result-returning patterns, panic helpers, unwrap/expect use, and obvious coverage gaps. Use when a broad review needs a dedicated test pass or when the user asks for test-review specifically.

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

What things get called. A file is named after its export in the project's case convention, a suffix is a resolution instruction rather than decoration, an index file only re-exports, and some symbol names are always wrong (utils, helpers, V2, Enhanced, New). Covers learning a tree's local vocabulary before adding to it, test and platform-variant naming, and the per-language conventions. Use when creating a file or directory, naming a test file, adding a platform variant, or when a name has to change. Triggers - "what should I call this file", "where does this file go", "naming convention", "kebab or camel", "name this test".

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

Drive the Voxt UI from Codex — chrome-devtools MCP setup, debugUI helpers, fast multi-user sign-in

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

Use for .NET application development involving services, managers, dependency injection, Microsoft.Extensions.Hosting, dependency direction, MiniDb persistence, DTOs, Mapster mapping, shared entities/helpers, MCP tools, module workflows, solution analysis, cancellation, logging, and logic shared by CLI and Blazor.

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

How to author one new tdmcp MCP tool the house way — the file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport over executePythonScript), the result helpers (errorResult/guardTd/jsonResult/structuredResult), fail-forward error handling, ESM/.js + Biome style, and the offline msw unit test that proves it. Load this whenever building, extending, reviewing, or testing a tdmcp tool file under src/tools/** (and its test under tests/unit/**). Use it for every Phase-13 / v0.5.0 feature-build tool and any re-run after a gate failure.

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

Vue 3 form patterns: native v-model, vee-validate + zod (most common), VueUse helpers, defineModel for custom inputs, controlled vs uncontrolled, field arrays, multi-step wizards. Use this skill to: - Wire vee-validate with a validation schema (zod / yup). - Build custom form components with defineModel (Vue 3.4+). - Implement multi-step forms. - Handle async validation. - Integrate forms with TanStack Query mutations or Pinia actions. Do NOT use this skill for: - General SFC conventions (see vue-conventions). - State management (see vue-state-management). - Routing (see vue-routing). - Testing forms (see vue-testing).

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