'bar' 검색 결과

Think and work like an expert Botanist. Use when a task calls for Botanist judgment. Reasons from morphology, floras (FNA/Jepson/eFlora), voucher herbarium specimens (Darwin Core, Index Herbariorum), nomenclature (IPNI/POWO/Madrid Code), APG IV phylogeny, DNA barcoding (rbcL/matK/ITS2), community ecology (vegan adonis2/betadisper, TRY traits), and CITES/ABS ethics; treats vegetative mis-ID, pseudoreplication, PERMDISP confounds, and unvouchered GBIF records as first-class failure modes.

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

Processes environmental DNA metabarcoding data from raw amplicon reads to species occurrence tables using OBITools3, DADA2, and taxonomic assignment against BOLD, MIDORI2, or MitoFish databases. Handles COI, 12S, rbcL, and ITS barcode regions with primer removal, denoising, chimera detection, and contamination filtering via decontam. Includes occupancy modeling (occumb) for detection probability correction. Use when analyzing eDNA from water, soil, or bulk samples for biodiversity monitoring. Not for 16S human microbiome (see microbiome/amplicon-processing).

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

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

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

E-Mail-Entwürfe auf die Merkmale prüfen, mit denen Spamfilter Werbepost erkennen, und empfangene Nachrichten auswerten, die im Junk gelandet sind. Nutze diesen Skill, wenn eine Mail vor dem Versand geprüft werden soll, wenn jemand wissen will, warum eine Nachricht im Spam- oder Junk-Ordner gelandet ist, oder wenn Betreff, Text, HTML und Kopfzeilen einer Mail auf Aufbau- und Inhaltsfehler durchgesehen werden. Prüft unter anderem Linktext gegen Linkziel, defekte Abmeldewege nach RFC 8058, erfundene Thread-Bezüge, sichtbare Seriendruckreste, versteckte Zählpixel, Domainstreuung sowie unbelegte Zahlen und Superlative. Sagt keine Zustellung voraus und ist kein Werkzeug, um Filter zu umgehen. Für die Frage, ob eine Kaltakquise-Mail überhaupt versendet werden darf, ist cold-email zuständig.

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

Kontextspezifische Marketinghypothesen entwickeln, vorprüfen und als messbare Experimente priorisieren. Nutze diesen Skill, wenn Ideen für Kanäle, Kampagnen, Angebote oder Wachstum gesucht werden, wenn eine Ideenliste auf Risiko und Machbarkeit geprüft werden soll, oder wenn aus Vorschlägen Experimentsteckbriefe mit Metrik, Laufzeit, Budget und Stopkriterium werden sollen. Sortiert vor der Bewertung aus, was rechtlich, plattformseitig oder finanziell nicht tragbar ist, und trennt Evidenz von Vermutung. Führt keine Kampagne aus und schaltet keine Anzeigen.

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

Sichtbarkeit, Zitierung und Empfehlung in KI-Antwortsystemen für Deutschland und den DACH-Raum evidenzbasiert prüfen und verbessern. Nutze diesen Skill, wenn eine Marke oder Seite in KI-Overviews, ChatGPT, Perplexity, Gemini oder Copilot auftauchen soll, wenn Crawler-Freigaben für KI-Bots, llms.txt, strukturierte Daten oder die Extrahierbarkeit von Inhalten zu bewerten sind, oder wenn jemand nach AEO, GEO oder LLMO fragt. Trennt Abruf, Zitierung, Erwähnung und Empfehlung, prüft Behauptungen über KI-Rankingfaktoren gegen Primärquellen und verspricht keine Sichtbarkeit. Für klassisches technisches SEO ist seo-audit zuständig.

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

iOS / Android platform-specific code in React Native: Platform.OS, Platform.select, .ios.tsx / .android.tsx file extensions, native modules, permissions, safe area handling, status bar. Use this skill to: - Branch code at runtime via Platform.OS / Platform.select. - Use file extensions for whole-component swaps. - Link and use native modules (Expo SDK or autolinked bare). - Handle permissions across platforms. - Configure status bar and safe area correctly. Do NOT use this skill for: - General project structure (see rn-conventions). - Navigation (see rn-navigation). - Storage (see rn-state-and-storage). - Testing (see rn-testing).

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

Use when configuring ADC sampling time, DMA-driven ADC, calibration, or DAC channel setup on bare-metal MCUs. Not for the DMA stream itself: use dma-baremetal.

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

Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.

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

Use when a task needs the judgment of a Dining Room Attendant or Bartender Helper — triaging which table to bus first during a rush, sequencing a table reset, setting bar-back par levels and restock timing, writing or triaging a side-work checklist, or diagnosing why table turn time or bar throughput has slipped.

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

Use when a task needs the judgment of a Bartender — reconciling actual pour cost against theoretical liquor cost by drink category, deciding whether and how to cut off a guest, pricing a drink menu across well/call/premium tiers, closing out a till and comp log at shift end, or sequencing bar-top service against a backed-up service well.

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

Diagnoses and prevents vbar_control_agent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbar_control_agent crashes, memory cgroup OOMs in serial console logs, tpu-device-plugin metrics checksum corruption errors, or custom TPU metrics collection conflicts on GKE TPU v6e nodes. Don't use for general non-TPU container OOM troubleshooting or standard GKE node lifecycle operations.

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

