fpf-local-first-unification-naming-protocol
FPF Pattern F.18: Local‑First Unification Naming Protocol
Discover databases architecture patterns skills, compare source repositories and read the instructions for each workflow.
FPF Pattern F.18: Local‑First Unification Naming Protocol
Testing strategies, patterns, and best practices across test types. Auto-triggers when writing tests, setting up test infrastructure, or improving test coverage.
Asynchronous programming patterns for Python, JavaScript/TypeScript, and other languages. Auto-triggers when implementing concurrent code, handling promises, or optimizing I/O operations.
Kubernetes operations, deployment patterns, and cloud-native best practices. Auto-triggers when working with containers, K8s manifests, or cloud infrastructure.
RESTful API and GraphQL design best practices. Auto-triggers when designing endpoints, handling HTTP methods, or structuring API responses.
Observability patterns including logging, metrics, tracing, and alerting. Auto-triggers when implementing monitoring, debugging production issues, or setting up alerts.
Create domain entities following DDD principles. Use when the user wants to create a new entity, add a domain model, implement domain logic, or mentions "entity", "domain", "model", "aggregate".
Create domain entities following DDD principles. Use when the user wants to create a new entity, add a domain model, implement domain logic, or mentions "entity", "domain", "model", "aggregate".
Guide for implementing Clean Architecture patterns in .NET projects. Use when creating new features, refactoring code structure, or when the user mentions "clean architecture", "layers", "domain-driven", "CQRS"...
Guide for implementing Clean Architecture patterns in .NET projects. Use when creating new features, refactoring code structure, or when the user mentions "clean architecture", "layers", "domain-driven", "CQRS"...
Prevents over-engineering by enforcing industry-proven principles: AHA (Avoid Hasty Abstractions), YAGNI, Colocation, and Rule of Three. Use when designing features, planning architecture, "architect this", "de...
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
Resilient command execution with automatic fallbacks and error recovery
Intelligent resource management with size checking and filtering to preserve context window
Create a C# server-side simulation service following the Plugin/IEventAdapter pattern with configuration, pulse updates, and entity management. Use when creating new simulations, scenario generators, or test da...
FastAPI backend development patterns. Use when creating API endpoints, authentication, database models, or backend logic.
React frontend development patterns. Use when creating pages, components, API integration, or UI features.
Strategic orchestrator for PlasmaDX-Clean volumetric rendering project. Use when coordinating multi-agent tasks, making architectural decisions, enforcing quality gates, or managing complex rendering workflows...
Create comprehensive implementation plans using Codex (GPT 5.2) for complex features. Use when user says "use codex plan mode", "codex plan", "plan with codex", or wants detailed implementation planning with fi...
This skill should be used when the user asks about Rails philosophy, DHH's principles, the Rails way, "convention over configuration", "majestic monolith", "omakase", "sharp knives", NO BUILD, integrated system...
This skill should be used when the user asks about deploying Rails applications, Kamal deployment, Docker containers, production configuration, environment variables, secrets management, CI/CD pipelines, server...
Apply Single Responsibility Principle when writing code. Keep modules focused, cohesive, and loosely coupled. Guide splitting classes with too many methods. Ensure code is reusable and testable.
Language-agnostic backend patterns: API design, authentication, security, databases. Use when: designing APIs, implementing auth, securing endpoints, modeling data. Triggers: "api design", "rest api", "graphql"...
Implementar serviços de lógica de negócio em services/. Use quando criar service, lógica de negócio, orquestração de repositórios, ou integração com LLM.
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.