'driven' 검색 결과

Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.

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

• Checking whether a feature fulfills its requirements
• Comparing implementations of the same specification
• Auditing unit and end-to-end test coverage

Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Orchestrates specialist agents for planning, entity creation, and code generation. Use it when user asks to build, retrieve, or update a page in an existing Microsoft Power Apps model-driven app. Use it when user mentions "generative page", "page in a model-driven", or "genux". Do not use it for a generic or standalone React or web app, website, or dashboard (including a Power Apps code app), for Power Pages, canvas apps, or Power Automate, or when the user rules out Power Platform, Dataverse, or model-driven apps (for example "no Power Platform"). A generative page only runs inside a model-driven app, and this skill cannot scaffold a standalone project. This skill stands alone and does not require /app-builder — but if the user wants a whole app built (tables, forms, views, sitemap) rather than pages for an app that already exists, use /app-builder instead.

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

Develop features and fix bugs through test-driven development: write a failing test, add minimal code to pass, then clean up. The workflow assigns agents to planning, test writing, implementation, and validation of the full test suite.

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

• Building a new feature with tests written first
• Adding a regression test before fixing a bug
• Testing boundary conditions and error behavior

Design backend systems with clear boundaries between business rules, databases, and external services. Use Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to organize new applications, refactor existing code, and make core logic easier to test.

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

• Planning the structure of a new backend
• Refactoring tightly coupled applications
• Testing business rules independently of external services

