architecture-patterns
3
applying-fsd-architecture
Feature-Sliced Design(FSD) 아키텍처를 적용한 프론트엔드 프로젝트 개발 지원. FSD 레이어, 슬라이스, 세그먼트 구조 설계, 의존성 규칙 적용, 마이그레이션 시 사용.
jeongsk
development
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
architecture-patterns
3
storage-sync
Synchronize memories between Turso (durable) and redb (cache) storage layers. Use when cache appears stale, after failures, or during periodic maintenance.
d-o-hub
development
architecture-patterns
3
infrastructure-software-upgrades
Generic guidelines on how to perform infrastructure component upgrades in a reliable way
stakpak
development
architecture-patterns
3
optimization-patterns
Apply caching strategies, database optimization, and algorithmic improvements to enhance application performance
dasien
development
architecture-patterns
3
brokle-error-handling
Use this skill when implementing, reviewing, or debugging error handling in the Brokle codebase. This includes repository error mapping, service layer AppError constructors, handler response mapping, domain alias imports, or understanding the industrial error handling flow.
brokle-ai
development
mobile
3
clean-archi-swiftui
Clean Architecture patterns for Swift/SwiftUI iOS projects. Use when working on Swift/SwiftUI projects that follow Clean Architecture with bounded contexts, ports/adapters pattern, and layered separation (domain/UI). Triggers for creating features, use cases, refactoring to bounded contexts, reviewing architecture compliance, or understanding project structure.
benaor
development
architecture-patterns
3
separation-of-concerns
Separation of Concerns principle for TypeScript code review and refactoring. Use when detecting mixed responsibilities, business logic in UI components, infrastructure code in domain layer, or tightly coupled modules. Helps improve modularity and maintainability. Related to Clean Architecture layers.
benaor
development
architecture-patterns
3
finding-code-patterns
Finds similar implementations, usage examples, and existing patterns in the codebase - shows concrete code examples for modeling new work. Pattern librarian documenting what exists without judgment.
samjhecht
development
backend
3
api-designer
Design consistent, RESTful APIs with proper versioning, documentation, and error handling.
nguyenthienthanh
development
architecture-patterns
3
unity-csharp-fundamentals
Unity C# fundamental patterns including TryGetComponent, SerializeField, RequireComponent, and safe coding practices. Essential patterns for robust Unity development. Use PROACTIVELY for any Unity C# code to ensure best practices.
creator-hian
development
architecture-patterns
3
csharp-async-patterns
Modern C# asynchronous programming patterns using async/await, proper CancellationToken usage, and error handling in async code. Use when guidance needed on async/await best practices, Task composition and coordination, ConfigureAwait usage, ValueTask optimization, or async operation cancellation patterns. Pure .NET framework patterns applicable to any C# application.
creator-hian
development
architecture-patterns
3
scalable-thinking
Design for scale while keeping implementation simple (KISS).
nguyenthienthanh
development
architecture-patterns
3
feature-planning
Break down features into implementable tasks and choose architecture approach. Use when starting a new feature or receiving requirements that need technical decomposition.
dagba
development
architecture-patterns
3
distributed-workers
Use when working on worker implementation, ServiceOrchestrator patterns, WorkerAPIBase, operation dispatch, progress tracking, cancellation, backend-to-worker communication, or adding new worker types.
kpiteira
development
architecture-patterns
3
software-engineering
The foundation of engineering mindset. Focuses on architecture, system patterns, and universal code navigation.
tao3k
development
architecture-patterns
3
domain-driven-design
Apply Domain-Driven Design patterns. Use when modeling complex business domains, defining bounded contexts, or designing aggregates. Covers entities, value objects, and repositories.
dralgorhythm
development
architecture-patterns
3
refactoring-code
Improve code structure while preserving behavior with test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
third774
development
architecture-patterns
3
functional-programming
Use when writing functional code - covers FP best practices (Lea differs from traditional FP languages)
mcclowes
development
architecture-patterns
3
effect-errors-retries
Error modeling and recovery with TaggedError, catchTag(s), mapError, and retry schedules. Use when defining errors or adding resilience.
mepuka
development
full-stack
3
backend-dev-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
weirdgme
development
architecture-patterns
3
policyengine-code-organization
Code organization patterns for PolicyEngine - variable naming conventions, folder structure, file organization
PolicyEngine
development
architecture-patterns
3
architecture-patterns
Choose and implement iOS architecture patterns (MVVM, TCA, Clean Architecture) based on feature complexity. Use when designing architecture for new features or refactoring existing code.
dagba
development
architecture-patterns
3
defense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
samjhecht
development
architecture-patterns
3
structurizr-architecture-sync
Maintain Structurizr C4 architecture diagrams in sync with code changes. Use when adding components, modifying relationships, changing architectural boundaries, or implementing new patterns. Ensures workspace.dsl accurately reflects the current system architecture.
VilnaCRM-Org
development