Loading...
Loading...
Found 2,222 Skills
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Microservices architecture patterns and design. Use when user asks to "design microservices", "service decomposition", "API gateway", "distributed transactions", "circuit breaker", "service mesh", "event-driven architecture", "saga pattern", "service discovery", or mentions microservices design patterns and distributed systems.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Provides comprehensive guidance for event-driven architecture including domain events, event sourcing, CQRS, and event patterns. Use when the user asks about event-driven architecture, needs to implement event-driven systems, or work with domain events.
Generates interactive codebase quizzes to test understanding of architecture, patterns, and implementation details. Configurable by card count (fewer, standard, more) and difficulty (easy, medium, hard). Use when asked to quiz me, test my knowledge, create flashcards, generate codebase questions, or run a code quiz.
Generate detailed layered architecture diagrams as self-contained HTML artifacts with inline SVG icons, CSS Grid nested container layout, SVG path connection overlays, and color-coded connection legends. Use when the user asks to create architecture diagrams, infrastructure diagrams, system topology diagrams, network diagrams, cloud architecture visuals, deployment diagrams, integration flow diagrams, or any request involving visual representation of system components, their containment hierarchy, and interconnections. Triggers on terms like "architecture diagram", "infra diagram", "system diagram", "topology", "deployment diagram", "network diagram", "integration architecture", or when the user provides a system description and asks for a visual/diagram.
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
Frontend architecture expert. Use when planning component architecture, state management strategies, performance optimization, or technology selection decisions.
Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.
Diagnose and fix React Native & Expo codebase health issues. Use when reviewing React Native code, fixing performance problems, auditing accessibility, or improving architecture.
Orchestrate comprehensive code review across ~12 AI reviewers. 5 persona reviewers (Grug, Carmack, Ousterhout, Beck, Fowler) via Moonbridge, 4 domain specialists (security-sentinel MANDATORY, performance, data integrity, architecture) via Task, plus hindsight-reviewer and synthesis. Use when: code review, PR review, pre-merge quality check.
Use this skill for Makefile audit and optimization. Use when auditing Makefiles, reviewing build system, checking portability, eliminating recipe duplication. Do not use when creating new Makefiles - use abstract:make-dogfood. DO NOT use when: architecture review - use architecture-review.