'chi' 검색 결과

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

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

릴리스 작업을 하위 에이전트에 맡기고 claude-mem의 version-bump 다음에 childhood를 실행해 두 단계의 진행을 자동화합니다.

• 릴리스 작업을 하위 에이전트에 위임
• version-bump 다음에 childhood 실행
• 두 단계의 릴리스를 한 번에 요청

Archive several OpenSpec changes together after reviewing their documents and task progress. The skill checks code to resolve overlapping specification updates, syncs the selected updates, and reports which changes were archived, skipped, or failed.

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

• Archive several completed changes together
• Resolve overlapping specification updates
• Review unfinished work before archiving

Calls significant loops from protein-directed and targeted 3C assays (HiChIP, PLAC-seq, Capture Hi-C/PCHi-C, ChIA-PET) where the contact background is peak-anchored and coverage-biased, so generic Hi-C loop callers (cooltools dots, Juicer HiCCUPS) use the wrong null. Covers FitHiChIP (config-driven coverage+distance-decay spline regression, peak-to-peak vs peak-to-all foreground, loose vs stringent background, coverage vs ICE bias), MAPS (positive Poisson regression on bias factors for PLAC-seq/HiChIP), hichipper (restriction-site-distance bias model + library QC), CHiCAGO (Delaporte two-component Brownian+technical background for asymmetric bait x other-end Capture Hi-C), the with/without separate-ChIP anchor decision, and differential loops via diffloop. Use when calling loops from HiChIP/PLAC-seq/Capture Hi-C, choosing FitHiChIP/MAPS/CHiCAGO, picking peak-to-all vs peak-to-peak, setting the loop FDR, supplying ChIP peaks as anchors, QCing a HiChIP library, or comparing loops between conditions.

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

Calls significant loops from protein-directed and targeted 3C assays (HiChIP, PLAC-seq, Capture Hi-C/PCHi-C, ChIA-PET) where the contact background is peak-anchored and coverage-biased, so generic Hi-C loop callers (cooltools dots, Juicer HiCCUPS) use the wrong null. Covers FitHiChIP (config-driven coverage+distance-decay spline regression, peak-to-peak vs peak-to-all foreground, loose vs stringent background, coverage vs ICE bias), MAPS (positive Poisson regression on bias factors for PLAC-seq/HiChIP), hichipper (restriction-site-distance bias model + library QC), CHiCAGO (Delaporte two-component Brownian+technical background for asymmetric bait x other-end Capture Hi-C), the with/without separate-ChIP anchor decision, and differential loops via diffloop. Use when calling loops from HiChIP/PLAC-seq/Capture Hi-C, choosing FitHiChIP/MAPS/CHiCAGO, picking peak-to-all vs peak-to-peak, setting the loop FDR, supplying ChIP peaks as anchors, QCing a HiChIP library, or comparing loops between conditions.

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

Calls significant loops from protein-directed and targeted 3C assays (HiChIP, PLAC-seq, Capture Hi-C/PCHi-C, ChIA-PET) where the contact background is peak-anchored and coverage-biased, so generic Hi-C loop callers (cooltools dots, Juicer HiCCUPS) use the wrong null. Covers FitHiChIP (config-driven coverage+distance-decay spline regression, peak-to-peak vs peak-to-all foreground, loose vs stringent background, coverage vs ICE bias), MAPS (positive Poisson regression on bias factors for PLAC-seq/HiChIP), hichipper (restriction-site-distance bias model + library QC), CHiCAGO (Delaporte two-component Brownian+technical background for asymmetric bait x other-end Capture Hi-C), the with/without separate-ChIP anchor decision, and differential loops via diffloop. Use when calling loops from HiChIP/PLAC-seq/Capture Hi-C, choosing FitHiChIP/MAPS/CHiCAGO, picking peak-to-all vs peak-to-peak, setting the loop FDR, supplying ChIP peaks as anchors, QCing a HiChIP library, or comparing loops between conditions.

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

Create Chinese academic presentation slides with Beamer, a LaTeX slide system, using a fixed CUFE template. Organizes research arguments, tables, and figures, with spacing and slide-splitting rules to address overflow, and supports updating existing decks.

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

