'monolithic' 검색 결과

Create a phased roadmap for splitting a monolithic application into separate services. Assess current progress, prioritize work by risk, value, and dependencies, and produce milestones, estimated effort, acceptance criteria, and progress reports.

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

• Planning a migration from a monolith to separate services
• Prioritizing components for extraction
• Defining phase milestones and completion criteria

Generates short, single-shot videos for product reveals, teasers, and ambient loops. Plans the subject, movement, and lighting, then saves an MP4 in the project folder using the selected model, duration, and aspect ratio.

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

• Creating a short product reveal video
• Generating a motion teaser
• Making an ambient background loop

Creates web prototypes inspired by Swiss industrial print, using newsprint backgrounds, oversized black type, fine grid lines, and red accents. It suits editorial pages, agency portfolios, and manifesto sites with a precise, assertive visual style.

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

• Prototyping a newspaper-style editorial page
• Designing an agency portfolio
• Building a manifesto site

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 and refactor Python components with clear responsibilities and simple structure. Assess when to split large classes, combine objects instead of extending them, and extract shared code without introducing unnecessary abstractions.

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

• Defining responsibilities for a new Python component
• Splitting oversized classes and functions
• Deciding when to extract shared code

Plan microservices by defining service responsibilities, communication methods, and data ownership. Use patterns for gradual migration, distributed transactions, and failure isolation to design systems made of independently responsible services.

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

• Gradually splitting a monolithic system into services
• Defining service responsibilities and interfaces
• Designing event-based communication and distributed transactions

Convert an existing SGLang cookbook page to shared templates driven by model configuration. Preserve its deployment commands and interactive choices, transfer eligible benchmark measurements, and check equivalence, links, and rendered behavior.

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

• Migrating a legacy SGLang cookbook page
• Moving deployment choices into model configuration
• Transferring reproducible benchmark measurements

Reorganize long AGENTS.md, CLAUDE.md, and similar instruction files into a short main file with links to topic-specific documents. Identifies conflicting rules and deletion candidates, then checks links and coverage so instructions remain organized and accessible.

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

• Shorten an oversized AGENTS.md
• Split CLAUDE.md into topic-specific files
• Resolve conflicting agent instructions

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 systems made of independently deployable services, or plan how to split an existing application. The skill produces service boundary diagrams and recommendations for communication, data ownership, failure handling, monitoring, and deployment.

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

• Planning how to split a monolithic application
• Choosing REST, gRPC, or event-based communication
• Defining data ownership and cross-service consistency

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

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

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

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

Builds voice and chat AI agents with LiveKit Agents on LiveKit Cloud or a self-hosted server. Use when the user asks to "build a voice agent", "create a LiveKit agent", "add voice AI to my app", "implement handoffs", "structure an agent workflow", "my agent is slow / too chatty", "it says it booked but nothing was saved", "make it confirm before committing", "it keeps re-asking things the caller already said", or is writing code against the LiveKit Agents SDK. Covers architecture: designing for latency, keeping context small, splitting a monolithic agent into handoffs and tasks, and designing for voice. Also covers keeping the model in charge of meaning while code owns state, approvals, and effects. For API specifics use reading-livekit-docs. To check behavior use debugging-livekit-agents and testing-livekit-agents.

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

Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

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

Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes.

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

Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Java 21+ Spring Boot 3.5+ applications. Use when structuring layered architectures, separating domain logic from frameworks, implementing ports and adapters, creating entities/value objects/aggregates, or refactoring monolithic codebases for testability and maintainability.

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

Restructure and improve Isabelle or Coq proofs to enhance readability, modularity, and maintainability without changing semantics. Use when proofs are long and monolithic, have repeated patterns, use unclear naming, lack documentation, or when the user asks to refactor, clean up, improve, or reorganize their formal proofs.

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

Enforces strict modular code architecture: SRP, no monolithic index files, no catch-all utils, 200 LOC hard limit. This rule is NON-NEGOTIABLE. Violations BLOCK all further work until resolved.

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

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

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

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

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

Software architecture patterns and best practices

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