cmux-backend

Enforce consistent TypeScript and Cloud VM backend development practices across cmux projects.

25.8k|2.2k|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-backend
Source: https://github.com/manaflow-ai/cmux/tree/main/skills/cmux-backend
Command: npx skills add https://github.com/manaflow-ai/cmux --skill cmux-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill captures and enforces cmux's backend development rules for TypeScript, Cloud VM workflows, provider integrations, and database migrations, ensuring consistent patterns across web/api code, services, and infrastructure scripts.

Core Features & Use Cases

  • Standardizes TypeScript usage across web/app/api/, web/services/, and backend scripts touching providers, databases, auth, rate limits, retries, timeouts, or telemetry.
  • Keeps Next route handlers thin: parse input, run one Effect program boundary, map errors to responses, and isolate defects.
  • Centralizes cloud VM backend logic in Vercel route handlers and Effect services backed by Postgres.
  • Provides guidance for migrations, runtime envs, and provider pricing gates.

Quick Start

Explain and apply the cmux backend rules to a new web/api module in your project.

Frequently Asked Questions about cmux-backend

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

FAQPage Schema
How do I standardize TypeScript route handlers for backend services?

To enforce backend TypeScript rules, keep Next route handlers thin by parsing input, running one Effect program boundary, mapping errors to responses, and isolating defects to ensure predictable recoverability across web/api code.

What are backend service boundaries in TypeScript and when do I need them?

Backend service boundaries in TypeScript require explicit rules for route handler shape and environment configurations. You need them when managing provider integrations, auth, rate limits, retries, timeouts, and telemetry across cloud VM workflows.

How do I structure backend TypeScript workflows for Postgres and provider integrations?

Structure backend TypeScript workflows by centralizing cloud VM logic in Vercel route handlers and Effect services backed by Postgres, applying explicit rules for runtime envs, migrations, and provider pricing gates across web/app/api modules.

Can I use Effect services with Postgres in cloud VM backend deployments?

Yes, you can use Effect services backed by Postgres within Vercel route handlers to centralize cloud VM backend logic, ensuring consistent patterns for database workflows, provider integrations, and runtime environment configurations.

What's the best way to handle error mapping and defect isolation in TypeScript backend services?

The best way to handle error mapping in TypeScript backend services is enforcing a single Effect program boundary inside thin route handlers, isolating defects, and mapping errors directly to standardized HTTP responses.

Why do my TypeScript database migrations and provider integrations fail across different runtime environments?

TypeScript database migrations and provider integrations fail without explicit rules for runtime environments, service boundaries, and environment configurations, which this approach enforces to guarantee predictable error mapping and recoverability across cloud VM workflows.