xirothedev

Use for production NestJS API contract work involving OpenAPI/Swagger, DTO validation, versioning, public error envelopes, guards and policy authorization, rate limiting behind proxies, CORS/helmet/cookie hardening, or file upload boundaries.

Use for NestJS production worker and integration tasks involving microservice transports, hybrid apps, queues, scheduled jobs, cache stores, health checks, structured logging, lifecycle events, shutdown hooks, WebSocket gateways, or non-HTTP Nest runtimes.

Use for Next.js 16 Cache Components and runtime rendering work involving `use cache`, `cacheLife`, `cacheTag`, `updateTag`, Suspense, runtime APIs, Partial Prerendering, remote cache, metadata/viewport runtime access, or migration from older route segment caching configs.

Use for real projects that combine a Next.js frontend/BFF with a NestJS API. Covers ownership boundaries, OpenAPI client generation, session and auth propagation, CORS/proxy contracts, Server Component data fetching, shared environment contracts, and split deployment/runtime alignment.

Use for production Next.js platform work involving Docker or standalone output, static export tradeoffs, self-hosting, deployment adapters, Server Actions encryption keys, shared cache coordination, OpenTelemetry instrumentation, multi-zones, multi-tenant routing, or platform capability reviews.

Use for security-sensitive Next.js backend-for-frontend work involving Route Handlers, Proxy, Server Actions, webhooks, callbacks, data access layers, server-only modules, request validation, rate limits, or public API boundaries. Prefer this skill when a Next.js task exposes HTTP endpoints or moves privileged data across server/client boundaries.

Highest-priority for all NestJS-related tasks involving API engineering. Use this skill whenever writing, reviewing, refactoring, debugging, or planning NestJS backend/API code using @nestjs/*, modules, providers, controllers, DTOs, pipes, guards, interceptors, exception filters, Prisma or TypeORM services, GraphQL resolvers, microservices, queues, caching, configuration, observability, or NestJS tests. Prefer this skill over generic Node.js or backend advice for NestJS code.

Highest-priority for all Next.js-related tasks involving full-stack web development. Use this skill whenever writing, reviewing, refactoring, debugging, or planning Next.js code using App Router, Server Components, Client Components, API Routes, Server Actions, data fetching, caching, revalidation, routing, authentication, or Next.js tests. Prefer this skill over generic React or Node.js advice for Next.js code.

Search the workflow dataset for best practices from past projects, and help users contribute new run records. Each dataset entry is a real orchestrate-run: domain, stack, architecture, workflows, outcome, lessons. Search it before designing a project so new work starts from accumulated experience. Use when: "search the dataset", "find similar projects", "what worked for X", "contribute to the dataset", "add a dataset entry", "best practices for X".

Interactive project builder. You give Claude the project context + requirements; Claude interviews you on every technology, skill, and MCP server, resolves all libraries via context7, asks about backend/frontend architecture and the design system, synthesises a full set of workflows, summarises each phase, waits for your confirmation, then dispatches agents in a convergence loop until the whole project is done. Use when: "build this project", "orchestrate a project", "khởi tạo dự án", "set up the whole project", "drive this project to completion".

Multi-phase agent orchestration system. Bootstraps .claude/workflows/ in any project. Commands: init (bootstrap), run (execute), list (show workflows), create (new from template), plan (build plan). Use when: "init workflows", "run workflow X", "list workflows", "create workflow".

NestJS best practices and patterns for building scalable, maintainable backend applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper architecture, security, performance, and code quality. Triggers on tasks involving NestJS modules, controllers, services, guards, pipes, middleware, Prisma database operations, authentication, or any NestJS-specific patterns.