error-handling-strategies
Implement robust error handling with proper validation, recovery mechanisms, and clear feedback for system stability
发现 devops architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Implement robust error handling with proper validation, recovery mechanisms, and clear feedback for system stability
Apply proven architectural patterns (MVC, layered, microservices) to create maintainable systems with clear separation of concerns
Design extract-transform-load patterns, data pipeline orchestration, and incremental loading strategies
Apply Gang of Four and architectural patterns appropriately to solve common software design problems
Apply caching strategies, database optimization, and algorithmic improvements to enhance application performance
Design Kubernetes deployment patterns, configure service mesh, and implement container best practices
Idiomatic Go patterns for errors, interfaces, concurrency, and packages. Use when: - Writing or reviewing Go code - Designing interfaces or package structure - Implementing concurrency patterns - Handling error...
Ruby and Rails best practices for services, testing, and architecture. Use when: - Writing or reviewing Ruby/Rails code - Designing service objects or organizing business logic - Setting up RSpec tests with Fac...
Modern C# development with .NET 8+, async patterns, and records. Use when: - Writing or reviewing C# code - Configuring async/await with ConfigureAwait - Using nullable reference types - Implementing pattern ma...
Invoke Codex CLI as a coworker for implementation, brainstorming, specs, and reviews. Use when you want parallel thinking, cheap execution, or a second opinion. Codex tokens are cheaper than yours — delegate ag...
Apply universal naming principles: avoid Manager/Helper/Util, use intention-revealing names, domain language, verb+noun functions. Use when naming variables, functions, classes, reviewing names, or refactoring...
Idiomatic Rust patterns for ownership, errors, traits, and configuration. Use when: - Writing or reviewing Rust code - Designing error handling with Result and thiserror - Implementing traits and composition pa...
Patterns for syncing state between external services (Stripe, Clerk) and local database. Invoke for: webhook failures, data sync issues, eventual consistency, recovery from missed events, subscription state man...
Codebase mapping and documentation using parallel AI subagents. Invoke for: map this codebase, document architecture, understand codebase, onboarding to new project, create CODEBASE_MAP.md, generate architectur...
Design Swift app architecture with MVVM, Clean Architecture, dependency injection, and repository patterns. Use when structuring iOS/macOS projects, creating ViewModels, implementing DI, or organizing code laye...
Codebase exploration techniques for rapid discovery, architecture analysis, pattern detection, and dependency mapping.
Design Laravel app architecture with services, repositories, actions, and clean code patterns. Use when structuring projects, creating services, implementing DI, or organizing code layers.
SOLID principles for Laravel 12 and PHP 8.5. Files < 100 lines, interfaces separated, PHPDoc mandatory.
Systematic process for analyzing and modernizing legacy applications to comply with the 12-Factor App methodology. Covers code analysis, configuration externalization, dependency management, and container/Kuber...
Generic guidelines on how to perform infrastructure component upgrades in a reliable way
Design system and security architecture. Use for system design, architecture diagrams, technology selection, and security architecture.
Simple Mode - Natural language orchestrator for TappsCodingAgents. Coordinates multiple skills (@enhancer, @planner, @architect, @designer, @implementer, @reviewer, @tester, @debugger, @improver) based on user...
Design API contracts, data models, and UI/UX specifications. Use for API design, data modeling, UI wireframes, and design systems.
Universal documentation standards and best practices for software projects
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。