backend-runtime-expert

Provides standards for building backend services with NestJS, Deno, and Payload CMS.

Updated May 12, 2026
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill backend-runtime-expert-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-runtime-expert
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/backend-runtime-expert
Command: npx skills add https://github.com/laionazeredo/che-ai --skill backend-runtime-expert-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend developers working across multiple runtimes often lack consistent architectural standards, leading to inconsistent module design, weak access control, and ad-hoc deployment practices. This Skill consolidates proven patterns for NestJS, Deno, and Payload CMS into one reference guide. ## Core Features & Use Cases - NestJS Architecture Standards: Enforces modular design with dependency injection, thin controllers, and business logic isolated in services, plus Pipes for validation and Guards for authorization. - Deno Security & Deployment: Guides use of Deno's permission system (e.g., --allow-net, --allow-read), the standard library, and Deno Deploy for edge computing. - Payload CMS Content Modeling: Covers collection and global schema definitions, hooks for side effects, granular field-level access control, and admin UI customization with React components. - Use Case: When scaffolding a new TypeScript API service, consult this Skill to structure NestJS modules correctly, apply validation pipes, and configure Payload CMS collections with proper access rules. ## Quick Start Ask the AI to review your NestJS service structure or Payload CMS collection schema against the backend runtime standards in this guide.

Frequently Asked Questions about backend-runtime-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a NestJS application with modules and services?▼

Group related functionality into Modules and follow the Dependency Injection pattern. Keep controllers thin by placing business logic in services, and use Pipes for validation and transformation with Guards handling authentication and authorization.

How to configure Deno permissions for secure execution?▼

Deno uses an explicit permission system where you grant capabilities via flags like --allow-net and --allow-read at runtime. Prefer the Deno standard library for basic utilities and deploy to Deno Deploy for edge computing and low-latency execution.

What is the difference between NestJS Pipes and Guards?▼

Pipes handle validation and transformation of incoming request data, while Guards handle authentication and authorization decisions. Use Pipes to enforce input schemas and Guards to control route access based on user roles or tokens.

How do I implement access control in Payload CMS?▼

Payload CMS supports granular permissions defined per collection and per field through access control functions. Define clear schemas for collections and globals, use hooks for side effects, and extend the admin UI with custom React components.

When should I use Deno Deploy instead of a Node.js server?▼

Deno Deploy suits edge computing scenarios requiring low-latency execution close to users. For traditional modular enterprise services with heavy dependency injection needs, NestJS on Node.js remains the more appropriate choice.