patternsarena-allocator
Arena Allocator Pattern (C-Specific) pattern for C development
Arena Allocator Pattern (C-Specific) pattern for C development
Master NestJS framework with modules, controllers, services, dependency injection, guards, interceptors, and microservices patterns for enterprise applications.
Clean Architecture and SOLID principles implementation including dependency injection, layer separation, domain-driven design, hexagonal architecture, and code quality patterns
Validate DDD 4-layer architecture compliance. Use when (1) after implementation completion, (2) during verification phase, (3) before PR creation, (4) architecture refactoring validation, (5) Constitution Principle I/II compliance check.
SRE principles, observability, and incident management
Create event hooks for Claude Code that trigger on specific events. Generate hooks with proper JSON configuration for automating workflows. Use when: creating hooks, setting up event triggers, automating on file saves or tool calls. Activates for: "create hook", "generate hook", "new hook", "event hook", "make hook"
Constraint satisfaction patterns for the Pips puzzle solver
Guarantee UI stability during extreme rendering pressure using boundary partitioning and adaptive throttling.
F# Domain/Application層とC# Infrastructure/Web層の型変換パターンを自律的に適用。F#↔C#境界コード実装時・型変換エラー発生時・contracts-bridge Agent作業時に使用。Phase B1で確立した4つの変換パターンをガイド。
Reuse existing Prospect ID code instead of creating new abstractions
Deliberately impose artificial constraints and simplification rules to counteract organizational drift toward complexity. Complexity kills companies—fight it with binary rules.
Design UI graphs that remain resilient to partial failures and unstable dependencies.
Use after design brainstorm and before creating implementation plans to validate architectural decisions
Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, evidence standards, quality criteria, and application methodology. Essential reference for HUMMBL-based development, analysis, and problem-solving.
Design and compose Effect layers for clean dependency management
Author ADR, PRD, and SDS specifications following SEA™ templates with full traceability. Use when creating architecture decision records (ADRs), product requirement documents (PRDs), or software design specifications (SDS) that require proper spec-to-code traceability and document relationships.
Orchestrates end-to-end F# full-stack feature development across all layers. Use when: "add feature", "implement X", "build Y", "create new feature", "full stack", "new functionality", "add capability", "implement end-to-end", "complete feature". Guides through: Shared types → Backend → Frontend → Tests. Use this for features that touch multiple layers of the application.
Core architectural principles for StepLeague - modular design, system thinking, future-proofing, and maintenance reduction. Use when designing new features, refactoring code, considering implementation approaches, or making any architectural decisions. Keywords: architecture, design, modular, refactoring, reusable, shadcn, maintenance, future-proof, system.
Apply Domain-Driven Design (DDD) architecture to backend projects. Use for tasks like defining bounded contexts, aggregates and invariants, entities/value objects, domain services, repositories, domain events, application services, anti-corruption layers, and aligning code structure and APIs with domain language while avoiding anemic models.
Event sourcing, CQRS, and message queue patterns with RabbitMQ and Kafka for distributed systems
This skill should be used when developing backend services for Manjha using Encore.ts, implementing agents, writing E2E tests, or working with the message-driven architecture. It ensures adherence to TDD practices, type safety, proper logging, and Manjha's development principles.
Build microservices - Spring Cloud, service mesh, event-driven, resilience patterns
Gerencia persistencia de contexto, decisoes e learnings do projeto. Armazena e recupera informacoes entre sessoes para manter continuidade. Use quando: salvar decisoes, recuperar contexto, persistir learnings.