আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Factory & Assembler 변환 전문가. CommandFactory Command→Domain 변환, QueryFactory Query→Criteria 변환, Assembler Domain→Response 변환. PersistBundle 영속화 묶음, QueryBundle 조회 결과 묶음. 단방향 변환 원칙: Factory는 생성만, Assembler는 조립만. 비즈니스 로직 절대 금지.
Entity definitions and multi-tenant architecture schema for the MotoRent rental system.
Disciplined development workflow that prevents incomplete implementations, silent fallbacks, and hallucinated code. Use this skill for ANY coding task, feature implementation, bug fix, or technical work. Enforces mandatory decomposition of specs into tasks, elicits clarification for ambiguities, prohibits fallbacks without explicit approval, requires research for uncertain APIs/libraries, and maintains grounding checkpoints to prevent rework. Triggers on requests like "implement", "build", "create", "fix", "add feature", "develop", or any programming task.
Master systematic debugging techniques to problem, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Message broker setup patterns (Redis, RabbitMQ, SQS) for Celery including connection strings, SSL configuration, high availability, and production best practices. Use when configuring message brokers, setting up Redis/RabbitMQ/SQS, troubleshooting broker connections, implementing HA/failover, securing broker communications with SSL, or when user mentions broker setup, connection issues, sentinel, quorum queues, or AWS SQS integration.
EARS requirement authoring guide (Ubiquitous/Event-driven/State-driven/Optional/Unwanted Behaviors) with 5 official patterns.
Implement user-friendly error handling with specific exception types, centralized error handling, graceful degradation, and proper resource cleanup. Use this skill when implementing error handling in controllers, services, or API endpoints, when creating custom exception classes, when writing try-catch blocks, when handling external service failures, when implementing retry strategies, when displaying error messages to users, when cleaning up resources in finally blocks, or when implementing fail-fast validation and error detection.
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
Implements GigLedger features following Clean Architecture. Use when building out feature modules from GitHub issues. Creates all layers (presentation, application, domain, data) with proper patterns.
Implement robust error handling with user-friendly messages, specific exception types, centralized error boundaries, and graceful degradation strategies. Use this skill when writing try-catch blocks, handling exceptions and errors, creating error messages for users, implementing error boundaries in React or other frameworks, validating input and checking preconditions, handling API errors and external service failures, implementing retry strategies with exponential backoff, cleaning up resources in finally blocks, designing graceful degradation for non-critical failures, or preventing technical details and security information from being exposed to users. Apply this skill when handling errors in any code file, implementing error recovery mechanisms, or reviewing error handling approaches for robustness and security.
Validates development plans using simple, safe best practices. Follows existing project structure and official documentation. Use this skill when reviewing migration plans or deployment plans to ensure they are complete, safe, and follow standard patterns. No advanced features - keeps it simple.
comprehensive 12-step project development workflow from initialization through deployment. use when starting a new project, continuing project development, or user mentions project steps, architecture planning, implementation planning, or references pydev-workflow steps 01-12.
AI-powered PR Author Agent that transforms Observability Diff Plans into Pull Requests. Use when: (1) Generating instrumentation code from Scout Agent output, (2) Creating OTel configuration, correlation headers, lineage specs, (3) Scaffolding telemetry validation tests, (4) Creating GitHub/GitLab PRs with observability artifacts. Triggers: "generate PR from diff plan", "create instrumentation PR", "scaffold observability code", "generate OTel config".
Rigorous adversarial validation for proposed solutions, architectures, and design decisions. Use when a plan, design, implementation, or architectural decision needs systematic challenge before commitment. Triggers on requests for design review, architecture validation, solution critique, pre-mortem analysis, or when explicitly invoked to challenge a proposal. Acts as devil's advocate with the rigor of a cold war era Russian Olympic gymnastics judge—blocking genuine issues while enabling good work.
Microservices architecture patterns for event-driven systems. Covers service-to-service communication, idempotency, user isolation, event-driven design, and service discovery.
Enhanced Spec-Driven Development (SDD) framework with recursive decomposition for large-scale features. Use when a feature is too large for a single spec (multi-service features, 5+ atomic components, complex dependency graphs, or features spanning multiple domains). Provides structured workflow: Blueprint (product discovery) to Parent Spec (orchestrator with decomposition map) to Atomic Specs (standard SPEC-XXX.md). Includes tools for dependency validation, visualization, progress tracking, and integration test generation.
Use when exploring unclear requirements or architectural decisions - refines rough ideas into clear requirements/designs through collaborative questioning (one at a time), explores alternatives, validates incrementally. Activates when user has vague feature idea, mentions "not sure about", "exploring options", "what approach", or during spec-driven requirements/design phases.
Five idempotency patterns for automation: check-before-act, upsert, force overwrite, unique identifiers, and tombstones. Choose based on constraints and APIs.
Guide for writing clean, maintainable code following industry best practices and design principles like DRY, SOLID, and composition patterns. Use when writing any code to ensure consistency, readability, and long-term maintainability across all programming languages.
Expert DevOps architecture including CI/CD, infrastructure as code, containerization, and observability
