'separation' 검색 결과

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

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

Audit and improve `/llms.txt`, a curated starting point for AI tools browsing documentation. Check its location, the usefulness and accessibility of linked pages, and its separation from existing crawl and indexing controls.

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

• Audit llms.txt on a public documentation site
• Select useful API references and getting-started guides
• Check documentation links for availability

Review JavaScript written directly in HTML and move suitable code into external files. Replace inline event handlers with addEventListener, clarify browser verification steps, and explain how separating code supports maintenance, caching, and security.

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

• Moving JavaScript out of HTML markup
• Replacing onclick handlers with addEventListener
• Reviewing script separation for caching and maintenance

Simulate peer review through five perspectives covering journal fit, methods, subject expertise, interdisciplinary implications, and counterarguments. Receive separate review reports, an editorial decision, and a revision roadmap, or check whether revisions address earlier comments.

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

• Simulate peer review before journal submission
• Check research methods and statistical validity
• Test core arguments against counterarguments

Design long-running processes across services with Temporal, a system that preserves workflow progress. Covers separating coordination from external operations, handling retries and failures, and structuring workflows so they can resume after interruptions.

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

• Designing order or booking processes across services
• Building approval flows with timeouts and escalation
• Planning recovery for distributed transactions

Add clear runtime reporting to Python, PowerShell, or Node.js batch scripts. Design start messages, progress counts, item failures, and final summaries while preserving existing result output, error handling, and exit codes, then verify visibility during execution.

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

• Add progress reporting to long-running batch scripts
• Report individual failures and final outcome counts
• Keep progress logs separate from machine-readable results

Build systems that use Pinecone to find documents for AI answers or retain agent memories across sessions. Guides index setup, data loading, meaning-based and keyword search, memory separation, and end-to-end checks.

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

• Build an AI assistant that answers from documents
• Keep agent facts and decisions across sessions
• Combine meaning-based search with exact terminology

Plan tiered administration for Active Directory by separating administrative accounts and systems into three levels. Cover dedicated administration workstations, authentication restrictions, and verification checks to help limit credential theft and the spread of compromise.

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

• Designing tiered Active Directory administration
• Separating privileged accounts by administrative tier
• Planning dedicated administration workstations

Set up Havoc infrastructure for authorized attack simulations, including its command server, traffic listeners, Nginx relay servers, and Windows agents. The skill also covers communication profiles and operational precautions for running the infrastructure.

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

• Preparing Havoc infrastructure for an authorized exercise
• Reviewing server and traffic relay separation
• Configuring communication profiles for an exercise

Apply consistent architecture and coding conventions when building cross-platform apps with Avalonia UI and Zafiro. The skill guides separation of interface and logic, reactive data handling, explicit error results, and reuse of existing helpers.

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

• Standardizing Avalonia UI and Zafiro implementation
• Keeping ViewModels independent of Avalonia
• Reviewing error handling with Result types

Guides changes to Handsontable themes and CSS, including cell spacing, text, icons, and theme tokens—named styling settings. It explains compatibility rules and the files and checks needed to keep theme changes consistent.

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

• Adjust cell spacing without disrupting scrolling
• Add or rename theme tokens
• Fix text styles affected by the host page

Plan and configure a shared GKE cluster for multiple teams or environments. Set up namespaces, team permissions, resource limits, and network separation, then use labels and GKE cost allocation to track spending by team.

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

• Design a GKE cluster shared by multiple teams
• Separate development, staging, and production workloads
• Set team permissions and resource quotas

Build .NET 8 APIs and backend services using C# 12, with clear separation of application responsibilities. The skill covers database access, authentication, API documentation, compilation checks, and integration tests that verify components working together.

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

• Building endpoints with minimal APIs
• Adding database access with Entity Framework Core
• Separating application responsibilities with MediatR

Prepare for a demand letter by gathering the parties, facts, legal basis, deadlines, and desired outcome. Record negotiation options and information to exclude in a structured intake.md file for the separate drafting skill.

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

• Preparing the facts for a payment demand
• Organizing a breach notice or cease-and-desist request
• Reviewing negotiation options and disclosure limits

Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.

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

• Preparing a final penetration test report
• Rewriting an executive summary for nontechnical readers
• Creating a reusable security reporting template

Validate Illumina BCL run folders and sample sheets, plan demultiplexing—the separation of reads by sample—and convert data to FASTQ using installed tools. Review conversion metrics, index settings, and reads that could not be assigned.

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

• Checking run folders and sample sheets before conversion
• Reviewing index, UMI, and lane settings
• Converting Illumina BCL data to FASTQ

Organize existing code components into business areas to prepare for service separation. Produce domain maps, component assignment tables, and refactoring plans that align namespaces, the naming structure used to organize code, with business responsibilities.

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

• Grouping existing components by business responsibility
• Planning service extraction from an existing application
• Aligning code namespaces with business areas

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

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

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

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Shape a high-contrast interface with dark molded panels, inset shadows, and tactile controls that resemble physical objects. Apply a consistent visual system across page framing, cards, buttons, and small status displays, using one restrained accent color.

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

• Designing a dark interface with tactile depth
• Giving cards and controls a consistent material feel
• Using a brand color for status and active indicators

Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.

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

Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go. For a specific DI library, → See `samber/cc-skills-golang@golang-google-wire`, `samber/cc-skills-golang@golang-uber-dig`, `samber/cc-skills-golang@golang-uber-fx`, or `samber/cc-skills-golang@golang-samber-do` skills.

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

Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.

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