40건 · 관련도순
front-end-design-patterns を使い、指定されたフロントエンド範囲に対して サブエージェント調査（必要時は複数スコープに分割した独立 fresh audit） → メインセッション修正 → 必要時のみ性能計測 → simple-add → 再調査を NO_FINDINGS まで繰り返す、機能変更なしの内部リファクタリングループ。 Trigger: front-end-refactor-loop, front-end-design-patterns リファクタリングループ, フロントエンドリファクタリングループ, Reactリファクタリングループ, サブエージェントでフロントエンド調査, NO_FINDINGSまでリファクタ, 性能計測つきフロントエンドリファクタ
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
JavaScript / React / Vue のフロントエンドコードを実装・レビュー・リファクタリングするときに、 現在のコードベースを調査し、適切な設計・パフォーマンス・レンダリングパターンを エージェントが自律的に選んで適用する。ユーザーが hooks-pattern や dynamic-import などの 個別パターンを指定しなくても、必要な reference を選択する。 Trigger: front-end-design-patterns, frontend design patterns, React設計, Vue設計, JavaScript設計, Reactリファクタリング, Vueリファクタリング, フロントエンドパフォーマンス改善, bundle改善, レンダリング戦略, Reactレビュー, Vueレビュー
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose Rust design patterns for RTK modules that process command output. Use concrete examples to structure configuration, prevent type mixups, manage parser states, and select abstractions suited to the task without adding unnecessary architectural complexity.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design patterns v3 — GoF, SOLID, enterprise patterns, anti-patterns, refactoring, language-specific
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Python code for common mistakes in error handling, asynchronous operations, type annotations, and tests. Use a practical checklist and correction examples to guide code reviews, investigate bugs, and improve existing implementations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design or review distributed systems, where multiple computers work together, using 42 cloud design patterns. Organizes options for reliability, performance, messaging, security, and deployment, emphasizing why to choose each pattern and the trade-offs involved.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic Golang design patterns — functional options, constructor APIs, `init()` and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem. Not for wiring a DI container or comparing DI libraries (→ See `samber/cc-skills-golang@golang-dependency-injection` skill), nor for error wrapping, `errors.Is`/`As`, or logging mechanics (→ See `samber/cc-skills-golang@golang-error-handling` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
REST API design with resource naming, pagination, versioning, and OpenAPI spec generation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
7 agentic design patterns with decision tree for choosing the right pattern for each agent type
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices for command definition files - size targets, declarative template, anti-patterns, and canonical examples based on research evidence
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven patterns, database and persistence patterns, and cross-cutting integration patterns. This should trigger for requests such as Apply Java design patterns; Review REST API patterns; Design Kafka event-driven patterns; Improve database persistence patterns; Add resilient integration patterns. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architecture patterns, design principles, and proven recipes for building robust robotics software. Use this skill when designing robot software architectures, choosing between behavioral frameworks, structuring perception-planning-control pipelines, implementing state machines, designing safety systems, or architecting multi-robot systems. Trigger whenever the user mentions behavior trees, finite state machines, subsumption architecture, sensor fusion, robot safety, watchdogs, heartbeats, graceful degradation, hardware abstraction layers, real-time constraints, or software architecture for robots. Also applies to sim-to-real transfer, digital twins, and robot fleet management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review code architecture for maintainability, catch structural issues before they become debtUse when "Reviewing pull requests with structural changes, Planning refactoring work, Evaluating new feature architecture, Assessing technical debt, Before major releases, When code feels "hard to change", architecture, code-review, refactoring, design-patterns, technical-debt, dependencies, maintainability" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply classic design patterns judiciously: when each pattern fits, modern alternatives, and anti-patterns. Use when designing object interactions or reviewing pattern usage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.