puzzle-solver-patterns
Constraint satisfaction patterns for the Pips puzzle solver
rendering-stability-under-load
Guarantee UI stability during extreme rendering pressure using boundary partitioning and adaptive throttling.
fsharp-csharp-bridge
F# Domain/ApplicationๅฑคใจC# Infrastructure/Webๅฑคใฎๅๅคๆใใฟใผใณใ่ชๅพ็ใซ้ฉ็จใF#โC#ๅข็ใณใผใๅฎ่ฃ ๆใปๅๅคๆใจใฉใผ็บ็ๆใปcontracts-bridge Agentไฝๆฅญๆใซไฝฟ็จใPhase B1ใง็ขบ็ซใใ4ใคใฎๅคๆใใฟใผใณใใฌใคใใ
npid-existing-code
Reuse existing Prospect ID code instead of creating new abstractions
entropy-defense-mechanism
Deliberately impose artificial constraints and simplification rules to counteract organizational drift toward complexity. Complexity kills companiesโfight it with binary rules.
fault-tolerant-ui-graphs
Design UI graphs that remain resilient to partial failures and unstable dependencies.
use-architect
Use after design brainstorm and before creating implementation plans to validate architectural decisions
hummbl-framework
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.
layer-design
Design and compose Effect layers for clean dependency management
spec-authoring
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.
fsharp-feature
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.
architecture-philosophy
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.
arch-ddd
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-driven-architecture
Event sourcing, CQRS, and message queue patterns with RabbitMQ and Kafka for distributed systems
backend-dev
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.
java-microservices
Build microservices - Spring Cloud, service mesh, event-driven, resilience patterns
memory-manager
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.
ai-architecture
AI application architecture - gateway, orchestration, model routing, observability, deployment patterns. Use when designing AI systems, scaling applications, or building production infrastructure.
best-practices
Principal Engineer focused on maintainability, SOLID principles, and clean code.
custom-plugin-flutter-skill-state
2300+ lines of state management mastery - all patterns (Provider, Riverpod, BLoC, GetX), dependency injection, persistence, testing with production-ready code examples.
mcp-2025-patterns
Current best practices for Model Context Protocol server design, implementation, and integration. Updated patterns for 2026 MCP ecosystem including multi-server orchestration, security, and performance.
aether-temporal-collective
Distributed evolutionary memory system using Merkle-DAG branching timelines, holographic erasure coding, and stake-weighted consensus to maintain coherent collective history across thousands of agents despite forking narratives and temporal relativity.
applying-solid-principles
Applies SOLID principles and clean code practices. Required for all code implementations. Covers single responsibility, open-closed, and dependency injection principles.
