Define clean architecture layers, entities, and services for the Pomodoro Time Tracker.
npx skills add https://github.com/manx/PomodoroTimeTracker --skill architect-manx
Please help me install this Agent Skill. Skill: architect Source: https://github.com/manx/PomodoroTimeTracker/tree/main/.claude/skills/architect Command: npx skills add https://github.com/manx/PomodoroTimeTracker --skill architect-manx
This Skill provides comprehensive guidance on the Clean Architecture principles applied to the Pomodoro Time Tracker. It helps maintain clear layer separation, make sound design decisions, and facilitates effective refactoring, ensuring the project remains scalable, testable, and maintainable.
TimeEntry and IDispatcherTimer abstraction, providing context for design choices.Using the architect skill, explain the purpose and dependencies of the Application layer in the Pomodoro Time Tracker project and list its key services.
High-intent search queries and answers about installing and using this skill.
Clean Architecture organizes .NET applications into distinct layers—Domain, Application, Infrastructure, and UI—where each layer has specific responsibilities and dependencies flow inward. This separation enables testability, maintainability, and scalability by isolating business logic from frameworks and external concerns.
Domain layer contains core entities and business rules; Application layer orchestrates use cases through services like ITimeEntryService and IStatisticsService; Infrastructure layer handles persistence and external integrations. Each layer depends only on layers closer to the center, preventing tight coupling and enabling independent testing.
Define core entities (TimeEntry, SessionType, Client, Project, PomodoroSettings) in the Domain layer, then create Application services (ITimeEntryService, IClientService, IProjectService) that encapsulate business logic. Services coordinate between layers while entities remain persistence-agnostic, supporting refactoring and schema evolution.
Refactor when adding complex modules, restructuring data models, or noticing layer violations. Use architectural guidelines and decision records to review layer interactions, ensure new designs align with established patterns, and maintain scalability and testability as requirements evolve.
Use Singleton lifetime for application-wide instances like IDispatcherTimer abstractions, and Transient for ViewModel instances created per view. Abstract timer implementations behind interfaces to enable testability and decouple UI frameworks from business logic.
Store SessionType as a domain entity with properties and relationships instead of a static enum. This allows runtime configuration, database-driven variations, and future feature additions without code changes, supporting evolving business requirements for time-tracking categories.
peterquielDocument domain models with entities, relationships, and business rules.
zlzforeverImplements a JUnit 4, 5 and 6 compatible @DataProvider annotation processor.
DVNghiemApply Clean Architecture boundaries to isolate domain logic from infrastructure.
v1bh0rSelect architectural styles using a decision tree and comparison matrix.