**AUTO-TRIGGER when:** - Progress reaches 5% milestone (5%, 10%, 15%, 20%...) - User says "sync [module] to main" - User says "approve main sync" - User says "reconcile [module] with main" Manages two-phase sync from yolo to main: (1) WIP markers to prevent contributor conflicts, (2) code sync with CI reconciliation after production validation. Use proactively without asking permission when task matches skill purpose.
Generates hierarchical knowledge graphs via Recursive Pareto Principle for optimised schema construction. Produces four-level structures (L0 meta-graph through L3 detail-graph) where each level contains 80% fewer nodes while grounding 80% of its derivative, achieving 51% coverage from 0.8% of nodes via Pareto³ compression. Use when creating domain ontologies or knowledge architectures requiring: (1) Atomic first principles with emergent composites, (2) Pareto-optimised information density, (3) Small-world topology with validated node ratios (L1:L2 2-3:1), or (4) Bidirectional construction. Integrates with graph (η≥4 validation), abduct (refactoring), mega (SuperHyperGraphs), infranodus (gap detection). Triggers: 'schema generation', 'ontology creation', 'Pareto hierarchy', 'recursive graph', 'first principles decomposition'.
HTTP client patterns, API integration, request/response handling, error handling, retry logic, axios usage. Use when building API clients, integrating external services, handling API errors, or making HTTP requests.
Never throw for expected failures. Use Result<T, E> types with explicit error handling and workflow composition.
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
CSS authoring guidance emphasizing web standards, accessibility, and performance. Use when writing, reviewing, or refactoring CSS. Provides patterns, snippets, and conventions that prioritize native CSS over frameworks, semantic structure, and maintainable code. Refer to references/patterns.md for specific patterns and snippets.
Implement robust error handling with user-friendly messages without technical details, fail fast with explicit error messages, specific exception types for targeted handling, centralized error handling at appropriate boundaries, graceful degradation for non-critical failures, retry strategies with exponential backoff, and proper resource cleanup. Use this skill when implementing try-catch blocks, throwing or catching exceptions, handling API errors, implementing retry logic, managing resources that need cleanup, creating error messages for users, or establishing centralized error handling strategies. This skill applies when working on any code that needs error handling including API integrations, database operations, file operations, or user-facing features.
Patterns for persisting and retrieving application data. Use when implementing data persistence, caching, or session management.
Distributed systems tools including NATS messaging, libp2p networking, and Temporal workflows
テスト駆動開発（TDD）方法論に従って新機能の実装やバグ修正を行います。新機能の実装、バグ修正、既存機能の拡張時に使用します。RED→GREEN→REFACTORサイクルをテストファーストアプローチで厳格に遵守します。高凝集度・低結合度・コロケーションを意識したアーキテクチャ設計を適用します。
Map module dependencies and relationships. Use for complex codebases with non-trivial coupling.
Implement robust error handling with user-friendly messages, specific exception types, fail-fast validation, centralized error boundaries, and graceful degradation. Use this skill when implementing try-catch blocks, throwing or catching exceptions, creating custom error classes or types, implementing error boundaries or middleware, validating input and checking preconditions, implementing retry logic with exponential backoff, handling external service failures, cleaning up resources in finally blocks, creating user-facing error messages, implementing centralized error handling at API boundaries, or designing systems for graceful degradation. Use across all programming languages when implementing error handling logic in any code file.
Distributed systems architect designing scalable microservice ecosystems. Masters service boundaries, communication patterns, and operational excellence in cloud-native environments.
Implement event-driven communication using BlueprintEventBus for cross-module coordination. Use this skill when modules need to communicate without tight coupling, broadcasting domain events (task.created, member.added), subscribing to events with proper lifecycle management, and implementing event-driven workflows. Ensures events follow naming conventions ([module].[action]), include Blueprint context, and use takeUntilDestroyed() for automatic cleanup.
UseCase 설계, Transaction 경계 관리, CQRS 적용. @Transactional 내 외부 API 호출 금지. /kb-application 명령 시 자동 활성화.
Custom repository pattern and DataContext implementation for JSON-based storage with computed columns.
Systematically reverse-engineers business requirements from legacy codebases using the Horseshoe Model to bridge the gap between implementation details and architectural intent.
Intelligent resource management with size checking and filtering to preserve context window
Use when exploring Context level impact during scoping - system boundaries, actors, cross-container interactions, and high-level concerns
