1.4만건 · 관련도순
Organize shared build settings, tasks, and package versions across .NET projects. Review Directory.Build file placement and import order, centralize repeated configuration, and retain the settings that belong to individual projects or folders.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props, and Directory.Build.rsp. Only activate in MSBuild/.NET build context. USE FOR: structuring multi-project repos, centralizing build settings, implementing NuGet Central Package Management (CPM) with ManagePackageVersionsCentrally, consolidating duplicated properties across .csproj files, setting up multi-level Directory.Build hierarchy with GetPathOfFileAbove, understanding evaluation order (Directory.Build.props → SDK .props → .csproj → SDK .targets → Directory.Build.targets). Critical pitfall: $(TargetFramework) conditions in .props silently fail for single-targeting projects — must use .targets. DO NOT USE FOR: non-MSBuild build systems, migrating legacy projects to SDK-style (use msbuild-modernization), single-project solutions with no shared settings. INVOKES: no tools — pure knowledge skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides development of ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK, covering server tools, React interfaces, and shared state. This skill is deprecated and directs users to mcp-app-builder.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts. A plan to convert a working legacy/non-SDK project to SDK style or migrate packages.config is a project-system migration, NOT a build-file review: do not activate, even to check scope. Framework/API upgrades are also excluded. Activate for advisory Import/Exists hook and NuGet packed-import questions even without a checkout or failed build; .csproj/.fsproj/.vbproj/.props/.targets conditions; custom-target inputs/outputs; .binlog capture/replay; failing dotnet build/restore/pack/publish or MSBuild-based test builds; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Exclude SDK installation alone, C# refactoring, runtime profiling, assertions after successful builds, and non-MSBuild builds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish build performance baselines and apply systematic optimization techniques. Only activate in MSBuild/.NET build context. USE FOR: diagnosing slow builds, establishing before/after measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update Flask-AppBuilder in Apache Airflow’s FAB provider, including pinned versions, dependency locks, and documentation. Check compatibility tests and review copied security code, with asset and database migration updates when the upstream release requires them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Edit and validate Bazel build settings using conventions specific to CodeQL development. Follow established helpers for packaging and operating system differences, add dependencies with checksums, and check changed targets while respecting the standalone build setup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs/Outputs on custom targets, volatile properties in output paths (timestamps/GUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. Only activate in MSBuild/.NET build context. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi-project builds, multi-targeting builds where project.assets.json conflicts. Diagnoses when multiple projects or TFMs write to the same bin/obj directories due to shared OutputPath, missing AppendTargetFrameworkToOutputPath, or extra global properties like PublishReadyToRun creating redundant evaluations. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, projects, evaluations, properties, double_writes); falls back to dotnet msbuild binlog replay + grep when the MCP is unavailable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze MSBuild binary logs to diagnose build failures. Only activate in MSBuild/.NET build context. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Codebuild — aWS CodeBuild project management and build analysis. Covers build project inventory, build history, build phase details, environment configurations, source credentials, report groups, and build metrics. Use when inspecting build projects, debugging build failures, reviewing build environments, or analyzing build performance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix Native SDK build failures caused by older Zig APIs. Organized by compiler error, this guide shows Zig 0.16 patterns for file access, output, lists, processes, environment variables, clocks, networking, and build configuration.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Interpret MSBuild performance summaries when ResolveProjectReferences appears unusually expensive. Separate time spent waiting for dependent projects from actual task work, then use task self-time rankings to identify a concrete optimization target.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review MSBuild project files and build definitions for correctness and maintainability. Get prioritized findings with concrete recommendations, distinguishing confirmed defects from conditional risks and valid exceptions such as F# source ordering or required imports.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs/Outputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for diagnosing and improving MSBuild project evaluation performance. Only activate in MSBuild/.NET build context. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin/obj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I/O ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with /pp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems. INVOKES: binlog MCP server tools (evaluations, evaluation_global_properties, evaluation_properties, imports, properties); falls back to dotnet msbuild -pp:full.xml for preprocessing, /clp:PerformanceSummary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ChatGPT 안에서 조작하는 앱의 구상부터 React 위젯과 상태 공유 구현까지 안내합니다. 현재는 사용이 권장되지 않으며 후속 스킬로 전환하도록 안내합니다.
Build MCP servers, which expose tools and data to AI agents, with mcp-use. The material covers server functions, reusable prompts, and interactive React widgets, but this skill is deprecated and points to mcp-app-builder as its replacement.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Builds CARLA's ue4-dev branch on Linux, producing the Unreal Engine 4.26 editor, server modules, and an installed Python client package. Fetches required content, optionally compiles native ROS 2 support, and verifies the build against a source-built server.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate files generated during MSBuild into compilation or build output. Address missing generated source and content by choosing target timing, using the configured intermediate directory, and registering files so Clean can remove them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Build or CI failure to triage: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish MSBuild/.NET build performance baselines before optimizing. USE FOR: unranked slow builds; cold, warm, incremental or no-op measurements; before/after comparisons; CI output caching; static graph, artifacts output and dependency graph trimming. Start here before build-perf-diagnostics, incremental-build or build-parallelism. DO NOT USE FOR: known repeated-restore fixes (use eliminate-redundant-restores), non-MSBuild builds. For measured target/task/analyzer bottlenecks, use build-perf-diagnostics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.