'solutions' 검색 결과

Route product questions to a specialist for prioritization, research, analytics, experiments, or implementation. Support recurring discovery by tracking interviews and assumption tests, checking how customer needs connect to proposed solutions, and returning results with a concise digest.

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

• Prioritizing features with an explicit framework
• Planning product experiments and sample sizes
• Tracking weekly interviews and assumption tests

Summarize customer interview transcripts into a consistent Markdown document. Capture what customers want to accomplish, their current solutions, satisfaction and problems, notable findings, and follow-up actions with dates and owners when available.

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

• Summarizing customer interview transcripts
• Organizing satisfaction and problems with current solutions
• Sharing findings from product discovery interviews

Generate improvement ideas for an existing product from product management, design, and engineering perspectives. Produce five ideas per perspective, then select the top five based on goals, potential impact, feasibility, and differentiation, with reasons and assumptions to test.

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

• Brainstorming features for an existing product
• Exploring solutions to a customer problem
• Comparing ideas from three professional perspectives

Find recurring questions in resolved Plain support tickets that existing knowledge articles do not cover. Draft articles from actual resolutions, avoid previously drafted topics, and open a pull request for human review.

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

• Find undocumented topics among recurring support questions
• Draft knowledge articles from resolved support tickets
• Run weekly checks without duplicating pending article drafts

Develop varied ideas for names, writing angles, and problem solving by exploring five candidates internally and presenting the strongest. It also expands small example collections into diverse datasets for evaluation, training, or testing.

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

• Finding a distinctive product name
• Developing a fresh angle for a blog post
• Exploring solutions to a technical problem

Clarify a problem before choosing solutions through structured questions about team assumptions, affected people, and overlooked stakeholders. Produce a completed problem canvas, a refined problem statement, and a question to guide solution exploration.

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

• Clarifying why users abandon onboarding
• Reframing a stakeholder's feature request
• Aligning teams on the problem to solve

Create .NET projects from templates and align them with neighboring projects and centralized package versions. Validate options, connect projects in a solution, and build the result to check that the generated structure works.

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

• Creating a new .NET application from a template
• Combining an API, tests, and a library in one solution
• Adding a new project with centralized package versions

Explore design options in Python when goals such as cost and performance compete. This skill guides optimization, constraint handling, and visualization of trade-offs, then helps compare candidate solutions using stated preferences.

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

• Comparing designs with competing cost and performance goals
• Finding solutions that meet design constraints
• Comparing optimization algorithms on benchmark problems

Choose methods for differential equations with conditions specified at boundaries. The skill guides problem classification, shooting methods, finite differences, numerical solvers, and eigenvalue problems, with command examples for exploring solutions and checking numerical accuracy.

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

• Choose a method for a two-point boundary value problem
• Build finite difference equations
• Review Sturm-Liouville eigenvalue problems

Solve optimization problems with equality constraints, inequalities, or variable bounds. Guides method selection, symbolic equations, and optimality checks, with SciPy examples for finding numerical solutions that respect the stated constraints.

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

• Classify constraints before choosing a solution method
• Solve equality-constrained problems with Lagrange multipliers
• Check KKT conditions for inequality constraints

Choose numerical methods for approximating integrals based on the interval, function behavior, and number of dimensions. The skill guides SciPy calculations, error tolerance settings, and accuracy checks against known solutions or repeated calculations with tighter tolerances.

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

• Choosing a method for a definite or improper integral
• Computing two- or three-dimensional integrals
• Checking accuracy by tightening error tolerances

Expert knowledge for Azure Managed Applications development including limits & quotas, security, configuration, and deployment. Use when designing createUiDefinition UIs, JIT access, managed identities, StorageAccountSelector, or Bicep-based catalog publishing, and other Azure Managed Applications related development tasks. Not for Azure Blueprints (use azure-blueprints), Azure Resource Manager (use azure-resource-manager), Azure Lighthouse (use azure-lighthouse), Azure Partner Solutions (use azure-partner-solutions).

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

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding templates (use template-discovery), producing a detailed side-by-side comparison of templates (use template-comparison), authoring custom templates (use template-authoring), deciding cross-parameter defaults such as which framework to pair with native AOT or whether to keep HTTPS when auth is enabled (use template-smart-defaults), modifying existing projects or adding NuGet packages to existing projects.

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

