yonatankarp
16 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
yonatankarparch-adr
Use when recording an architectural decision so future maintainers know why — phrases like "ADR", "architecture decision record", "why did we pick X", "lightweight architecture documentation", "decision log", "should this be an ADR", "tribal knowledge", "we chose this two years ago and now nobody remembers why". Defines the ADR as a short, structured document capturing what was decided, why, alternatives considered, and consequences — written at the time of the decision and kept in the repo.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarparch-fitness-functions
Use when enforcing architectural characteristics through automation — phrases like "architecture fitness function", "evolutionary architecture", "architecture tests", "ArchUnit", "dependency rules in CI", "automated architecture checks", "guardrails", "drift detection". Defines fitness functions as automated checks that verify architectural characteristics on every change, catching drift before it accumulates.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarparch-microservices
Use when designing or reviewing a microservices architecture — phrases like "microservices", "should we split this service", "service boundaries", "bounded context per service", "API gateway", "backend for frontend", "BFF", "service mesh", "microservices vs monolith", "database per service", "data ownership". Defines microservices as independently deployable services aligned with business capabilities — and the discipline of resisting the style until the monolith proves inadequate.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarparch-strangler-fig
Use when migrating a legacy system incrementally — phrases like "strangler fig", "strangler pattern", "incremental migration", "monolith to microservices", "rewrite without big bang", "replace legacy in place", "facade in front of the legacy system", "anticorruption layer". Defines Fowler's Strangler Fig as the migration discipline of gradually replacing legacy functionality behind a stable facade, never doing a big-bang rewrite.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpddd-aggregate
Use when designing or critiquing aggregate boundaries — phrases like "aggregate", "aggregate root", "should these be one entity or two", "consistency boundary", "transactional consistency", "this aggregate is huge", "should I reference by ID or by object". Defines aggregates as transactional consistency boundaries and the rules for entity references within and across them.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpddd-bounded-context
Use when drawing or auditing model boundaries — phrases like "bounded context", "where do we draw the line between X and Y", "this model is getting muddled", "should this be one service or two", "the same word means different things in different places". Defines what a bounded context is, what it isn't, and the signals that say a boundary should exist. Pairs with ddd-context-mapping for the relationships across boundaries.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpddd-domain-service
Use when behavior doesn't naturally belong to a single entity or value object — phrases like "domain service", "this logic spans multiple aggregates", "where does this go", "the entity is starting to know too much", "we need a calculator/coordinator that isn't a thing". Defines when to introduce a stateless domain service vs forcing behavior onto an entity. Distinguishes domain services from application/infrastructure services.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpddd-refactor
Use when the user wants to transform existing code toward DDD — phrases like "refactor this to use aggregates", "extract a value object from this primitive", "split this god aggregate", "make this domain model less anemic", "introduce a bounded context boundary here". Sequences refactor steps and points at the pattern skill that explains the target shape. Do NOT use for code review (route to ddd-review) or initial design (route to ddd-design).
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpddd-ubiquitous-language
Use when establishing or auditing a domain's shared vocabulary — phrases like "ubiquitous language", "what should we call this concept", "the team uses different words for the same thing", "the code uses different names than the business". Defines what a ubiquitous language is, how to grow one, and the smell tests that reveal a missing one. Do NOT use for code generation; this is a process/language skill.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-facade
Use when simplifying access to a complex subsystem — phrases like "Facade pattern", "home theater example", "make this subsystem easier to use", "hide the complexity behind one method", "high-level interface to many classes". Defines Facade as a single entry-point class that orchestrates a set of subsystem classes behind a simpler interface, without preventing direct subsystem access.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-identify
Use when the user has a design problem and is asking which GoF pattern (if any) fits — phrases like "which design pattern should I use", "is this an Observer or a Mediator", "what pattern handles this", "I'm not sure if it's Strategy or State", "help me pick a pattern for this scenario". Diagnostic mode that walks the problem statement to a candidate pattern (or rules patterns out) and hands off to the relevant pattern skill.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-iterator
Use when traversing a collection without exposing its internals — phrases like "Iterator pattern", "the menus use different internal structures but the diner shouldn't care", "encapsulate iteration", "hide whether it's an array, list, or hash map". Defines Iterator as providing a uniform way to access elements of a collection sequentially without revealing the collection's underlying representation.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-prototype
Use when creating new instances by copying an existing one rather than constructing from scratch — phrases like "Prototype pattern", "clone this object", "copy an instance with one field changed", "registry of prototypes", "the constructor is expensive but I have a finished example". Defines Prototype as specifying the kinds of objects to create using a prototypical instance and creating new objects by copying that prototype.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-template-method
Use when an algorithm has a fixed skeleton with variable steps — phrases like "Template Method pattern", "the steps are the same but one varies", "Coffee and Tea both brew via boil-brew-pour-add-condiments but differ in two steps", "hook method", "the Hollywood principle don't call us we'll call you". Defines Template Method as a base class that defines an algorithm's skeleton in a final method, deferring some steps to subclasses.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarpgof-visitor
Use when adding new operations over an existing object hierarchy without modifying it — phrases like "Visitor pattern", "double dispatch", "I want to add operations to this AST/tree without changing the node classes", "separate algorithm from data structure". Defines Visitor as representing an operation to be performed on the elements of an object structure — letting you define a new operation without changing the classes of the elements on which it operates.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj
yonatankarptdd-anti-patterns
Use when auditing tests for TDD smells — phrases like "test smells", "flaky tests", "slow tests", "brittle tests", "test anti-patterns", "tests testing the framework", "over-mocking", "mystery guest", "fragile tests", "test breaks on every refactor". Catalogs the most common test-suite anti-patterns with symptoms, why each is wrong, and the fix.
- instalacje
- 2
- GitHub Stars
- 1
- Aktualizacja
- 19 maj