3.6천건 · 관련도순
Run evaluations for Hugging Face Hub models using inspect-ai and lighteval on local hardware. Use for backend selection, local GPU evals, and choosing between vLLM / Transformers / accelerate. Not for HF Jobs orchestration, model-card PRs, .eval_results publication, or community-evals automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trains and fine-tunes vision models for object detection (D-FINE, RT-DETR v2, DETR, YOLOS), image classification (timm models — MobileNetV3, MobileViT, ResNet, ViT/DINOv3 — plus any Transformers classifier), and SAM/SAM2 segmentation using Hugging Face Transformers on Hugging Face Jobs cloud GPUs. Covers COCO-format dataset preparation, Albumentations augmentation, mAP/mAR evaluation, accuracy metrics, SAM segmentation with bbox/point prompts, DiceCE loss, hardware selection, cost estimation, Trackio monitoring, and Hub persistence. Use when users mention training object detection, image classification, SAM, SAM2, segmentation, image matting, DETR, D-FINE, RT-DETR, ViT, timm, MobileNet, ResNet, bounding box models, or fine-tuning vision models on Hugging Face Jobs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python research assistant with Context7 MCP. Use for Python library research, evaluating packages, enforcing strict Python coding standards, or fetching up-to-date library docs via Context7.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Density, whitespace, rhythm, and how space communicates relationships between elements. Use when building layouts, evaluating spacing consistency, or diagnosing why a design feels cramped or empty.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Micro-decision analysis. Catalog the border radii, spacing scales, type sizes, and state coverage that most people miss. Use when auditing design systems, evaluating craft quality, or training granular perception.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read a designer's taste through their typography decisions alone. Type is the fastest taste signal in any design. Use when evaluating design maturity, assessing portfolio quality, or understanding what typography reveals about design thinking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose typefaces based on voice and context, not trends. Use when selecting fonts for a project, evaluating type choices, or understanding what a typeface communicates before anyone reads a word.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Visual weight, attention order, and the decisions that guide the eye. Use when building layouts, evaluating information architecture, or diagnosing why a design feels confusing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
LLM Agent engineering: pattern selection (12-mode matrix), data simulation, convergence iteration. Covers intent routing, function calling, ReAct, MCP, prompt chaining, guardrails, evaluation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and improve SwiftUI runtime performance. Use when diagnosing slow rendering, janky scrolling, high CPU, memory usage, excessive view updates, layout thrash, body evaluation cost, identity churn, view lifetime issues, lazy loading, Instruments profiling guidance, and performance audit requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.