This skill should be used when creating comprehensive ontological documentation for software systems, including extracting domain concepts, modeling semantic relationships, and generating visual representations of system architectures and business domains.
Internal skill. Use cc10x-router for all development tasks.
Internal skill. Use cc10x-router for all development tasks.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
Internal skill. Use cc10x-router for all development tasks.
Rules and patterns for refactoring UI components to the ERT archetype system.
Guide version migrations for MBC CQRS Serverless framework. Use this when upgrading framework versions, migrating from deprecated APIs, or understanding breaking changes between versions.
Review code for MBC CQRS Serverless best practices and anti-patterns. Use this when reviewing code that uses MBC CQRS Serverless framework, checking for common mistakes, or validating implementation patterns.
Internal skill. Use cc10x-router for all development tasks.
Analyze and address technical debt in codebases.
Standardizes Model Observers for handling side-effects of model events.
Creates or refactors Business Logic into Service classes using MCP-Aware standards.
Standardizes Events and Listeners for decoupled architecture.
Invoke before configuring Nette DI - services, .neon files, autowiring.
Each routine does one thing and does it well - extract when routines have multiple responsibilities
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Invoke before designing presenters, modules, or application structure in web applicartion.
Try 2-3 different approaches before implementing - don't settle for first design you think of
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Guidelines for creating Filament 4 Resources with strict Separation of Concerns (SoC) and UI standards.
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
