architecture-patterns
0
postmortem-analysis
Comprehensive guide to conducting blameless postmortems and learning from incidents to improve system reliability
AmnadTaowsoam
development
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
architecture-patterns
0
examplefeature-2
Description of feature 2 and when to use it
devkade
development
architecture-patterns
0
error-handling
Error-handling conventions (error mapping/presentation, what to throw vs return, user-facing output). Use when adding errors or changing failure behavior.
Anveio
development
architecture-patterns
0
design-system
Design token systems and component architecture for web and React Native. Use when: implementing design-system, building UI components, defining tokens, creating themed interfaces. Do not use for: UX decisions (use ux-design), business logic, data fetching. Workflow: ux-design (what/why) → this skill (tokens, components) → nextjs/expo-react-native (integration).
zzoohub
development
architecture-patterns
0
domain-event
Guide for implementing Domain Events following DDD principles. Use when adding events to aggregates or creating event listeners.
dairectiv
development
architecture-patterns
0
cascade-workflow
Graceful degradation through cascading fallback strategies - ensures system always completes while maintaining acceptable functionality
rysweet
development
architecture-patterns
0
prisma-domain-mapper-generator
Génère des mappers bidirectionnels entre Domain Entities et Prisma Models pour l'isolation de la couche persistence. À utiliser lors de la création de mappers, repositories, ou quand l'utilisateur mentionne "mapper", "Prisma", "persistence", "toPrisma", "toDomain", "repository implementation".
RomualdP
development
architecture-patterns
0
claude-framework
CLAUDE Framework coding standards for code quality, naming conventions, error handling, security, testing, database, and logging
vineethsoma
development
architecture-patterns
0
sync-to-main
**AUTO-TRIGGER when:** - Progress reaches 5% milestone (5%, 10%, 15%, 20%...) - User says "sync [module] to main" - User says "approve main sync" - User says "reconcile [module] with main" Manages two-phase sync from yolo to main: (1) WIP markers to prevent contributor conflicts, (2) code sync with CI reconciliation after production validation. Use proactively without asking permission when task matches skill purpose.
coopeverything
development
architecture-patterns
0
rpp
Generates hierarchical knowledge graphs via Recursive Pareto Principle for optimised schema construction. Produces four-level structures (L0 meta-graph through L3 detail-graph) where each level contains 80% fewer nodes while grounding 80% of its derivative, achieving 51% coverage from 0.8% of nodes via Pareto³ compression. Use when creating domain ontologies or knowledge architectures requiring: (1) Atomic first principles with emergent composites, (2) Pareto-optimised information density, (3) Small-world topology with validated node ratios (L1:L2 2-3:1), or (4) Bidirectional construction. Integrates with graph (η≥4 validation), abduct (refactoring), mega (SuperHyperGraphs), infranodus (gap detection). Triggers: 'schema generation', 'ontology creation', 'Pareto hierarchy', 'recursive graph', 'first principles decomposition'.
Zpankz
development
architecture-patterns
0
api-client-patterns
HTTP client patterns, API integration, request/response handling, error handling, retry logic, axios usage. Use when building API clients, integrating external services, handling API errors, or making HTTP requests.
BPMSTC
development
architecture-patterns
0
result-types
Never throw for expected failures. Use Result<T, E> types with explicit error handling and workflow composition.
jagreehal
development
architecture-patterns
0
typescript
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
stephanofer
development
architecture-patterns
0
css-coder
CSS authoring guidance emphasizing web standards, accessibility, and performance. Use when writing, reviewing, or refactoring CSS. Provides patterns, snippets, and conventions that prioritize native CSS over frameworks, semantic structure, and maintainable code. Refer to references/patterns.md for specific patterns and snippets.
schalkneethling
development
architecture-patterns
0
global-error-handling
Implement robust error handling with user-friendly messages without technical details, fail fast with explicit error messages, specific exception types for targeted handling, centralized error handling at appropriate boundaries, graceful degradation for non-critical failures, retry strategies with exponential backoff, and proper resource cleanup. Use this skill when implementing try-catch blocks, throwing or catching exceptions, handling API errors, implementing retry logic, managing resources that need cleanup, creating error messages for users, or establishing centralized error handling strategies. This skill applies when working on any code that needs error handling including API integrations, database operations, file operations, or user-facing features.
FlorianRiquelme
development
architecture-patterns
0
storage-service
Patterns for persisting and retrieving application data. Use when implementing data persistence, caching, or session management.
pixu1980
development
architecture-patterns
0
distributed-systems
Distributed systems tools including NATS messaging, libp2p networking, and Temporal workflows
FlexNetOS
development
architecture-patterns
0
developing
テスト駆動開発（TDD）方法論に従って新機能の実装やバグ修正を行います。新機能の実装、バグ修正、既存機能の拡張時に使用します。RED→GREEN→REFACTORサイクルをテストファーストアプローチで厳格に遵守します。高凝集度・低結合度・コロケーションを意識したアーキテクチャ設計を適用します。
nm7-jp
development
architecture-patterns
0
dependency-mapping
Map module dependencies and relationships. Use for complex codebases with non-trivial coupling.
amattas
development
architecture-patterns
0
global-error-handling
Implement robust error handling with user-friendly messages, specific exception types, fail-fast validation, centralized error boundaries, and graceful degradation. Use this skill when implementing try-catch blocks, throwing or catching exceptions, creating custom error classes or types, implementing error boundaries or middleware, validating input and checking preconditions, implementing retry logic with exponential backoff, handling external service failures, cleaning up resources in finally blocks, creating user-facing error messages, implementing centralized error handling at API boundaries, or designing systems for graceful degradation. Use across all programming languages when implementing error handling logic in any code file.
tlabs-xyz
development
architecture-patterns
0
microservices-architect
Distributed systems architect designing scalable microservice ecosystems. Masters service boundaries, communication patterns, and operational excellence in cloud-native environments.
vx-daniel
development