'framework' 검색 결과

Coordinate compliance work across multiple standards and regulations. Use a company profile to identify relevant frameworks, map shared controls, prepare mock audits, and build a unified evidence checklist showing where documents can be reused.

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

• Starting a compliance program across multiple frameworks
• Planning an annual audit calendar
• Preparing for a certification audit

Analyze CLR activation logs to explain how .NET Framework selects and loads its runtime, the software that executes managed code. Diagnose loading failures, unexpected version choices, installation dialogs, and conflicting activation paths within a process.

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

• Investigating failures to load the .NET Framework runtime
• Explaining why an unexpected CLR version was selected
• Tracing .NET 3.5 installation dialogs or their absence

Prepare an ASP.NET .NET Framework application for Windows Docker containers. Create project-specific build and runtime files, configure environment-based settings and Windows dependencies, and verify that the Docker image builds successfully.

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

• Move an existing ASP.NET application into a Windows container
• Configure COM components and other Windows dependencies
• Read application settings and connection strings from environment variables

Django 앱의 구조, API, 데이터 조회, 캐시 구현과 검토를 돕습니다. 환경별 설정과 업무 로직을 분리하고 불필요한 데이터베이스 조회를 줄이는 예시를 제공합니다.

• Django 구조와 설정 정리
• Django REST Framework API 설계
• 불필요한 데이터베이스 조회 줄이기

Build persistent agents on Azure AI Foundry with the Microsoft Agent Framework Python SDK. Connect functions, search, and MCP tools, preserve conversation context, stream responses, and return data in a defined structure.

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

• Building an agent that preserves conversation context
• Connecting Python functions and hosted search tools
• Displaying responses as they arrive

Build C# applications with .NET 8+, including ASP.NET Core APIs and Blazor interfaces. Get models, endpoints, services, and configuration, with guidance on database access, asynchronous operations, cancellation, authentication, performance tuning, and tests.

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

• Build a REST API with ASP.NET Core
• Implement database access with Entity Framework Core
• Create Blazor components and manage application state

Inspect imports and agent patterns in existing Python code to identify its framework and recommend an Omnigent executor, the component that runs the agent. Explain unsupported frameworks and suggest available next steps.

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

• Identify the framework used by existing Python agent code
• Choose an executor for Claude SDK or OpenAI Agents SDK code
• Check whether a framework has native support

Find explanations, tutorials, configuration guidance, and code examples in official documentation for Microsoft technologies. Choose documentation sources for Azure, .NET, VS Code, GitHub, Aspire, and Agent Framework based on where the relevant material is published.

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

• Find official explanations and setup instructions
• Look up code examples for a specific language
• Research VS Code settings or extension APIs

Build, update, explain, or review Microsoft Agent Framework applications in .NET or Python. The skill guides agent and workflow design using current official documentation and supports migration from Semantic Kernel or AutoGen.

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

• Build an agent application in .NET or Python
• Review agent and workflow design
• Migrate from Semantic Kernel or AutoGen

Generate database relationship diagrams from Entity Framework Core models, mappings, and migrations. Produce D2 diagram source showing tables, keys, relationships, and constraints, with display options for columns and grouping. The d2 CLI can render SVG or PNG images.

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

• Document an EF Core project's database structure
• Review primary keys and foreign key relationships
• Visualize owned types and many-to-many join tables

Build .NET 8 APIs and backend services using C# 12, with clear separation of application responsibilities. The skill covers database access, authentication, API documentation, compilation checks, and integration tests that verify components working together.

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

• Building endpoints with minimal APIs
• Adding database access with Entity Framework Core
• Separating application responsibilities with MediatR

Build Django web applications and REST APIs with Django REST Framework. This skill guides data models, input validation, views, authentication, permissions, and tests, while improving how applications retrieve related records from the database.

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

• Build a REST API with Django
• Design data models and relationships
• Reduce database queries for related records

Plan and configure command and control (C2) systems for red team exercises. Covers major frameworks, communication methods, relay servers, certificate management, and the network or endpoint signals defenders use to detect these systems.

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