管理咨询 (管理咨询 (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) 争议/批判 — 咨询的

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

Orchestrator for spec-driven development (SDD) — the discipline of writing executable specs before code, with a constitution above them and a hard cross-check gate before implementation. Mirrors GitHub Spec Kit / AWS Kiro slash-command shape. Routes /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement to the right leaf skill. Load when the user says "spec-driven development", "SDD", "specs-first workflow", "run the spec loop", "/specify a feature", "/plan from this spec", "do spec-driven for this", "GitHub Spec Kit workflow", "Kiro workflow", or invokes any SDD-style slash command. Single entry point for all SDD workflows.

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

Use this skill for internal architecture work around config-driven, registry-driven, and pattern-driven feature design in the nuxt-ui-tools repository. Covers how to organize variant-heavy features, where to put implementations, and how to keep both internals and public APIs standardized.

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

Build AWS applications that run without managing servers directly. Covers Lambda functions, APIs, DynamoDB storage, message-driven workflows with SQS/SNS, deployment through SAM/CDK, and reducing the delay when a function starts for the first time.

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

• Building an API with Lambda and API Gateway
• Developing an application backed by DynamoDB
• Designing event-driven workflows with SQS/SNS

Plan backend architecture using Clean Architecture, Hexagonal Architecture, or Domain-Driven Design. Clarify business boundaries, choose a suitable structure, define how modules depend on each other, and outline migration steps and validation checks.

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

• Design the structure of a new backend
• Reduce tight coupling in a monolithic application
• Define shared architecture standards for a team

Design or refactor backend services with clear layers and dependency rules. Using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design, it separates business logic from databases and frameworks and defines interfaces that support testing without external services.

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

• Designing the structure of a new backend service
• Separating business logic from database and HTTP code
• Resolving circular dependencies between layers

Build websites with layered depth, scroll-driven transitions, and animated text using static images, CSS, and JavaScript. The skill covers asset inspection, visual planning, implementation, and checks for performance and motion accessibility.

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

• Build a product landing page with scroll-driven effects
• Add layered depth and animated text to an existing site
• Inspect image transparency and plan asset placement

Guide an approved defect fix from reproduction on current main through testing and independent validation. Record evidence for each operator workflow, track change size and rollback scope, and apply review records when receipt-driven development is enabled.

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

• Reproducing approved defects before implementation
• Recording runtime evidence for CLI and lifecycle flows
• Splitting fixes by cause and rollback scope

Create HTML-based videos with animated titles, synchronized captions, narration, music-driven effects, and scene transitions. Structure scenes and timing, define a visual style, and check layouts, text contrast, and animation choreography within HyperFrames.

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

• Creating animated title cards and overlays
• Adding captions synchronized with audio
• Generating narration and music-driven animation

Build features or fix bugs through test-driven development: write one failing test, add enough code to pass, then refactor. Focuses on observable behavior through public interfaces, helping tests remain useful when internal code changes.

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

• Building a feature one tested behavior at a time
• Reproducing a bug with a failing test before fixing it
• Designing integration tests around public interfaces

Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows, generative page intents for overview/dashboard surfaces, and an app module + sitemap. Runs an interactive authoring flow with plan approval and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", "add a business process flow", or "edit/add to my app". Do not use it for a generic web or React app or website, Power Pages, canvas apps, or Power Automate, or when the user rules out Power Platform, Dataverse, or model-driven apps (for example "no Power Platform"). This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpage instead.

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

Rank content angles by engagement data, competition level, and platform fit. Data-driven angle selection instead of guesswork. Use this skill when the user has a keyword or product and needs to decide WHAT to create, which angle to take, which format to use, or which platform to target. Triggers on: "what angle should I use", "rank content ideas for [keyword]", "best angle for [product]", "which content idea will perform best", "help me pick an angle", "what should I write about", "content angle for [topic]", "rank my content ideas", "which approach will get the most views", "data-driven content planning", "angle ranker", "content scoring", "which hook should I use", "compare these content ideas", "prioritize my content angles", "what video should I make".

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

Conduct proactive, hypothesis-driven threat hunts — search SIEM / EDR / logs for adversaries who haven't tripped an alert yet. ATT&CK-driven, hypothesis-based methodology. Use when the user mentions 'threat hunting,' 'proactive hunt,' 'TaHiTI,' 'PEAK framework,' 'MITRE ATT&CK hunt,' 'hypothesis-driven hunt,' 'hunt hypothesis,' 'living off the land,' 'LOLBins,' 'beaconing,' 'lateral movement detection,' 'data staging,' 'persistence hunting,' or wants to find threats that have evaded existing detections.

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

Provides Event-Driven Architecture (EDA) patterns for Spring Boot — creates domain events, configures ApplicationEvent and @TransactionalEventListener, sets up Kafka producers and consumers, and implements the transactional outbox pattern for reliable distributed messaging. Use when implementing event-driven systems in Spring Boot, setting up async messaging with Kafka, publishing domain events from DDD aggregates, or needing reliable event publishing with the outbox pattern.

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

Applies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.

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

Plan, implement, or review test driven development work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests test driven development work.

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

Plan, implement, or review spec driven development work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests spec driven development work.

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

Implement consumer-driven contract testing with Pact-JS (v16). Covers consumer test writing, broker-driven provider verification, Pact Broker setup, can-i-deploy as a deployment gate, webhook-triggered verification, pending pacts, and schema-first vs consumer-first approaches (OpenAPI/Ajv, Schemathesis). Use when: "contract test," "Pact," "consumer-driven," "API contract," "provider verification," "can-i-deploy." Not for: stubbing or mocking a dependency to isolate a test — use service-virtualization; general REST/GraphQL endpoint assertions against your own API — use api-testing. Related: api-testing, service-virtualization, ci-cd-integration, test-environments.

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

Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.

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

Validate system resilience through controlled fault injection. Covers hypothesis-driven chaos experiments, failure injection types (network, service, infrastructure, dependency), LitmusChaos/Chaos Mesh/AWS FIS/Gremlin/toxiproxy tooling, automated abort gating, game day planning, and progressive chaos adoption. Use when: "chaos engineering," "fault injection," "resilience test," "game day," "failure recovery," "system reliability," "blast radius." Not for: safe rollout flags/canary/dark launch during a release — use testing-in-production; designing new tests from production telemetry — use observability-driven-testing. Related: testing-in-production, observability-driven-testing, performance-testing, release-readiness, test-environments.

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