'architect' 검색 결과

Restructure claude-flow v3 into focused modules using Domain-Driven Design, which groups code by responsibility. Define module boundaries, event communication, and plugin interfaces to support a modular architecture with independently testable business logic.

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

• Split an oversized orchestrator into focused modules
• Define boundaries between tasks, sessions, and monitoring
• Design plugin extensions and domain events

Organize new features, complex implementations, and architecture changes into the SPARC stages: specification, pseudocode, architecture, refinement, and completion. Define requirements and acceptance criteria, consult existing patterns, and record lessons for future work.

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

• Defining requirements for a new feature
• Organizing a complex implementation
• Planning an architecture change

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

Restructure claude-flow v3 into focused modules using Domain-Driven Design, which groups code by responsibility. Define module boundaries, event communication, and plugin interfaces to support a modular architecture with independently testable business logic.

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

• Split an oversized orchestrator into focused modules
• Define boundaries between tasks, sessions, and monitoring
• Design plugin extensions and domain events

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

Write and maintain Architecture Decision Records (ADRs), documents explaining important technical choices. Capture the context, options, decision, and consequences, then organize records and track their status so teams can revisit the reasoning.

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

• Record the reasons for choosing a framework or database
• Document design options and their trade-offs
• Explain past technical decisions to new team members

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

Make system design decisions by clarifying requirements, identifying constraints, and comparing the benefits and drawbacks of different approaches. Record the reasoning in architecture decision records, or ADRs, while considering simpler alternatives and the team's experience.

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

• Organizing requirements before designing a system
• Comparing architectural patterns and trade-offs
• Documenting the reasons behind design decisions

Plan backend services and APIs, from service responsibilities and interface definitions to authentication, failure handling, monitoring, and rollout. Produces architecture diagrams, API specifications, and documented tradeoffs based on business and operational requirements.

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

• Designing an order management API
• Defining responsibilities across multiple services
• Planning retries and timeouts for external integrations

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

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

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Plan a system or service from requirements through components, APIs, data storage, and reliability. Produce a structured design document with diagrams, stated assumptions, trade-offs between choices, and decisions to revisit as usage grows.

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

• Planning the architecture of a new service
• Defining APIs, data models, and service boundaries
• Reviewing scaling and reliability plans

Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.

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

• Prioritize technical debt fixes by impact and effort
• Plan engineering hiring, timing, and budget
• Compare building internally with buying a service

Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.

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

• Reviewing a Pascal pull request for architecture violations
• Auditing package responsibilities in a branch
• Checking new node definitions and scene compatibility

Review Google Cloud workloads against the security principles of the Well-Architected Framework. Identify gaps in access control, network protection, data handling, and security operations, then receive prioritized recommendations linked to relevant Google Cloud products.

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

• Reviewing security during Google Cloud architecture design
• Checking access permissions and network defenses
• Identifying gaps in data protection and security monitoring

Evaluate Google Cloud workloads and develop reliability recommendations covering user experience goals, redundancy, monitoring, and recovery. The skill applies the Google Cloud Well-Architected Framework to help identify gaps and plan improvements suited to business requirements.

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

• Reviewing a Google Cloud architecture for reliability gaps
• Setting reliability targets based on user experience
• Planning redundancy and behavior during partial failures

Design a Google Cloud system that combines multiple services, starting with a discussion of business and technical requirements. The skill produces service recommendations, architecture diagrams, deployment guidance, and validation plans, with user approval at each stage.

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

• Gather requirements for a new cloud workload
• Compare and select services for a cloud migration
• Create a diagram and explain system data flows

Design a Google Cloud system for data analysis or machine learning with AI agents. Turn requirements into product choices, an architecture diagram, infrastructure configuration, deployment instructions, and validation steps, with user reviews between phases.

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

• Design a data analysis system with multiple AI agents
• Choose Google Cloud products for analytical requirements
• Prepare an architecture diagram and deployment guide

Review Google Cloud workloads using the Performance Optimization pillar of the Well-Architected Framework. Assess performance requirements and architecture, then get actionable recommendations for resource allocation, caching, independent components, automatic scaling, and ongoing monitoring.

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

• Review resource capacity for expected peak demand
• Assess automatic scaling for traffic spikes
• Review component design for independent scaling

Plan and build AI agents on Google Cloud, from gathering requirements to choosing a single-agent or multi-agent design. Produce architecture diagrams, deployment code and instructions, and validation plans tailored to the workload.

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

• Plan an AI agent architecture on Google Cloud
• Choose between single-agent and multi-agent designs
• Prepare deployment code and step-by-step instructions

Understand a public GitHub repository through GitDiagram's architecture overview. Get an explanation of its main components, source paths, and connections, plus Mermaid diagram source and an interactive diagram for exploring the code.

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

• Getting an overview of an unfamiliar public repository
• Finding source paths for major components
• Understanding connections and data flow

Explore how a public GitHub repository is organized using GitDiagram. Get explanations tied to component names and source paths, an interactive architecture diagram, and a narrated explainer video when one is available.

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

• Preparing to work in an unfamiliar public codebase
• Understanding major components and their source paths
• Exploring component connections in an interactive diagram

Turn structured JSON into editable SVG diagrams for system architectures, workflows, and pipelines. Specify positions, connections, and groups precisely, reproduce the same output under fixed rendering conditions, and convert figures to PDF for papers.

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

• Creating architecture diagrams for technical papers
• Illustrating workflows and processing pipelines
• Adjusting diagram layouts through JSON specifications

Plan a system or service from requirements through components, APIs, data storage, and reliability. Produce a structured design document with diagrams, stated assumptions, trade-offs between choices, and decisions to revisit as usage grows.

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

• Planning the architecture of a new service
• Defining APIs, data models, and service boundaries
• Reviewing scaling and reliability plans

Design and implement a NestJS backend organized into business modules within one deployable application. The skill defines module boundaries, separates data ownership, builds layered code and event communication, and validates isolation through checks and tests.

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

• Designing a new modular NestJS backend
• Implementing business modules with layered responsibilities
• Connecting modules through events