ralph
Spec-driven development with task-by-task execution. Transforms feature ideas into structured specs (research, requirements, design, tasks) then executes them autonomously with fresh context per task. Supports...
Discover devops architecture patterns skills, compare source repositories and read the instructions for each workflow.
Spec-driven development with task-by-task execution. Transforms feature ideas into structured specs (research, requirements, design, tasks) then executes them autonomously with fresh context per task. Supports...
Habilidad para desarrollar soluciones empresariales en Odoo siguiendo arquitectura modular, buenas prácticas oficiales, testing y CI/CD.
Enhanced Spec-Driven Development (SDD) framework with recursive decomposition for large-scale features. Use when a feature is too large for a single spec (multi-service features, 5+ atomic components, complex d...
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.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexp...
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing A...
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debug...
OpenFGA authorization modeling best practices and guidelines. This skill should be used when authoring, reviewing, or refactoring OpenFGA authorization models. Triggers on tasks involving OpenFGA models, relati...
Unified document lifecycle management. Defines terminal statuses, unified numbering via .next-id, close procedures, and orphan detection. Load at session start.
Unified execution engine for all development workflows. Progressive disclosure for phase execution, quick features, story completion, and scaffolding. Integrates with artifact-tracking and meatycapture-capture....
High-velocity, intent-driven development using agentic workflows and MCP servers.
Implement features following Domain-Driven Design (DDD) and CQRS patterns with event-driven architecture, Kafka, and BullMQ
Review architecture decisions and code changes against documented architecture principles. Use this skill before implementing new features or refactoring existing code to ensure compliance with layer boundaries...
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
API versioning strategies including URL-based, header-based, and breaking change management
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
Single Responsibility Code in Self-Documented Folder Structure
Implements OTP design patterns including GenServer, Supervisor, and Application behaviors.
Enforce SOLID design principles during code generation, refactors, and code review (SRP/OCP/LSP/ISP/DIP). Use when changing architecture, introducing new abstractions, reducing coupling, eliminating type-switch...
Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repea...
Use Neo4j memory MCP for creating/updating linked memories (entities, relations), de-duplication (DRY), and retrieval queries for project continuity. Use when saving global learnings or querying graph relations...
Full-stack development context for coordinating changes across contracts and frontend. Use this skill when changes span both backend contracts and frontend code, requiring synchronized updates across the stack.
Enterprise-level rules for Melos/Mason project structure (Core, Common, Package)
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.