backend-architecture-nestjs
NestJS 10 modular architecture, services, DTOs, guards, and API patterns.
Découvrez les skills lifestyle architecture patterns, comparez leurs dépôts et consultez leurs instructions.
NestJS 10 modular architecture, services, DTOs, guards, and API patterns.
Infrastructure operations, deployment, debugging, and monitoring. Use when deploying services, managing secrets, checking health, viewing logs, or troubleshooting infrastructure issues. Covers both finance_repo...
Use this skill when the user asks about "async patterns", "Promise.all", "parallel execution", "Firebase functions", "webhook handlers", "cron jobs", "cold start", "timeout", "pubsub", "background processing",...
React component patterns, hooks, state management, and performance optimization for the PMS frontend. Use for React development questions, component creation, and frontend architecture.
Backend architecture, API design, database strategy, and scalability
Design, document, and generate APIs using OpenAPI/Swagger specifications. Create interactive API documentation, generate client SDKs, validate schemas, and build mock servers. Use when designing REST APIs, crea...
Backend engineering for Skriptoteket (FastAPI monolith): architecture + file tree navigation (DDD/Clean layers), protocol-first DI, Unit of Work + transactions, DomainError semantics, core data shapes/contracts...
REST controller patterns, request handling, validation, exception handling, and WebFlux.
Architecture decision guides for Kailash SDK including framework selection (Core SDK vs DataFlow vs Nexus vs Kaizen), runtime selection (Async vs Sync), database selection (PostgreSQL vs SQLite), node selection...
Provides specialized guidance for backend development including API design, database interactions, authentication, error handling, and security best practices. Use when working on backend code, API endpoints, s...
Comprehensive design toolkit for crafting distinctive interfaces. Workbench for SaaS dashboards and admin panels. Launchpad for landing pages and marketing sites.
Structure projects for maintainability and scalability with clean architecture, separation of concerns, and consistent project layouts.
Create detailed implementation plans through interactive research and iteration. This skill should be used when creating new implementation plans, designing feature specifications, planning technical work, or w...
Create structured implementation plans with scope, phases, and risks. Use when user wants to plan a feature, architect a solution, design an approach, or says 'let's plan', 'create a plan', 'how should we build...
Project Management System domain knowledge including entities, business rules, workflows, and industry standards. Use for understanding PMS requirements, implementing features, and ensuring domain accuracy.
Practical UI/UX work within existing design systems. Use for styling, layout, states, accessibility, and design system compliance. Use when working on established products.
Create detailed implementation plans through interactive research and iteration
Task engine architecture, action queue management, and execution scheduling
Create structured, language-agnostic implementation plans with risks, tests, and approvals. Use when the user asks for a plan or design before coding, especially for large new features or brand new projects whe...
This skill should be used when the user asks to "design a system", "architect an application", "plan infrastructure", "create system architecture", "design for scale", "microservices architecture", "monolith vs...
Transform implementation plans into concise stakeholder-friendly summaries with file change overviews, component listings, and optional flow diagrams.
Create Product Requirements Documents (PRDs) that define the end state of a feature. Use when planning new features, migrations, or refactors. Generates structured PRDs with acceptance criteria.
Use when refining Tasks into actionable plans - SRE-style review ensuring corner cases handled, junior engineer can execute without questions
Create detailed implementation plans for Go projects using Clean Architecture and DDD. Triggers: planning complex features, architectural changes, multi-step tasks, new domain aggregates, bounded contexts, larg...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.