'architecture analysis' 검색 결과

Design Azure infrastructure using natural language, or analyze existing Azure resources to auto-generate architecture diagrams, refine them through conversation, and deploy with Bicep. When to use this skill: - "Create X on Azure", "Set up a RAG architecture" (new design) - "Analyze my current Azure infrastructure", "Draw a diagram for rg-xxx" (existing analysis) - "Foundry is slow", "I want to reduce costs", "Strengthen security" (natural language modification) - Azure resource deployment, Bicep template generation, IaC code generation - Microsoft Foundry, AI Search, OpenAI, Fabric, ADLS Gen2, Databricks, and all Azure services

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

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

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

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

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

Perform 12-Factor Agents compliance analysis on any codebase. Use when evaluating agent architecture, reviewing LLM-powered systems, or auditing agentic applications against the 12-Factor methodology.

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

データモデル分析エージェント - 既存のデータモデルを分析し、エンティティ・リレーションシップ・ドメインルールを抽出。/data-model-analysis [対象パス] で呼び出し。

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

セキュリティ分析エージェント - 既存システムのセキュリティ状況を分析し、OWASP Top 10対応状況とゼロトラスト準備状況を評価。/security-analysis [対象パス] で呼び出し。

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

DB設計分析エージェント - 既存のデータベース設計を分析し、テーブル定義・インデックス・制約・問題点を抽出。/db-design-analysis [対象パス] で呼び出し。

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

アクセス制御分析エージェント - ゼロトラストモデルに基づくアクセス制御の現状分析と移行準備評価。/access-control-analysis [対象パス] で呼び出し。

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

ER図分析エージェント - 現行システムのER図を作成し、エンティティ・リレーションシップ・カーディナリティを可視化。/er-diagram-analysis [対象パス] で呼び出し。

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

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

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

Design Azure infrastructure using natural language, or analyze existing Azure resources to auto-generate architecture diagrams, refine them through conversation, and deploy with Bicep. When to use this skill: - "Create X on Azure", "Set up a RAG architecture" (new design) - "Analyze my current Azure infrastructure", "Draw a diagram for rg-xxx" (existing analysis) - "Foundry is slow", "I want to reduce costs", "Strengthen security" (natural language modification) - Azure resource deployment, Bicep template generation, IaC code generation - Microsoft Foundry, AI Search, OpenAI, Fabric, ADLS Gen2, Databricks, and all Azure services

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

Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.

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

• Investigate possible causes of a bug
• Understand behavior across multiple files
• Explain architecture and tradeoffs

Run Gemini CLI to review code, assess technical plans, and analyze large collections of files. Choose a model and execution settings for the task, then capture findings about security, maintainability, architecture, or technical debt.

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

• Reviewing security and quality across multiple files
• Checking architecture plans for missing components
• Analyzing the structure of a large codebase

Design and implement systems that collect, transform, validate, and store data for analysis. Covers scheduled and real-time processing, data warehouses, quality checks, monitoring, and cost tuning using tools such as Apache Spark, dbt, and Airflow.

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

• Building scheduled data collection and transformation workflows
• Designing a data warehouse for analysis
• Synchronizing database changes in real time

Stress-test ideas, strategies, and plans by breaking them into individual claims for parallel expert agents to challenge. Receive the strongest supporting case, surviving counterarguments, and findings ranked by severity with suggested ways to address weaknesses.

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

• Challenge assumptions in a business strategy
• Find weaknesses in a software architecture proposal
• Prepare strong objections to a pricing decision

Prepare a Web3 bug bounty investigation by scoring targets, setting up analysis tools, reviewing past audits, and tracing how funds move. Use the findings to prioritize smart contracts and assess whether suspected issues have concrete impacts.

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

• Choose a protocol for a bug bounty investigation
• Prepare build, test, and static analysis tools
• Map fund flows and prioritize contract reviews

Review consequential or ambiguous decisions through ten stages of structured reflection. Separate observations from assumptions, examine alternatives and risks, and produce a recommendation supported by evidence, with verification needs and conditions for revisiting the decision.

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

• Compare options and their tradeoffs
• Review architecture choices and wider effects
• Investigate incidents and challenge assumptions

Read existing code to reconstruct system specifications, including architecture, data flows, APIs, and business rules. Produces documentation tied to code locations, separating observed behavior from inferences and questions that need clarification.

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

• Understand an undocumented legacy system
• Document existing APIs and business rules
• Map module dependencies and data flows

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

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

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Build a documented understanding of unfamiliar code before a security audit. It records function assumptions, guarantees, dependencies, and open questions, producing a dossier and individual function notes to support later vulnerability analysis.

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

• Understanding unfamiliar code before an audit
• Mapping dependencies for threat modeling
• Preparing background notes for an architecture review

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

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

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Use Ontoly's deterministic Software Graph and MCP server for codebase architecture, request tracing, dependency analysis, and impact analysis.

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

Have a fast, conversational analysis with the AWS DevOps Agent. Use for cost optimization, architecture review, topology mapping, knowledge / runbook discovery, security audits, dependency questions, and quick diagnostics — anything that needs a 5-30 second answer rather than a 5-8 minute deep investigation. Trigger words include cost, optimize, review, architecture, topology, what runbooks, show me, compare, audit, what if.

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

Detect business logic vulnerabilities in a codebase using a three-phase approach: threat modeling (domain analysis and attack scenarios), batched verify (check exploitable gaps in parallel subagents, 3 scenarios each), and merge (consolidate batch results). Covers price manipulation, workflow bypass, limit violations, race conditions, reward abuse, etc. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/businesslogic-results.md. Use when asked to find business logic, logic flaws, or abuse-of-function bugs.

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