AI bartender — cocktail recipe, mixology technique, bar setup, menu engineering, food pairing, responsible alcohol service

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

Use when designing, reviewing, or implementing Apple-platform toolbars — current-screen actions vs sidebar navigation, one primary action per screen, overflow menus, protected destructive actions, and keyboard shortcuts.

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

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

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

Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.

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

Regelmäßiger Pflegedurchlauf für ein bereits veröffentlichtes GitHub-Repository (Stufe 1, günstig und oft wiederholbar): zuerst alle Distributionsflächen des Projekts ermitteln (npm, PyPI, Registries, Marketplaces, Stores, Website) und Änderungen später dorthin spiegeln, dann Topics setzen, Privacy-Gate, Dokumente auf Veröffentlichungsabsicht prüfen und interne Planungsdateien nachträglich ignorieren, Banner ergänzen, Aussagen im README gegen den echten Code-Stand abgleichen, Darstellung verbessern, Sprachfassungen der README vervollständigen, Sichtbarkeitsmaßnahmen umsetzen, Eintrag auf der Organisationsseite prüfen sowie offene Issues und Pull Requests abarbeiten. Nutze diesen Skill, wenn ein bestehendes Repo gepflegt, aufgeräumt, aktualisiert, aufgehübscht oder "mal wieder durchgesehen" werden soll, wenn ein Repo veraltet oder unaufgeräumt wirkt, bei Formulierungen wie "Repo-Pflege", "after care", "Nachpflege", "Repo auf Stand bringen", "aufräumen und pushen" oder bei rotierenden Qualitätsrunden über mehrere Repos. Für die tiefe Runde inkl. Rechtscheck und orga-übergreifenden Querverweisen stattdessen full-after-care nutzen; für die Erstveröffentlichung github-repo-care.

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

Use when generating, modifying, explaining, or reviewing TBQ3 Bar-based trading strategies with OnBar, OnInit, OnReady, entries, exits, MarketPosition, stop profit/loss, sizing, slippage, commission, multi-symbol, or cross-period logic.

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

Adds a per-form settings panel to the JetFormBuilder Gutenberg form editor sidebar — registers REST-exposed post meta on the form CPT, enqueues a block-editor JS bundle, and registers a panel via the JFB-specific 'jet.fb.register.plugins' filter using @wordpress/components (TextControl, SelectControl, ToggleControl) and JFB's useMetaState hook for two-way binding to post meta. Use when a companion plugin needs settings that vary per form (e.g. upload folder, file size limit, integration target) instead of (or in addition to) site-wide defaults from the global Settings page. Triggers on mentions of "JFB form sidebar", "JFB form settings panel", "form-level settings", "useMetaState", "jet.fb.register.plugins", "jet-form-builder/editor-assets/before", or scaffolding a JFB companion plugin that needs per-form config.

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

Expert en BaridiMob avancé (paiements CCP, mobile money, factures, transferts, réglementation Algérie)

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

Liquid Glass material best practices for SwiftUI, UIKit, and AppKit on iOS 26+/macOS 26+ (Tahoe) through iOS 27/macOS 27. Use when implementing, reviewing, or migrating to glass: glassEffect, Glass variants (.regular/.clear/.identity), tint, interactive(), GlassEffectContainer, glassEffectUnion, toolbar glass, ToolbarSpacer, scrollEdgeEffectStyle, sharedBackgroundVisibility, tabBarMinimizeBehavior, backgroundExtensionEffect, NSGlassEffectView, UIGlassEffect, Tahoe window chrome, glass accessibility (Reduce Transparency/Increase Contrast), pre-26 Material fallbacks, UIDesignRequiresCompatibility. Also fires on symptoms: glass renders dark or muddy, glass looks like a flat tinted rectangle, glass button doesn't register taps, tap passes through glass, "'glassEffect' is only available in iOS 26.0 or newer", "ambiguous use of 'opacity'", "'cornerRadius' was deprecated", glass looks different in simulator vs device, screenshots of glass UI don't match. For glass animation, morphing, glassEffectID, transitions, Metal shaders, or performance profiling use the liquid-glass-motion skill instead.

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

Implement, review, or improve SwiftUI Liquid Glass effects for iOS 26+. Covers glassEffect modifier, GlassEffectContainer, glass button styles, glass toolbar, glass tab bar, morphing transitions, translucent material, vibrancy, tinting, interactive glass, ToolbarSpacer, scrollEdgeEffectStyle, backgroundExtensionEffect, and availability gating. Use when asked about Liquid Glass, glass buttons, glassEffect, GlassEffectContainer, GlassEffectTransition, glassEffectID, glassEffectUnion, scroll edge effects, or adopting iOS 26 design.

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

Implement, review, or improve data visualizations using Swift Charts. Use when building bar, line, area, point, pie, or donut charts; when adding chart selection, scrolling, or annotations; when plotting functions with vectorized BarPlot, LinePlot, AreaPlot, or PointPlot; when customizing axes, scales, legends, or foregroundStyle grouping; or when creating specialized visualizations like heat maps, Gantt charts, stacked/grouped bars, sparklines, or threshold lines.

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

Build, refactor, or review macOS menubar apps that use Tuist and SwiftUI. Use when creating or maintaining LSUIElement menubar utilities, defining Tuist targets/manifests, implementing model-client-store-view architecture, adding script-based launch flows, or validating reliable local build/run behavior without Xcode-first workflows.

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