Discover databases architecture patterns skills, compare source repositories and read the instructions for each workflow.
Génère des bounded contexts DDD complets avec architecture en couches (Domain, Application, Infrastructure, Presentation). À utiliser lors de la création de nouvelles features backend, bounded contexts, domain...
ユーザーが「コードレビューして」「品質チェック」「改善提案」「レビューお願い」等と要求した時に発動。 指定されたファイルやPRの変更内容をレビューし、以下を提供する： - バグの可能性 - パフォーマンス問題 - Goのイデ...
Automated content discovery workflow for scanning multiple data sources (ArXiv, GitHub, HuggingFace), applying AI-powered semantic filtering and deduplication, analyzing content quality, downloading images, and...
プラグイン全体の構造設計原則（要素の役割分担、階層構造、依存関係管理）を定義する。プラグイン設計時、アーキテクチャレビュー時、またはユーザーがプラグイン構造、設計原則、独立性、汎用性、依存関係管理に言及した際に...
Génère des Commands, Queries et Handlers suivant le pattern CQRS (Command Query Responsibility Segregation). À utiliser lors de la création de use cases, commands, queries, handlers, read models, ou quand l'uti...
Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation...
This skill demonstrates auto-activation based on conversation context. It activates when users mention "example task," "demonstrate skill," or similar trigger phrases. Replace these with your actual triggers.
Perform deep, expert-level codebase and architecture audits to identify technical strengths, weaknesses, risks, and opportunities. Use when a user asks for an assessment of a codebase's structure, quality, or r...
Use when tasks fail due to transient errors. Provides structured retry strategies and graceful degradation patterns. Invoke on network errors, rate limits, or intermittent failures.
Это набор правил (архитектурных, семантических) для проекта Lotus.Core
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent duplication and technical debt.
Architecture/design support for Treido (feature design, module boundaries, data flow, caching, Supabase/Stripe integration). Triggers on "ARCH:" prefix or when asked to propose an architecture or migration plan...
Guide for designing software systems and making architectural decisions. Use when asked to design a system, evaluate architecture options, or make structural decisions about code organization.
Write a comprehensive system design solution document. Use when the user says "/sys-design..." or "Design [system]". Performs research, documents assumptions, calculations, and provides two implementation appro...
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Use this skill when designing or reviewing APIs - REST, GraphQL, gRPC, or any programmatic interface. Applies API design thinking focused on contracts, ergonomics, and evolution to specifications, designs, and...
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
Design scalable, maintainable system and integration architectures for pilot projects. Use when defining components, data pipelines, tool integrations, and guardrails to ensure robustness, performance, and exte...
Microservices architecture pattern for distributed, independently deployable services
Guide for building resilient applications with robust error handling strategies. Use when designing APIs, debugging issues, or implementing resilience patterns like retries and circuit breakers.
Iteration 8 of Multiplicity Cascade - Collides unrelated domains for emergence
strategies for building automated CI/CD pipelines for agents. Use this to implement "shift left" testing, staged validation, and evaluation-gated deployments.
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.