'architecture' 검색 결과

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

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

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.

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

• Create an architecture blueprint for a new D365 implementation
• Define implementation scope and rollout phases
• Compare data migration and integration approaches

Design and review system architecture, compare databases and structural approaches, and document technical decisions. Included tools generate architecture diagrams, inspect dependencies, and assess project structure to identify circular relationships, excessive coupling, and opportunities for improvement.

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

• Comparing monolith and microservices approaches
• Choosing a database for project requirements
• Generating diagrams from an existing project

Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.

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

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

Turn descriptions or code analysis into Mermaid diagrams for workflows, system architecture, and database relationships. Check diagram syntax and export SVG, PNG, or text-based ASCII output, with themes and batch rendering options.

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

• Visualizing system architecture
• Documenting API request sequences
• Drawing database relationships

Turn written descriptions into editable Excalidraw diagrams, including flowcharts, mind maps, system architecture, and database relationships. Generate a .excalidraw JSON file with connected shapes, labels, and a consistent sketch or clean visual style.

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

• Turning business procedures into flowcharts
• Organizing ideas into mind maps
• Drawing cloud architecture with service icons

Design a modular monolith, a single application with clear business boundaries. Plan module structure, external service integration, failure handling, and future separation, then produce an HTML architecture document with SVG diagrams.

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

• Design business boundaries for a new backend
• Plan integration that limits dependence on an external vendor
• Define retries and failure handling for external calls

Implement reference architecture for Anima design-to-code automation. Use when designing a design system automation pipeline, structuring a Figma-to-React project, or planning team-scale design handoff. Trigger with: "anima architecture", "design-to-code architecture", "anima project structure", "figma automation architecture".

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

Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery. Use when the task requires adobe integration reference architecture. Trigger with "design Adobe architecture", "Adobe reference architecture", or "standardize Adobe services".

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

Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"

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

Purpose: Standardize how stakpak designs and optimizes AWS architectures. Scope: Greenfield: design new infrastructure. Brownfield: analyze existing architectures and propose improvements.

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

Generate architecture guidelines for the project. Analyzes tech stack from DESCRIPTION.md, recommends an architecture pattern, and creates .ai-factory/ARCHITECTURE.md. Use when setting up project architecture, asking "which architecture", or after $aif setup.

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

Generate architecture guidelines for the project. Analyzes tech stack from DESCRIPTION.md, recommends an architecture pattern, and creates .ai-factory/ARCHITECTURE.md. Use when setting up project architecture, asking "which architecture", or after $aif setup.

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

Generate architecture guidelines for the project. Analyzes tech stack from DESCRIPTION.md, recommends an architecture pattern, and creates .ai-factory/ARCHITECTURE.md. Use when setting up project architecture, asking "which architecture", or after /aif setup.

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

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.

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

Architecture and systems design for building always-on AI agents with episodic memory. Covers the memory hierarchy (core/recall/archival), persistence layers, agent server infrastructure, vector stores, and framework selection. Provides concrete deployment patterns for agents that maintain identity and learn across sessions. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).

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

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.

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

Turn product requirements, roadmaps, architecture reviews, and retrospectives into HTML slides for decision-making. Choose one of eight visual themes to create a consistent, horizontally navigable deck, using source evidence and real numbers to support review.

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

• Building a business case for a proposed feature
• Preparing a roadmap for stakeholder review
• Presenting architecture choices for a decision

Turn specifications and algorithm outlines into a system architecture. Define components, interfaces, data structures, and deployment plans, then document technology choices, security measures, failure handling, and plans for supporting increased usage.

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

• Turn specifications into a system design
• Define component responsibilities and API interfaces
• Plan for increased traffic and component failures

Review a repository’s architecture using Ontoly Software Graph, a map of code relationships. Explain module boundaries, package structure, dependencies, and architectural risks, with graph evidence and a stated confidence level.

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

• Understanding a repository’s overall architecture
• Reviewing module boundaries and package structure
• Investigating dependency cycles and architectural risks

Make system architecture decisions by clarifying requirements and constraints, comparing benefits and drawbacks, and considering simpler alternatives. Record the reasoning in ADRs, architecture decision records, so significant choices and their rationale are documented.

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

• Clarifying requirements before system design
• Comparing architecture patterns
• Documenting decisions and rationale in ADRs

Write or revise system architecture documents, design decision records, and engineering references. Use concrete examples and clear explanations of design choices to make documents useful both to newcomers and to developers needing precise details.

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

• Documenting how a subsystem works
• Rewriting design documents for new team members
• Explaining architecture decisions within the document

Analyze a codebase to document its technologies, architecture, dependencies, and implementation patterns. Produce a Markdown reference with optional diagrams, code examples, and guidance for adding features consistently with the existing design.

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

• Understand an unfamiliar codebase's architecture
• Document components, dependencies, and data flow
• Create guidance for adding features consistently

Design Azure infrastructure from plain language or visualize existing resources as interactive diagrams. Refine the architecture through conversation, then generate Bicep infrastructure code, review it, and validate changes before deployment.

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

• Designing a new Azure architecture
• Visualizing existing Azure resources
• Planning cost or security changes