'baseline' 검색 결과

Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线

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

Generates a meta-analysis baseline characteristics section (text + table) from raw data. Supports Chinese and English. Use when the user provides baseline data and wants a formatted results section.

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

Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

Establish a security baseline for a website or web app. Use this skill when configuring HTTPS and TLS, setting security headers, planning secrets management, evaluating CSP policies, doing a basic security audit, or hardening a site before launch. Triggers on security headers, HTTPS, TLS, CSP, content security policy, HSTS, secrets management, vulnerability scan, security audit, harden, OWASP, security baseline. Also triggers when a security review is required for compliance or before going live.

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO — baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

Diagnose MSBuild bottlenecks from binlog timelines and Target/Task Performance Summaries after build-perf-baseline establishes measurements. USE FOR: unknown build slowness, RAR >5s, analyzers >30% of Csc, one target >50% of build time, node utilization <80%, excessive Copy tasks, finding restore overhead. DO NOT USE FOR: known repeated-restore fixes (use eliminate-redundant-restores), initial baselines (use build-perf-baseline), incremental rebuilds (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild builds.

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

Apply stable-baselines3 in reproducible local data workflows with version-aware APIs, explicit assumptions, and validation. Use when the user chooses stable-baselines3 or its strengths fit the task.

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

Implement visual regression testing with Playwright screenshots, Chromatic, Percy, and Argos CI. Covers baseline management, diff threshold tuning, dynamic content masking, responsive viewport testing, and review/approval workflows. Use when: "visual test," "screenshot," "visual regression," "pixel diff," "snapshot diff," "update baselines," "Chromatic," "percy snapshot," "argos screenshot." Not for: bulk baseline regeneration after a redesign broke many tests — use selector-drift-recovery; cross-browser rendering matrices — use cross-browser-testing; general Playwright test structure — use playwright-automation. Related: playwright-automation, ci-cd-integration, cross-browser-testing.

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

Learn the target framework from enabled knowledge tools and implement a baseline GPU kernel. Use this skill to understand compute semantics, determine the target platform and framework, search reference implementations, and produce a correct V0 baseline with performance records for later profile-driven optimization.

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO — baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

Create .agent/baseline.md and later compare against it. Use when capturing baseline build/lint/test results or investigating newly introduced findings.

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

Reconcile baseline-versioned files that the `create-baseline upgrade` CLI staged for LLM-assisted semantic merge. Use when the CLI prints "Open Claude Code and run /upgrade-project to reconcile". Reads the stage manifest at `.claude/state/upgrade/<ts>/manifest.json`, reasons through each pending file's three-way delta in main context, writes a reconciled LOCAL, then deletes the stage when every file lands. Supports `--dry-run` (preview the reconciled diff without writing) and a structured "needs-user-input" fallback when the conflict cannot be disambiguated automatically.

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

Generate or repair a project's .gitignore. Composes the baseline must-ignore set (the single source of truth in baseline-ignores.json) with optional gitignore.io enrichment, and merges add-only so existing entries are never lost. Use when a repo has no .gitignore, when the commit-leak guard reports a gap, or when onboarding a new stack. Trigger: "set up gitignore", "fix my gitignore", "ignore node_modules/secrets", "gitignore for <stack>".

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

Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.

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

Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线

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

Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild/.NET build context. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target/Task Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep/cat when the MCP is unavailable.

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

SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".

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

기계 학습이 없는 기존 앱에 추천, 분류, 예측 기능을 추가하는 절차를 정리합니다. 문제와 데이터 확인부터 초기 모델의 학습, 평가, 통합까지 돕습니다.

• 기존 앱에 추천 기능 추가
• 학습 데이터 준비 상태 확인
• 대체 규칙을 갖춘 예측 기능 통합

Turn speedup requests into a measured optimization process with limits on time, cost, and variants. Compare each change against a baseline and correctness checks, then retain the fastest safe option with reproducible commands and measurements.

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

• Speeding up a slow operation using measured comparisons
• Comparing implementation variants under the same input conditions
• Evaluating latency, throughput, or cost per run

Train and evaluate models that estimate human poses from WiFi signals. Compare results against a model that always predicts the average pose, check for data leakage, and report measured improvements with clear evaluation conditions.

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

• Train a pose model using camera labels
• Evaluate pose estimation without a camera at inference
• Compare accuracy against an average-pose baseline

Compare saved benchmark runs over time to track win rate, response times, escalation rate, and LLM baseline costs. Review changes between the first and latest runs, with flags for declining win rates or rising average latency.

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

• Check performance trends before a release
• Review benchmark history after expanding the test corpus
• Track latency changes after an agent-booster upgrade

Run a prepared set of test cases to check agent-booster success rates and routing decisions. Optionally compare results with Gemini or Claude models, then save detailed measurements and summaries as JSON records for later verification.

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

• Checking success rates before a release
• Verifying routing after adding test cases
• Checking performance claims against measurements