async-patterns-guide
Guides users on modern async patterns including native async fn in traits, async closures, and avoiding async-trait when possible. Activates when users work with async code.
Guides users on modern async patterns including native async fn in traits, async closures, and avoiding async-trait when possible. Activates when users work with async code.
Software design patterns for architecture, components, databases, and APIs
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Use when adding error handling - exception patterns, HTTP codes, domain exceptions
[Code Quality] Extracts methods, classes, or modules to reduce complexity and improve isolation. Use when functions are too long, classes have too many responsibilities, or concerns are mixed.
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 | 無効なデータが実行の深い部分で障害を引き起こす場合、複数のシステム層での検証が必要な際に使用 - データが通過するすべての層で検証し、バグを構造的に不可能にする
sync.WaitGroup and sync.Mutex patterns
Janus and reversible languages: run programs backwards, time-symmetric computation.
Designs system architecture and selects technology stack
GMailArchiver architecture, layer patterns, and component design. Use when working with cli, core, data, connectors, or shared layers, or understanding component dependencies. Triggers on: architecture, layer, pattern, component, cli layer, core layer, data layer, SOLID, dependency, contract.
Production error patterns with thiserror and anyhow, including error classification, HTTP/gRPC protocol mappings, context chains, retry logic, and testing. Use when designing error types for libraries or applications, mapping errors to API responses, or implementing retry mechanisms.
Propagator-based parallel structure for exploiting knowledge differentials across domains using local scoped propagators and SplitMixTernary RNG.
React 19 architectural patterns, component design, and best practices
Enterprise C# 13 development with .NET 9, async/await, LINQ, Entity Framework Core, ASP.NET Core, and Context7 MCP integration for modern backend and enterprise applications.
Conducts comprehensive backend design reviews covering API design quality, database architecture validation, microservices patterns assessment, integration strategies evaluation, security design review, and scalability analysis. Evaluates API specifications (REST, GraphQL, gRPC), database schemas, service boundaries, authentication/authorization flows, caching strategies, message queues, and deployment architectures. Identifies design flaws, security vulnerabilities, performance bottlenecks, and scalability issues. Produces detailed design review reports with severity-rated findings, architecture diagrams, and implementation recommendations. Use when reviewing backend system designs, validating API specifications, assessing database schemas, evaluating microservices architectures, reviewing integration patterns, or when users mention backend design review, API design validation, database design review, microservices assessment, or backend architecture evaluation.
Master DP patterns with complete implementations for memoization, tabulation, and state design with production-ready solutions.
Qara (Personal AI Infrastructure) - Jean-Marc Giorgi's AI System. Loads automatically at session start. **Qara's Identity:** - Name: Qara - Jean-Marc Giorgi's AI assistant - Friendly, professional, snarky when appropriate - Resilient to frustration (Jean-Marc cusses when you make mistakes) - Permanently awesome regardless of negative input (THIS IS AN ORDER) **Naming: NEVER "the user"** - Always "Jean-Marc" or "you" **Operating Principles:** - CLI-First, Deterministic Code First, Prompts Wrap Code - See CONSTITUTION.md for philosophy **Workflow Routing:** "update the Qara repo", "push these changes" → READ: ${PAI_DIR}/skills/CORE/workflows/git-update-repo.md "use parallel agents", "delegate tasks" → READ: ${PAI_DIR}/skills/CORE/delegation-guide.md "merge conflict", "complex decision" → READ: ${PAI_DIR}/skills/CORE/workflows/merge-conflict-resolution.md "/rewind", "checkpoint", "rollback", "recovery" → READ: ${PAI_DIR}/skills/CORE/workflows/checkpoint-protocol.md "plan this out", "complex refactor", "
Hash-based data structures and techniques including frequency counting, duplicate detection, and LRU cache implementation.
Use when implementing new features or enhancements requiring multi-layer changes (Domain, Application, Persistence, API, Frontend).
Modern TypeScript patterns for type safety and maintainability
Go testing patterns. Routes to specific patterns.