Loading...
Loading...
Found 3 Skills
This skill should be used when the user asks to "implement a feature in Elixir", "refactor this module", "should I use a GenServer here?", "how should I structure this?", "use the pipe operator", "add error handling", "make this concurrent", or mentions protocols, behaviours, pattern matching, with statements, comprehensions, structs, or coming from an OOP background. Contains paradigm-shifting insights.
Expert architectural standards for building scalable Godot applications (Apps, Tools, UI, or Games) using the Composition pattern. Use when designing node structures, refactoring monolithic scripts, or implementing complex behaviors. Enforces "Has-A" relationships over "Is-A" inheritance.
Domain-oriented architecture for Laravel without external package dependencies, based on concepts from "Laravel Beyond CRUD" (Spatie). Use this skill when the user wants to structure a Laravel project using DDD, domain-oriented architecture, or organize code by business concepts instead of technical properties. Also activate when the user asks about: Actions, Data Objects (DTOs), lean models, States with enums, ViewModels (Blade or API), HTTP Query builders, application layer, or scaling Laravel projects beyond simple CRUD. Activate for any mention of "domain layer", "application layer", "beyond CRUD", "domain-oriented", or requests to refactor a Laravel project into domain structure. Even if the user asks "how to organize a large Laravel project", this skill is relevant.