Work on C# and .NET-adjacent mixed-reality solutions around HoloLens, MRTK, OpenXR, Azure services, and integration boundaries where .NET participates in the stack. USE FOR: building or integrating mixed-reality solutions with C#; working on HoloLens, MRTK, Azure mixed-reality services, or OpenXR-related code; reviewing how .NET services. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Refresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.

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

Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao". Trigger even when the user asks for solutions directly: "give me ideas to fix falling sales" is a diagnosis request. Not for open-ended ideation when nothing is broken (brainstorm-coach), understanding user needs (design-thinking), or company-level strategic bets (strategy-board).

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

Drafts U.S. corporate board resolutions authorizing bank account opening, signatory designation, transaction limits, and related banking documents with ratification, supersession, and secretary certification language. Use when preparing board resolutions, written consents, bank account opening packets, signatory authority letters, or banking authorization documents. Trigger keywords: bank account resolution, banking resolution, board consent, signatory authority, account opening, ACH, wire, signature card.

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

Drafts U.S. corporate board-of-directors meeting minutes into formal, defensible records documenting valid corporate action and governance process. Triggers on board minutes, directors meeting record, board resolutions, quorum validation, motion and vote capture, corporate secretary records, governance drafting. Requires source materials such as agenda, attendance, bylaws, notices, reports, prior minutes, and resolutions.

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

Capture a solved, verified problem as a durable learning in `docs/solutions/` so the next agent or engineer does not repeat the mistake or redo the investigation, and keep the `CONCEPTS.md` glossary in step. Use after a fix, debugging session, or design decision whose reasoning is not readable from the final code, tests, or existing docs — "document this", "write up what we learned", "capture this learning", "add it to solutions", "that worked, save it for next time". Writes nothing for routine fixes the code already explains. For auditing or cleaning up existing learnings, use `learn-with-docs-refresh`.

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

Add a text watermark to one or multiple PDFs by uploading them to the Solutions API, polling until completion, then returning download URL(s) for the watermarked PDF(s) (or a ZIP if multiple).

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

Solves complex, open-ended problems using an evolutionary search mechanism inspired by genetic algorithms. Generates a diverse population of candidate answers, scores them against a rubric, then iteratively applies selection, crossover, and mutation to breed progressively better solutions. Use this skill whenever the user wants to explore a solution space deeply, asks for the "best" answer to a subjective or multi-dimensional problem, wants to evaluate competing approaches and distill the strongest, or uses any of these triggers: "evolutionary search", "genetic algorithm", "evolve an answer", "breed solutions", "population-based search", or phrases like "give me multiple approaches and refine the best one". Also trigger when the problem is complex, open-ended, or has no obvious single correct answer and the user wants a high-quality, well-explored result, not just a quick response.

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

Knowledge base from the SD-22 DMSMS Guidebook (DSPO, FY24 working draft). Use for managing Diminished Manufacturing Sources and Material Shortages (DMSMS) and obsolescence across a long-lived system's life cycle: the five-step process (Prepare, Identify, Assess, Analyze, Implement) plus the Strategize overlay; standing up a DMSMS Management Team (DMT) and Management Plan (DMP); risk-based monitoring and surveillance (the risk cube, predictive tools, vendor surveys, GIDEP/DLA PDNs, critical-materials analysis); health assessments and resolution timing; costing and selecting resolutions (life-of-need buys, substitutes, redesign, technology refreshment) by AoA/BCA; and budgeting/executing resolutions through modification funding and the ECP process. Defense-sustainment / DoD-acquisition framing throughout. Does NOT teach general systems engineering, parts-management standards, or contracting law in depth, and does not reproduce DoD policy text or the source's tables and figures.

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

Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.

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

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding or comparing templates (use template-discovery), authoring custom templates (use template-authoring), modifying existing projects or adding NuGet packages to existing projects.

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