autonomous-agent-readiness
Assess a codebase's readiness for autonomous agent development and provide tailored recommendations. Use when asked to evaluate how well a project supports unattended agent execution, assess development practic...
Discover documentation architecture patterns skills, compare source repositories and read the instructions for each workflow.
Assess a codebase's readiness for autonomous agent development and provide tailored recommendations. Use when asked to evaluate how well a project supports unattended agent execution, assess development practic...
Clean code principles for readable, maintainable software
Use when creating or modifying code in nomarr/services/. Services own runtime wiring, long-lived resources (DB, queues, workers), and call workflows. No complex business logic here.
REST API design best practices for consistent, intuitive APIs
Modern API development patterns for building high-performance, scalable web services. Expert in async/await patterns, REST/GraphQL APIs, middleware, error handling, rate limiting, OpenAPI documentation, testing...
Define clean, hexagonal, and DDD-based architecture patterns for a server-authoritative real-time multiplayer game backend implemented in TypeScript.
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Deterministic MCP protocol for build/runtime issues. Sequential thinking, zero drift, Commit Skill integration.
Implements networking and replication systems including RemoteEvent optimization, custom replication, lag compensation, client prediction, and bandwidth optimization. Use when building multiplayer games that ne...
Elite execution & breakthrough perfection framework. Think like a human, execute like a master across all technical domains.
Document software architecture using ARCHITECTURE.md and docs/*.md files with Mermaid diagrams. Use proactively when ARCHITECTURE.md exists in project root, or invoke to create initial architecture documentatio...
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing A...
Contract lifecycle management - creation, consumption, modification, and resolution.
Use when implementing structured error handling in backend or frontend code. Triggers for: try-catch patterns, custom exception classes, global error handlers, error logging, user-friendly error messages, or AP...
Modern authentication and security patterns for web applications. Expert in JWT tokens, OAuth2 flows, session management, RBAC, MFA, API security, and zero-trust architectures. Framework-agnostic patterns that...
Decomposes requirements into executable tasks and coordinates domain orchestrators (frontend, backend, data, test, devops). Use when receiving PRDs, user requirements, or feature requests that span multiple dom...
Use when creating or modifying code in nomarr/persistence/. Persistence handles database and queue access. Never stores business logic.
Implements data persistence systems including DataStore patterns, session locking, data migration, error handling, and backup systems. Use when saving player progress, inventory, settings, or any persistent dat...
SOLID object-oriented design principles for maintainable code
Load past architectural decisions. Use when making new decisions to ensure consistency.
Park Golf Platform NATS 메시징 패턴 가이드. BFF-Microservice 통신, 메시지 패턴 명명 규칙, 타임아웃 설정, 에러 처리 방법 안내. "NATS", "메시징", "마이크로서비스" 관련 질문 시 사용합니다.
Performs root-cause analysis of failed transfers, missing events, or notification issues using system-level reasoning.
Enforce proper error handling patterns. Use when writing async code, API calls, or user-facing features. Covers try-catch, error boundaries, graceful degradation, and user feedback.
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.