'overhead' 검색 결과

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.

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

Trigger for: FFP IGCE, firm-fixed-price estimate, FFP cost model, proposed FFP rate validation, wrap-rate analysis, Agency BPA rate comparison, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable Firm-Fixed-Price federal estimates using BLS OEWS wages, layered fringe/overhead/G&A/profit, GSA CALC+ positioning, and GSA Per Diem travel. Use for FFP-by-period, FFP-by-deliverable, SOW/PWS decomposition, implied-multiplier analysis, and fixed-price scenario comparisons. Do NOT use for Labor Hour, T&M, or cost-reimbursement IGCEs (use IGCE Builder LH/T&M or IGCE Builder CR). Do NOT use for grant budgets. Requires the bls-oews, gsa-calc, and gsa-perdiem MCP servers.

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

Trigger for: cost-reimbursement IGCE, CR cost estimate, CPFF, CPAF, CPIF, cost-plus estimate, BAA estimate, fixed-fee analysis, award-fee analysis, incentive-fee analysis, proposed CR rate validation, cost-pool buildup, share-ratio scenario, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable CR estimates using BLS OEWS wages, fringe/overhead/G&A/FCCM pools, contract-type-specific fee, GSA CALC+ positioning, and GSA Per Diem travel. Do NOT use for FFP, LH/T&M, grants, or cooperative agreements. Requires the bls-oews, gsa-calc, and gsa-perdiem MCP servers.

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

Build construction project estimates. Generate detailed cost breakdowns with labor, materials, equipment, and overhead.

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

Calculate construction labor rates with overhead, benefits, and productivity factors. Regional rate databases and crew composition.

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

Builds estimates, quotes, and bids for trades and field-service businesses (HVAC, plumbing, electrical, roofing, landscaping, painting, cleaning, remodeling, general contracting, IT/AV installs). Turns a scope into line items with waste factors, burdened labor, materials, equipment, subs, permits, mobilization, contingency, overhead, profit, and tax, then writes a client-ready xlsx (live formulas) and PDF plus an internal cost sheet, with good/better/best options, add-ons, a payment schedule, exclusions, and assumptions. Use whenever someone asks for a quote, estimate, bid, proposal price, or job price, asks "how much should I charge for this job", wants to check a price or margin on a job, or is confused about markup vs margin. Computes deterministically with a script instead of mental math, because models routinely treat a 30% markup as a 30% margin and drop labor burden, waste, and mobilization.

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

Find out which clients and jobs actually make money -- allocate real costs (labor hours, materials, subs, overhead) against what each job billed, and rank every client by true margin. Most service businesses discover their biggest client is their least profitable.

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

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

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

Applies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.

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

Use when reviewing a Rezolus sampler change before merge — a new sampler, a change to an existing sampler's probes/refresh/metrics, or core changes that affect samplers; or whenever a sampler's overhead, cadence, or data source is in question.

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

Think and work like an expert Computer Architecture Researcher. Use when a task calls for Computer Architecture Researcher judgment. Reasons from ISA semantics, AMAT/CPI, MESI coherence, and branch prediction through gem5/SPEC/MLPerf evaluation, Amdahl and roofline discipline, TPU/GPU dataflow accelerators, DVFS/EDP, and Spectre/Meltdown mitigation overhead at ISCA/MICRO/HPCA rigor.

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

You are an expert in Drizzle ORM, the lightweight TypeScript ORM that maps directly to SQL. You help developers write type-safe database queries that look like SQL (not a new query language), generate migrations from schema changes, and deploy to serverless environments with zero overhead — supporting Postgres, MySQL, SQLite, Turso, Neon, PlanetScale, and Cloudflare D1.

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

Art-direct and generate one high-craft minimal-zine bitmap from a landscape, portrait, person, object, product, food, plant, building, interior, photograph, mood, sentence, or article concept. Use when the user wants a standalone poetic poster, editorial cover, visual concept, aesthetic photo upgrade, photo-to-zine restyle, or a subject-aware minimal-zine image without the overhead of a social carousel. Chooses adaptive composition and a physically coherent print process, preserves subject identity, saves the final prompt, invokes the runtime-native image generator, and audits the raster result.

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

Fast-lane prototype skill for the hybrid workflow. Builds a playable prototype in 2-3 days with minimal process overhead. Designed for discovery phase.

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

Keep coding work complete, readable, and proportionate to the task. Use when planning, implementing, debugging, testing, reviewing, or maintaining code, including bounded changes in larger repositories. Avoid unnecessary design and verification overhead. Does not apply to non-code conversation or writing.

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

Execute a trivial task inline — no subagents, no planning overhead

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

Operational efficiency audit — identify waste, redundancy, and friction across processes, tools, and team workflows. Use when asked to "audit our operations for waste", "where are we inefficient", "what tools are we paying for but not using", or "reduce operational overhead".

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

Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to avoid 1-2 minute download overhead on every build.

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

Track and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.

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

Expert C++ developer specializing in modern C++20/23, systems programming, and high-performance computing. Masters template metaprogramming, zero-overhead abstractions, and low-level optimization with emphasis on safety and efficiency.

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

Analyzes Claude Project context budget under the automatic-RAG-by-window model: knowledge files vs. threshold-exempt overhead (Skills, MCPs, CI, Memory). Two modes: Quick Diagnostic and Full Budget Audit. Use when user says "check my context budget," "how much context am I using," "is my project too big," "optimize my token usage," "tier my files," "optimize for RAG," "improve retrieval quality," "should I keep compressing," "am I over-compressing," "should I accept RAG mode." Also trigger on context pressure symptoms: "Claude forgets my instructions," "responses getting generic," "content not found in my knowledge files." Also use when a project audit scores Knowledge Architecture ≤ 3. Do NOT use for content placement decisions (use rootnode-memory-optimization if available), full project audits (use rootnode-project-audit if available), or behavioral tuning (use rootnode-behavioral-tuning if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

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

Fix GraphSnapshot tests blocking CI on every feature PR. Use when: (1) every PR fails CI with "Snapshot mismatch" despite correct behavior, (2) fixing snapshots requires build → regen → commit → wait CI cycle per PR, (3) snapshot test in test/unit/*.test.js glob breaks on any intentional change, (4) pre-push hook runs pnpm build + snapshots:update on every push (2-3min overhead). Solution: move GraphSnapshot.test.js to test/unit/snapshots/ so it's excluded from the *.test.js glob. Run manually via pnpm snapshots:update when needed.

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

Analyze Ascend NPU computation-side profiling data for single-card runs or a selected rank from multi-card runs. Use this skill when the user asks to diagnose computation bottlenecks, AI Core / AI Vector / AICPU hotspots, dynamic shape overhead, block dim issues, redundant TransData/Transpose/Cast, cross-stream waits, frequency/runtime-state issues, or fusion opportunities.

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

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

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