'architect' 검색 결과

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

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

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

Design cloud architectures and migration plans for AWS, Azure, and GCP. Produce service diagrams, selection rationale, security designs, cost estimates, and recovery strategies, with deployment and rollback plans that account for availability and operational monitoring.

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

• Design a cloud architecture and explain service choices
• Plan a cloud migration and cutover checks
• Review cloud spending and resource sizes

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.

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

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.

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

Architecture Decision Framework workflow skill. Use this skill when the user needs Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Use when configuring or troubleshooting Salesforce CPQ contract creation, subscription management, amendment quotes, or renewal quotes. Trigger keywords: contract, amendment, renewal, subscription, co-termination, SBQQ__Subscription__c. NOT for designing the amendment/renewal architecture or swap pattern — use architect/subscription-management-architecture. NOT for amending or renewing contracts from Apex — use apex/cpq-api-and-automation. Also covers the standard Contract and Order objects underneath CPQ — Contract Status vs StatusCode, activation locking, EndDate auto-calculation, ContractSettings and OrderSettings, reduction orders, and renewal-reminder automation. Trigger keywords: Contract, ContractStatus, StatusCode, ActivatedDate, OwnerExpirationNotice, ContractTerm, EndDate, Order, OrderItem, reduction order, ContractSettings, OrderSettings, renewal reminder. NOT for Revenue Cloud or Subscription Management objects — use architect/revenue-cloud-architecture and architect/subscription-management-architecture.

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

Router for the 106 SfSkills `architect` skill packages. Solution and platform architecture: multi-org strategy, scalability limits, licensing, Well-Architected reviews and architecture decision records. Use when the request mentions architecture, solution design, ADR, Well-Architected, scalability, large data volume, multi-org, licensing, tenant isolation, HA/DR, technical debt. Finds and opens the exact skill package to read; it does not contain the guidance itself.

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

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".

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

Architecture Decision Records (ADR) — a lightweight method for capturing important architectural decisions with context, trade-offs, and rationale. Based on Michael Nygard's ADR pattern and Google/Meta/ByteDance's design documentation culture. USE WHEN: deciding between technology choices, designing new architecture, changing existing architecture, documenting why a decision was made, onboarding new team members, or preserving design context for future maintainers. Triggered by terms like "tech choice", "architecture decision", "why did we choose", "design rationale", "ADR", or "architectural decision record".

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

Turn product requirements and user experience plans into technical architecture with Winston, a system architect persona. Discuss technology choices and their trade-offs, with an emphasis on established tools, developer productivity, and designs that can be implemented.

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

• Turning product requirements into a technical design
• Discussing trade-offs between technology choices
• Reviewing architecture with developer productivity in mind

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

Review system architecture and major design changes for scalability, resilience, and maintainability. Identify risks, compare design tradeoffs, and document recommendations and next steps across services, APIs, data storage, security, and deployment.

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

• Reviewing microservice boundaries
• Assessing a move to event-driven architecture
• Comparing serverless and container deployment

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

Design an AI agent around its requirements, or audit an existing agent for architectural problems. Deliver justified decisions, verification plans, and a PDF report with a diagram, covering budgets, permissions, stopping rules, and failure handling.

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

• Design an agent from an idea or specification
• Audit an existing agent’s architecture
• Diagnose errors and false completion reports

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

Clean up DeepChat's specification-driven development documents after implementation and validation. Review feature, issue, and architecture files, remove completed or obsolete material when evidence supports deletion, and preserve maintained specifications while checking references.

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

• Remove issue documents after confirming a bug is resolved
• Clear old plans from completed feature work
• Update or remove architecture documents after replacement