• Compare C2 frameworks for a red team exercise
• Plan communication methods and relay infrastructure
• Review C2 detection signals from a defender's perspective

Migrate .NET Framework code that forcibly stops threads to cooperative cancellation, where work checks and responds to stop requests. The skill covers loops, timeouts, blocked threads, and ASP.NET request endings, with cleanup and validation guidance.

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

• Replacing Thread.Abort when moving to .NET 6 or later
• Migrating timeouts and blocked-thread cancellation
• Preserving cleanup from ThreadAbortException handlers

Identify a .NET project’s test framework, project format, and execution platform: VSTest or Microsoft.Testing.Platform. Trace configuration imports and overrides to explain the result, including conflicting settings or differences between target frameworks.

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

• Determine whether tests execute on VSTest or MTP
• Identify the test framework from project configuration
• Investigate conflicting runner settings

Neutral, framework-agnostic decision tree for project kickoff: "which agent / RAG / LLM framework should I reach for?" Synthesizes the ecosystem sections of 7 landmark-project SOPs (LangGraph, LlamaIndex, DSPy, CrewAI, vLLM, Aider, Dify) into one layered rubric. Core stance: frameworks are LAYERS, not competitors — a real project usually combines DSPy (compile) + LlamaIndex (retrieve) + LangGraph (orchestrate) + vLLM (serve), and you choose ONE per layer, not one to rule all. Use when starting any LLM/agent/RAG project, or whenever the "which framework?" question is asked. Deliberately neutral — unlike vendor docs and the LangChain-biased `framework-selection` on skill.sh, this skill has no horse in the race.

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

Review Entity Framework Core code and get improvements for database models, queries, saving changes, and migrations, which track database schema changes. Covers performance, security, testing, and how database access code is organized.

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

• Review database models and relationships
• Improve slow queries and avoid repeated database calls
• Check migrations before production deployment

Review readiness across multiple compliance frameworks using six focused questions. Identify overlapping evidence, missing owners, audit scheduling conflicts, and mock audit findings, then produce a readiness verdict with three actions, owners, and deadlines.

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

• Reviewing readiness before adopting a compliance framework
• Planning the annual audit calendar
• Consolidating evidence across multiple frameworks

Assess existing Google Cloud folders and projects through read-only discovery. Compare resource locations, service usage, and customer-managed encryption requirements with Assured Workloads frameworks, then report suitable options and policy readiness findings.

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

• Assess an existing folder or project's policy readiness
• Compare EU or US data boundary frameworks
• Review location, service, and encryption readiness

Select technologies for AI and machine learning features in .NET 8+ applications. Get task-specific plans or implementation guidance for structured predictions, text generation, document retrieval, tool-using agents, and running pretrained models locally or in production.

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

• Choosing libraries for classification or prediction in .NET
• Adding text generation or summarization to an application
• Designing document retrieval with source-backed AI answers

