'system-design' 검색 결과

시스템 구조와 기술 선택을 검토하고 구성도, 데이터 흐름, 설계 판단의 근거를 문서로 정리합니다. 성능, 보안, 향후 확장을 고려해 설계안을 비교할 수 있습니다.

• 새 시스템의 구조를 설계합니다
• 기술 후보의 장단점을 비교합니다
• 구성 요소의 관계와 데이터 흐름을 정리합니다

Agent skill for arch-system-design - invoke with $agent-arch-system-design

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

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 interview processes for specific roles and experience levels, with round objectives, timing, suggested questions, and scoring criteria. Help interviewers align their judgments and review potential bias before using the process.

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

• Designing interview rounds for a specific role
• Preparing questions for each interview round
• Aligning scoring criteria across interviewers

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 scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "design Twitter", "design Uber", "design a news feed", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs (TinyURL, feeds, chat) and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

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

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or "make it resilient". Also trigger when designing resilient microservices, planning zero-downtime deployments, or capacity-planning for peak load. Covers stability patterns, capacity planning, deploy/release decoupling, and observability. For data systems, see ddia-systems. For system architecture, see system-design.

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

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, designing data pipelines, or debugging distributed-system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

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

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.

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

Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.

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

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.

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

Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way, software-design-philosophy - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, ARCHITECTURE.md, EXPERIMENTS.md, CREATE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new app, validate an idea before writing code, architect an MVP that will not need a rewrite, or says 'help me build my app the right way'. App already exists: use improve-app or grow-app. Business idea not yet validated: run create-business first. Marketing site only: use create-website. Architecture-only question: design-code-architecture. For one framework in isolation, invoke that skill directly.

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

Design calibrated interview loops, competency-based question banks, and hiring calibration. Use when designing interview processes, creating hiring pipelines, generating scoring rubrics, analyzing interviewer bias, or building question banks.

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

System architecture design and review. Use when designing architecture, evaluating microservices vs monolith, writing ADRs, choosing a database, planning for scalability, reviewing system design, or generating architecture diagrams.

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

Design a developmental band system mapping student growth from early childhood through upper secondary. Use when building competency-based curriculum architecture for a school or programme.

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

Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.

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

Defines measurable architecture drivers and constraints before system design; edits architecture docs only.

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

Right-size, ground, and gate SDLC decisions with SNC-sized depth, said-vs-assumed write-back, an evidence ledger, honest option cards, recorded approval, and self-review. Use when running brainstorm-feature, plan-feature, design-solution, or system-design-session.

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

Design an industrial recommendation system or subsystem with explicit scale, latency, freshness, consistency, availability, privacy, cost, degradation, observability, and rollout constraints.

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

Deeply research technical architecture, source code, mechanisms, SDKs, frameworks, project comparisons, and system-design options across repositories, history, official docs, issues, discussions, and high-quality community signals. Use when the user asks for deep research, source-level understanding, architecture comparison, mechanism satisfaction, or evidence for designing a system. Always map the question and obtain confirmation before beginning substantive research; skip for simple factual lookups or straightforward implementation tasks.

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

Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

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

Draft a practical system design for a feature. Use when a mid-level developer needs a starting architecture.

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

System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories).

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

Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision.

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