software-architecture
Senior Staff Engineer guidance for Clean Architecture, SOLID principles, and Domain-Driven Design. Use for refactoring, planning new modules, or reviewing code organization.
Найдите подходящую возможность для вашего агента.
Senior Staff Engineer guidance for Clean Architecture, SOLID principles, and Domain-Driven Design. Use for refactoring, planning new modules, or reviewing code organization.
Orchestrator skill for implementing features based on detailed specifications (Specs). Representative use cases include (1) Decomposing specs into TDD-based implementation tasks (Issues) with a shared plan, (2) Managing the integration of distributed TDD results (code & tests) into a unified codebase, and (3) Auditing the final implementation to ensure strict adherence to specifications and test coverage requirements.
Systematically validate implementation plans before execution - catches hallucinations, TDD violations, missing references, and temporal drift that derail implementations. Use after writing-plans skill creates a plan document.
Build reusable, composable UI components with single responsibilities, clear prop interfaces, proper state management, and minimal coupling. Use this skill when creating React, Vue, Angular, or web components with well-defined APIs, sensible defaults, and documentation. Applies to component files, component libraries, design systems, or any modular UI code that should be maintainable, testable, and reusable across different contexts in the application.
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
Disposable runner patterns for GitHub Actions. Container-based, VM-based, and ARC deployment strategies with complete state isolation between jobs.
React best practices and patterns for building maintainable, performant applications with modern React features
Refactor Ruby on Rails code to improve maintainability, readability, and adherence to best practices. This skill transforms messy Rails code into elegant, well-structured solutions following Rails conventions and modern Ruby best practices. It addresses fat controllers and models, extracts business logic into service objects, applies DRY principles, uses concerns for shared behavior, implements query objects for complex database operations, and leverages Rails 8 and Ruby 3.3+ features including pattern matching and Data classes.
Security patterns and best practices. Use for any security-related work - input validation, authentication, authorization, secrets management, Docker security. Contains learned security preferences and requirements.
AI-powered CI Gatekeeper Agent that enforces observability standards in CI/CD pipelines. Use when: (1) Generating GitHub Actions/Jenkins pipelines for observability gates, (2) Configuring progressive enforcement policies, (3) Validating schema compatibility in CI, (4) Generating gate status reports. Triggers: "create observability gate", "configure CI enforcement", "generate gate policy", "check observability compliance".
Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.
Maintain system architecture documentation (ARCHITECTURE_MAP.md) showing module structure, data flows, and entry points. Use this skill when architecture changes, modules are added, or system overview needs updating.
Create comprehensive technical documentation for code systems including data flow diagrams, architecture overviews, algorithm documentation, cheat sheets, and multi-file documentation sets. Use when documenting pipelines, algorithms, system architecture, data flow, multi-stage processes, similarity algorithms, or creating developer onboarding materials. Covers Mermaid diagrams, progressive disclosure, critical patterns, JSON schemas, Pydantic models, and print-friendly reference materials.
gRPC client development patterns for Braiins OS miners - connection pooling, retry logic, stream handling, and error recovery
API and system versioning strategies to enable evolution while maintaining backward compatibility.
Object-oriented design principles including object calisthenics, dependency inversion, fail-fast error handling, feature envy detection, and intention-revealing naming. Activates during code refactoring, design reviews, or when user requests design improvements.
Discovers and finds connection details for Model Context Protocol (MCP) servers through research and documentation