• Preparing Chinese slides for a thesis defense
• Building slides for a Chinese academic conference
• Fixing text and table overflow

Design backend systems with clear boundaries between business rules, databases, and external services. Use Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to organize new applications, refactor existing code, and make core logic easier to test.

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

• Planning the structure of a new backend
• Refactoring tightly coupled applications
• Testing business rules independently of external services

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

Edit Chinese text to remove stiff translation patterns, repetitive AI-style phrases, and unnecessary filler. Apply consistent spacing around English and numbers, appropriate punctuation, and spacing after bold Chinese text.

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

• Revising Chinese text that sounds translated
• Removing repetitive AI-style phrasing
• Standardizing mixed Chinese and English formatting

Archive the current Cloudroom thread and its child threads, then stop its runtime, the environment running the agent. It acts only on an explicit request and provides a short closing summary before archiving.

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

• Archiving a finished Cloudroom conversation
• Stopping the runtime for the current thread
• Closing a thread together with its child threads

Search Wayback Machine archives for deleted GitHub files, issues, pull requests, and wiki pages. Recover available text and repository details from saved web pages to investigate a project's past state.

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

• Recovering a deleted README or documentation
• Checking deleted issue and pull request discussions
• Reviewing a repository's past state

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

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

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

Set up Git workflows for Gitee, Coding.net, 极狐 GitLab, and CNB with platform-specific connection and authentication examples. Choose branching rules, standardize Chinese commit messages, and adapt automated testing and deployment configurations to your team's workflow.

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

• Configure connections and authentication for Chinese Git platforms
• Choose branching rules that fit the team
• Standardize Chinese commit messages and review templates

Write Chinese code review feedback that clearly distinguishes required fixes, suggestions, and optional advice. Use question and suggestion templates, organize review summaries, and follow guidance for mixed Chinese-English comments and commit messages.

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

• Writing Chinese review comments with clear priorities
• Rephrasing blunt feedback as questions or suggestions
• Standardizing Chinese-English comments and commit messages

Write and revise Chinese technical documentation using consistent spacing, punctuation, terminology, and structure. Includes README.md and API documentation templates, bilingual formatting examples, and a checklist for reviewing documents before publication.

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

• Standardizing spacing and punctuation in Chinese documents
• Writing a Chinese README.md
• Organizing API documentation in Chinese and English

Collect GitHub activity and local git history as evidence for investigations, then save, filter, and share it as JSON. The skill also supports recovering deleted content from archives and checking stored evidence against its original sources.

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

• Preserving GitHub commits, issues, and pull requests as evidence
• Examining local commits no longer linked to branches or tags
• Recovering deleted GitHub content from archives

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.

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

Design multi-tier caching architectures for web applications — cache-aside vs write-through vs write-behind, TTL design, cache invalidation, Redis patterns, CDN configuration, browser caching, and stampede prevention. Use when choosing a caching pattern, designing cache invalidation strategies, implementing Redis caching, configuring Cache-Control headers, or preventing cache stampedes. Activate on "cache invalidation", "cache-aside", "write-through", "TTL", "Redis cache", "CDN caching", "cache stampede", "stale data", "browser cache". NOT for database query caching within an ORM, memoization of pure functions, or CPU-level caching.

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

Design multi-tier caching architectures for web applications — cache-aside vs write-through vs write-behind, TTL design, cache invalidation, Redis patterns, CDN configuration, browser caching, and stampede prevention. Use when choosing a caching pattern, designing cache invalidation strategies, implementing Redis caching, configuring Cache-Control headers, or preventing cache stampedes. Activate on "cache invalidation", "cache-aside", "write-through", "TTL", "Redis cache", "CDN caching", "cache stampede", "stale data", "browser cache". NOT for database query caching within an ORM, memoization of pure functions, or CPU-level caching.

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

Archify의 실제 도표와 에이전트 작업 기록으로 정확성·가독성·완료 시간을 평가합니다. 변경 전후를 비교해 배치, 연결선 경로와 작성 절차를 개선합니다.

• 도표 배치와 연결선 경로 비교하기
• 도표 수정이 반복되는 원인 조사하기
• 도표 작성 절차의 개선 효과 검증하기