“architecture”的搜索结果

软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / 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'.

中文简介正在准备中。当前显示原文说明。

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

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.

中文简介正在准备中。当前显示原文说明。

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

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

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.

中文简介正在准备中。当前显示原文说明。

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 whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.

中文简介正在准备中。当前显示英语简介。

• Find game requirements without architecture decisions
• Check for conflicts between architecture decisions
• Review compatibility with the pinned engine version

Write architecture decision records, short documents explaining a software design choice, its context, and its consequences. It helps decide what deserves a record, select a template, organize files, and link replacement decisions to earlier records.

中文简介正在准备中。当前显示英语简介。

• Record why a database or library was chosen
• Set up a directory for decision records
• Choose an ADR template that fits the decision

Maintain a collection of architecture decision record templates, examples, translations, and tool links. It explains which files to update for each contribution and how to review pull requests for completeness, consistent formatting, and relevant content.

中文简介正在准备中。当前显示英语简介。

• Add an ADR template to the collection
• Add a worked decision record example
• Update links to ADR tools and pull request checks

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

中文简介正在准备中。当前显示原文说明。

Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app's architecture, choose boundaries and a domain model, decide monolith versus microservices, or says 'how should I structure this app'. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.

中文简介正在准备中。当前显示原文说明。

Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

中文简介正在准备中。当前显示原文说明。