'architect' 검색 결과

软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / API 边界 / 可扩展性 / 演进式架构 — 不含 硬件架构 / 纯企业架构 / 纯 DevOps / 纯安全架构) (software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).) Master OS — automated mastery of software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」

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

Create, update, or validate a concise architecture document from a specification, an idea, or existing code. It records shared design rules so separately developed parts follow consistent boundaries, dependencies, state changes, and data ownership.

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

• Defining shared rules before development
• Extracting design rules from existing code
• Updating architecture for a new feature

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

Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a new project, defining architecture standards, or when the user says 'setup architecture', 'define layers', 'architecture principles', 'help me define my architecture', 'hexagonal architecture', 'modular monolith', 'ports and adapters', or 'define my architecture style'.

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

Enforce architectural rules when generating or modifying code, and validate proposed designs before approval (design mode). Defaults to clean architecture; supports any architecture style via the architecture-refiner. Validates layer responsibilities, dependency direction, and structural constraints using the loaded architecture rules. Use when generating code, reviewing architecture, creating new files, or when the user mentions 'architecture', 'layers', 'structure', 'dependency rules', 'hexagonal architecture', 'ports and adapters', 'modular monolith', or 'onion architecture'. Also use when reviewing generated code for structural compliance.

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

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

Turn a codebase into architecture documentation with Mermaid diagrams. Using the C4 model, a way to describe systems at different levels of detail, the skill explains external relationships, applications, internal components, deployment, and request flows.

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

• Explaining a system overview to stakeholders
• Documenting relationships between apps and databases
• Mapping internal components of a feature

Translate approved game designs into a technical blueprint before coding begins. Map system layers, module responsibilities, data flow, and API boundaries, then check architecture decisions against the pinned engine and identify missing knowledge or decisions.

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

• Creating a technical blueprint before implementation
• Clarifying system layers and module responsibilities
• Mapping data flow and API boundaries

Design or review a system’s overall structure, compare technology choices, and plan for growth and failures. Produce architecture diagrams and Architecture Decision Records, documents that explain key choices, alternatives, and their consequences.

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

• Designing the overall structure of a new system
• Comparing monolith and microservices architectures
• Recording technology decisions and alternatives

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

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

Review AWS infrastructure code and deployed resources against the six Well-Architected pillars. Produce risk-ranked findings, remediation examples, and an architecture diagram, then create GitHub issues for tracking improvements after user confirmation.

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

• Review AWS infrastructure code and deployed resources
• Prioritize findings by risk
• Prepare infrastructure code remediation examples

Plan backend systems with clear module boundaries and dependency rules. This skill helps select architecture patterns, organize business logic, and outline migration steps for systems that are easier to maintain and test.

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

• Designing a new backend system
• Restructuring a monolithic application
• Defining shared architecture standards

Architectural thinking partner for an existing repository — scans the codebase, conducts a structured interview, agrees on current architectural state and recommended direction, and produces a shareable insights document. Scoped to one repository, module, or folder. Does not execute transformation — it orients. Use when the user says 'assess my codebase architecture', 'what direction should my codebase go', 'architecture compass', 'understand my architecture', 'audit architecture drift', 'architectural assessment', or 'help me understand what is wrong with my codebase'.

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

Architecture Patterns workflow skill. Use this skill when the user needs Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Architecture Patterns workflow skill. Use this skill when the user needs Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

architect-review workflow skill. Use this skill when the user needs Master software architect specializing in modern architecture and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Generate the architecture guidelines for a game project. Scans the project structure and tech stack, then produces .unikit/ARCHITECTURE.md describing the folder layout, dependency rules, and how modules communicate. Name a specific pattern or let it auto-detect. Use when the user wants to define or document the project architecture, e.g. "generate architecture", "describe the architecture", "which architecture should I use", "set up project architecture", or mentions module structure, module boundaries, project organization, or dependency rules.

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

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

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

Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional archify skill for interactive standalone HTML diagrams (used only when already installed in the environment; never installed at runtime). Use whenever architecture documentation, ADRs, or architecture diagrams must be created or updated.

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

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

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

Review Azure infrastructure code and deployed resources against five Well-Architected Framework pillars. Identify configuration drift, classify risks, and produce remediation guidance and an architecture diagram, with GitHub issues created after user approval.

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

• Review Azure reliability and security risks
• Compare infrastructure code with deployed resources
• Assess opportunities to improve cost and performance

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