VS-Enhanced Theoretical Framework Architect with Critique & Visualization Full VS 5-Phase process: Modal theory avoidance, Long-tail exploration, differentiated framework presentation Absorbed A3 (Devil's Advocate) critique and A6 (Conceptual Framework Visualizer) capabilities Use when: building theoretical foundations, designing conceptual models, deriving hypotheses, critiquing frameworks, visualizing models Triggers: theoretical framework, 이론적 프레임워크, conceptual model, 개념적 모형, hypothesis derivation, critique, devil's advocate, 반론, visualization, diagram

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

Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.

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

管理咨询 (管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的价值之辩 (「借你的表告诉你时间」「frameworks 是剧场表演 vs 真洞见」Matthew Stewart《The Management Myth》)、McKinsey 的丑闻 (Purdue 阿片类/独裁政府/ICE/利益冲突, Bogdanich & Forsythe《When McKinsey Comes to Town》)、咨询 vs 自建战略部、generalist 通才 vs specialist 专才之争、AI/GenAI 对初级分析师工作的冲击; (h) 流派 — 战略经典 (Porter 定位学派/五力 vs 资源基础观 RBV vs 蓝海战略 Kim&Mauborgne vs 颠覆式创新 Christensen vs Mintzberg 应急战略批判 planning school); 三巨头气质分野 (McKinsey 事实驱动/CEO 信任/通才, BCG 概念/思想领导力/经验曲线/增长-份额矩阵, Bain 结果导向/NPS 净推荐值/PE 关系/与客户深度绑定)。不含: 投行 M&A/财务顾问 (估值/承销超出范畴)、纯 IT 实施/系统集成 (SI 人力外包)、纯审计/税务、纯人力 RPO/猎头、内部战略部 only (虽相关但本 skill 聚焦专业服务咨询的外部视角)。) Master OS — automated mastery of 管理咨询 (Management Consulting) — 战略与管理咨询的职业认知操作系统，从业者/咨询顾问/想入行者/采购咨询服务的客户视角。覆盖: (a) 第一性张力 — 假设驱动 (hypothesis-driven / answer-first / Day-1 answer) 的「先有答案再验证」⇄ 数据驱动 (data-led / bottom-up) 的「先穷尽事实再归纳」，这行的核心张力是「先射箭再画靶 vs 先画靶再射箭」，资深人偏 top-down 假设树减少 boil-the-ocean，但要时刻防 confirmation bias; 以及更深层的张力 — 「卖洞见 (insight / so-what) vs 卖工时 (analysis / 体力)」，「客户影响 (client impact / 落地) vs 智识严谨 (intellectual rigor / 漂亮 deck)」; (b) 方法论正典 (最标准化、最易蒸出高质量) — MECE (相互独立完全穷尽)、issue tree / logic tree (问题树/逻辑树)、hypothesis-driven problem solving (假设驱动)、Pyramid Principle (Minto 金字塔原理: SCQA 情境-冲突-疑问-回答 + 结论先行 + 自上而下 + 归纳/演绎)、80/20 (帕累托/抓大放小)、so-what (所以呢/洞见提炼)、storyline (故事线/ghost deck 鬼影稿)、driver tree / profit tree、2x2 矩阵、value chain、frameworks (Porter 五力/3C/4P/7S/BCG 矩阵/价值链) 既是脚手架也是陷阱 (套框架 vs 真洞见); (c) 行业结构 — MBB (McKinsey/BCG/Bain 战略三巨头) vs Big Four 咨询臂 (Deloitte/PwC Strategy&/EY-Parthenon/KPMG) vs 精品战略所 (Oliver Wyman/Kearney/Roland Berger/L.E.K./Arthur D. Little) vs 专业/职能 boutique (运营/数字化/PE 尽调); up-or-out (非升即走)、leverage model (杠杆模型: 1 个合伙人带多个 EM/咨询师/分析师的金字塔)、partner/principal/EM(项目经理)/associate(咨询师)/analyst(分析师) 职级; (d) 项目交付模型 (the case/study/engagement) — 提案/SOW (scope of work)、problem definition (问题定义/真问题 vs 表象问题)、workplan (工作计划)、hypothesis tree (假设树)、analysis (分析/建模)、synthesis (综合)、recommendation (建议)、implementation (落地); 客户管理 (steering committee 指导委员会、stakeholder 利益相关方、对齐); (e) 产出物 — the deck (PPT 幻灯片是咨询的母语)、executive summary、action title (行动标题/每页一句话结论)、ghost deck (先搭骨架后填数据)、Excel 财务模型、framework 图; (f) 职业/招聘 — case interview 生态 (案例面试: Victor Cheng LOMS/Case in Point/market sizing 市场估算/估算题/fit 行为面)、网申-笔试-案例面、up-or-out、exit options (退出路径: PE/VC/corp dev 企业发展/战略岗/创业/industry); (g) 争议/批判 — 咨询的

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

Agent Framework Azure Hosted Agents workflow skill. Use this skill when the user needs Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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