'issue' 검색 결과

Use this skill when buying a used tractor or trailer. Covers verifying compliance status, hidden issues, and what to inspect before signing.

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

Use this skill for wheel-end maintenance and lubrication. Covers oil-bath vs grease packs, wheel-end loss issues, and inspection intervals.

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

Use this skill to verify that a driver's medical certificate was issued by a certified examiner on the FMCSA National Registry. Covers the search process, what to verify, and how to handle examiner removal.

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

Use this skill when a driver holds CDLs in multiple states or has resided in multiple states. Covers what MVRs to pull, federal recordkeeping requirements, and state-specific issues.

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

Use this skill when the user asks about CDL driver wellness, retention strategies, what causes driver turnover, common health issues (obesity, hypertension, sleep apnea, mental health), benefits packages, home-time policies, and how to build a culture that keeps drivers. Reference ATA Workforce Development + FMCSA Wellness Initiative.

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

Use when optimizing Docker builds with BuildKit, designing multi-stage Dockerfiles, leveraging cache mounts, building multi-arch images, choosing distroless vs alpine, or signing images with cosign. Triggers: docker build slow, layer cache not hitting, npm install / pip install reruns, multi-stage final image bloat, glibc vs musl issues, RUN --mount=type=cache, BUILDKIT_INLINE_CACHE, registry cache exporters, qemu emulation for arm64, COPY ordering for cache. NOT for Docker daemon admin, Kubernetes-specific image policies, container security scanning workflows, or Buildpacks (different paradigm).

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

Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

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

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

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

The re-measure and standing report of the canonical data model's live DB conformance. Use when asked 'where are we at' on DB drift or conformance, to update the drift numbers, when a drift-audit brief is re-issued, or on /drift-audit. NOT the per-table fix recipe (use matrx-frontend's db-canonicalize-table).

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

iOS-native mobile web UX rules. Use when building any UI component, fixing mobile issues, reviewing responsive code, or touching viewport heights (dvh vs h-screen), safe areas, Dialog vs Drawer, tabs on mobile, touch targets, or input zoom.

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

Create a new find-XXXX preprocessor Python script from scratch (no existing SKILL.md), add configs/<GAMEVER>.yaml skill and symbol entries. Covers xref-string-based and LLM_DECOMPILE-based discovery patterns. Use when a GitHub issue or user instruction specifies a new function to find.

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

One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.

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

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

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

Access Google Search Console for SEO data such as queries, clicks, impressions, rankings, and indexing status across sites. Use when diagnosing search performance or indexing issues.

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

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

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

Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.

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

Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.

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

CSS and UI animation patterns for responsive, polished interfaces. Use when implementing hover effects, tooltips, button feedback, transitions, or fixing animation issues like flicker and shakiness.

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

Troubleshoot and debug LiveAvatar integration issues. Use when the user's LiveAvatar integration isn't working, the avatar is silent, audio is garbled, sessions fail to start, events aren't received, or they're getting API errors.

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

This skill should be used when the user asks to "最小再現環境を作って", "再現環境を構築して", "問題を切り分けたい", "パッケージの不具合か確認したい", "create a minimal reproduction", "isolate the issue", "build a repro environment", "reproduce this bug", "narrow down the cause", "is this a package bug or my code", "このPRの問題を再現して", "this commit broke something", or wants to determine whether a bug is caused by a package, the environment, or application code. Accepts PR URLs, commit hashes, or branch names as input.

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

This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).

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

Expert knowledge of Brev (letter generation) in melosys-api. Use when: (1) Producing letters and decision documents (vedtaksbrev), (2) Understanding Dokgen templates and mapping, (3) Configuring letter recipients and distribution, (4) Debugging letter generation issues, (5) Adding new letter types or templates.

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

Expert knowledge of Person data integration (PDL) in melosys-api. Use when: (1) Working with person data from PDL (Person Data Lake), (2) Understanding identity types (fnr, aktørID, NPID), (3) Working with addresses, family relations, or citizenship, (4) Debugging person data lookup issues, (5) Understanding the mapping between PDL and domain models.

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

Expert knowledge of SED/EESSI integration in melosys-api. Use when: (1) Understanding SED document types (A001, A003, H-series, X008), (2) Debugging SED sending/receiving flows and RINA integration, (3) Working with BUC (Business Use Case) creation and management, (4) Understanding saga steps for SED handling (SEND_VEDTAK_UTLAND, SED_MOTTAK_RUTING), (5) Troubleshooting mottakerinstitusjoner (recipient institutions) issues.

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